Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
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 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 Notification Server Email Header Information
Notification Server Email Header Information
CMS-XML Default from address for notification server always used for emails from items
Default from address for notification server always used for emails from items
CMS-XML When notification rule starts with NOT, emails are “from” server$@server instead of the last modifier
1) Setup a notification with a "when" rule such that the first line of the condition is a "not". (This rule does not make a lot of sense, but this is just for demo purposes.) For example:
CMS-XML When second part of notification rule is TRUE, emails are “from” server$@server instead of the last modifier
1) Setup a notification with two "parts" (separated by an "OR") in the rule. For example:
CMS-XML Notification Server hangs or crashes so notifications no longer go out in 2009 R4
If the amount of emails being sent in a cycle is less then the number of configured threads then each unused thread will be leaked. This will result in the number of threads increasing whereby the notification server will eventually crash or hang and no notifications will be sent out. All installations of 2009 R4 will have this problem as the configured number of threads is 2. So if in notification cycle there is only 1 email there will be a thread leak.
CMS-XML NS - Notification emails broken with high-ASCII chars in name of addressee
In 10.1.2 the Notification Server switched on customer request to using user names in the "To:" section of emails . If the user name contains any non-ASCII characters, such as high-ASCII accented characters, while the email will still be sent, it may not display correctly.
CMS-XML Notification Server not sending updated fields
A user updates an item by adding an attachment. Shortly thereafter (30 or so seconds), the user updates another field within the same item. The email will sometimes show the old data instead of the updated data.
CMS-XML Web services authentification user should be available for Notification Server
The web services authentication user setting is on the Mail Client tab under Mail Services in the Configurator. This option also applies to scripts and web services being run by notifications so the setting should be available under the Notification Server tab as well.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs