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 Work Item On Update notifications don't go out after resource is assigned
[Repro Steps] 1. Setup an On Update notification for Work Items. 2. Create a new work item.
CMS-XML Notification Server hangs or crashes so notifications no longer go out in 2009 R4 - DEF198769
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.
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 Thrown back out of the rules when exiting a notification rule - back arrow or via breadcrumb
Go into any notification rule, e.g. Administrator Portal -> Notifications -> Rules -> pick any rule Click on the Back arrow or on the Notifications button in the path and you are thrown back out to the Initial Rules screen and have to expand your process apps again to navigate to the rules again. In the old App Admin this worked nicely and if you went back you were placed on the previous screen.
CMS-XML Configurator exits with exception preventing admin from configuring notification server
Configurator exits with exception preventing admin from configuring notification server
CMS-XML Notification Server leaving orphans in TS_NotificationEvents on Notification deletion.
Occurred after upgrade from 2009 R2 to 10.1.1.3. Through the Admin Portal the Notification was deleted. This immediately caused warnings to be generated that the notification server was trying to process entries in the TS_NotificationEvents table that didn't have an associated Notification.
CMS-XML Notification not firing for new users or new projects
There is a 10,000 hard limit on some tables for the Notifications server. If this is hit then notifications may not go out .
CMS-XML HTML content appears in notification when contents have been copy pasted from web page
When users copy and paste content from a web page into the Description field in an item. When the notification goes out , the email contains html.
CMS-XML How do workflow transition notifications work?
The Pacific Edge Scheduler service starts the job (called "Workflow Notifications") as configured on the Scheduled Jobs screen. The scheduled service checks for notifications that need to go out and sends the messages directly. It uses the same code files as the Pacific Edge Notification Service, but the Notification Service is not involved in sending these notifications.
CMS-XML Notifications not firing for new users or new projects
There is a 10,000 row limit on some tables for the Notification server. If this is hit then notifications may not go out .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs