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 Troubleshooting Microsoft Message Queue (MSMQ) Problems or Notification sending problems.
Under Configuration | Environment Settings | Notification Settings, verify that the Notification Queue Server Name is correct. Do not use "localhost", even if the MSMQ is on the same server as Mariner/Agile.
CMS-XML Failed promotion cleanup notifies task id
Failed promotion cleanup notifies task id
CMS-XML Delayed notification not working in SBM11.3.1
In case if customer have queue of escalated notification events, new Undelayed notification event may never processed
CMS-XML Whole import log was sent in each notification email
Notification email for user/data import log contains all old import logs concatenated and not the current import log alone. Import log is not automatically cleaned up and whole import log was sent in each such notification email. Eventually the import log size grows and exceeds the email server size limit for email message, and customer stopped to receive emails with import results.
CMS-XML Notification template loses html tags after editing
To reproduce, start with a clean install.
CMS-XML Getting "remote computer not available" error in notification log for Mariner.
Verify the Queue is already setup in the Microsoft Message Queue . An example of a Queue path running on the same computer as Mariner might look like this "private$\mariner"
CMS-XML Mail Client process does not clean item cache after each cycle
Mail Client process does not clean item cache after each cycle. As a result, each email-submitted item is visible in its initial state for a timeout period of 15/30/60 seconds, depending on cache settings which can cause notifications to not get triggered as expected.
CMS-XML Inefficient handling of deleted users in Notification Subscription mechanism since 11.4
The log excerpt below shows a long delays (40 mins+) in processing of notifications. 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
CMS-XML Notification Server leaving orphans in TS_NotificationEvents on Notification deletion.
Customers might see intermittent instances of orphaned items in the TS_NotificationEvents table proving that events associated with the notification were not cleaned up when the notification was deleted via the admin tool.
CMS-XML Items stuck in TS_NOTIFICATIONEVENTS table when jboss restarted, causing some notifications to stop functioning
SBM isn't cleaning up after itself correctly and leaves a thread id value in the database. Consequently, when JBoss is started next time the notifications with a value in the threadid column is just skipped and don't run again.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs