Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Configuration report has incorrect Load Level and caching level information for notification server
Notification server Email server protocol: SMTP Connection timeout: 120
CMS-XML Database unavailability causes thousands of Notification Warning emails.
Running Oracle and a SBM instance which runs on Windows Server 2003, if the Database is shut down but application services left running, the Notification server sends a warning email every 10 seconds to the "Administrator" email address. This issued 20,000 emails from the Notification server and the Configuration Settings were overridden
CMS-XML New fields are missing from notification emails
This is due to cached information in the Notification Server . The cache is refreshed automatically (about every 20-30 minutes). If this does not pick up the change or you cannot wait, restarting JBOSS will also force the cache to refresh.
CMS-XML Mail Client process does not clean item cache after each cycle
Possible workarounds are to run the Mail Client and Notification Server on different servers or perform the following steps: - stop JBoss - edit ../Serena/SBM/Common/jboss405/server/default/deploy/notificationsrv.war/WEB-INF/classes/ns_ehcache_config.xml file
CMS-XML Approvers getting project notification and email for each file in the project
********* INSTRUCTION FOR APPLYING PATCH ********** 1. Shut down DS server . 2. Exit from Change Man DS clients or development IDEs
CMS-XML Randomly missing field content in notification emails, which may lead to confusion
build-in a delay of 1 minute (no more is necessary) into the affected notifications send only those fields that are necessary for easy identification of the item - the rest can be read by opening the item (this also keeps the size of the database and the emails to a minimum) set the Performance and Cache settings for the Notification Server in Configurator; experimentation may help in finding an acceptable value that minimises this problem.
CMS-XML E-mail notifications not completing when sent to an Exchange 2000 IMC server.
E-mail notifications not completing when sent to an Exchange 2000 IMC server .
CMS-XML Notification Server could not recover after SQL Server connection problem and causes shutdown in progress errors
Notification Server could not recover after SQL Server connection problem and causes shutdown in progress errors
CMS-XML Add more information for ERROR message "Cannot convert Message to Email" in ns.log for Notification Server
Add more information for ERROR message "Cannot convert Message to Email " in ns.log for Notification Server
CMS-XML SBM System Administrator: unable to start Mail Client and Notification Server remotely
SBM System Administrator: unable to start Mail Client and Notification Server remotely
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs