Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML SBM 10.1.5 Upgrade Deletes Older Notification Events
SBM 10.1.5 Upgrade Deletes Older Notification Events
CMS-XML Dim: How to diagnose problems with Dimensions CM Build Notification Mail messages
... popup titled " Notification Service Configuration" ... by build for event notifications . ... for any build notifications ... still not sending notifications from a build ... Navigate into the into the 6.0 directory (this will be 5.5 for older versions of Dimensions) ... Uncomment the following 4 lines (this will likely be only 3 lines if you are using an older version of Dimensions with tomcat 5.5). ... Delete the work folder (underneath tomcat/6.0)
CMS-XML Deleted notification events remains in Oracle database.
Deleted notification events remains in Oracle database.
CMS-XML Notification escalation event is not updated when owner changes
When an item changes owner, the notification escalation event is not being changed to notify the new owner; the old owner still recieves the escalation e-mails.
CMS-XML KM-Dim7: Email event notifications are not being received
If VMS email addresses are mapped to other email addresses (say NT) the delay in the lookup process causes the message to be deleted off the system before the VMS mail system is ready to send it onwards.
CMS-XML Remove old Work Center UI notifications
SBM Work Center shows notifications received by the user using the bell icon in the upper right corner. When selecting the icon, it is possible to produce a list of those notifications so that the user can read and delete the notifications. However, it is currently only possible to delete notifications one at a time.
CMS-XML Dim12: Mail: Unable to delete users subscribed to mail notification of Promote of an Item when project is deleted
Subscribing users to the Promote of an Item Mail Event which is assigned to a specific project and GSL lifecycle. In turn, if the assgined project is deleted and the users remain subscribed to the Mail Event and a delete can not be performed. What are the steps to reproduce the problem?
CMS-XML Exception Thrown while processing Notification Event 'Process Active Processes' and many records in NS_DUMPRECORDS table
org.springframework.dao.CannotAcquireLockException: could not delete : []; SQL [delete from NS_DUMPRECORDS where ID=?]; nested exception is org.hibernate.exception.LockAcquisitionException: could not delete: []
CMS-XML Restart of JBOSS server sends out an old notification email
Stop the JBOSS Server. Delete all cache files and folders under [Serena\SBM Install Dir]\Common\jboss405\server\default\work.
CMS-XML Inefficient handling of deleted users in Notification Subscription mechanism since 11.4
INFO 12-09-2018 09:43:00 [Notifications] -- Notification 'Incident submitted to investigation Queue' being sent on Tbl:ItemId 1620:1381 for recipient with userid = 96 INFO 12-09-2018 09:43:00 [ Notifications ] -- Added event 29362915, Tbl:ItemId 1620:1381, to events table for notification 'Incident submitted to investigation Queue' for recipient with userid = 96 which is the first email generated.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs