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 DIM10: How to stop email notifications for pending items on Windows server
DIM10: How to stop email notifications for pending items on Windows server
CMS-XML Unable to send email from Mariner / Agile test message button or stop getting email notifications and reports.
You may get errors like below in the Application Log of the Event Viewer on the Mariner / Agile server which results in email notifications no longer being recieved. Event Type: Error Event Source: Pacific Edge Software
CMS-XML Problem: #1064 Users stop receiving In Tray or E-mail notifications
Several reasons exist why a user may not receive notifications they expect.
CMS-XML Problem: Notify 6.5 stops processing notifications when a user does not have a mail address specified.
If a user does not have a mail address specified for there user profile, and Notify tries to notify that user, 6.5 will give a prompt stating no mail address specified for that user. This effectively stops Notify until the dialogue is confirmed. Until manual acceptance of this error is given, no notifications will be sent.
CMS-XML Stop or start notification server or mail client or SLA without using Configurator in SBM 10.1 and newer
...\SBM\Common\tomcat\server\default\webapps\notificationsrv\WEB-INF\classes directory and the restart SBM Tomcat When the notification server and the mail client are running, the contents of the file will look like the following: ns_paused=0
CMS-XML Dim10: Cannot shutdown email communication / notifications on unix systems
On Unix systems, disabling the following value field in dm.cfg is not sufficient to stop email notifications from going to users. #DM_DMEMAIL #DM_MAIL
CMS-XML KM-Dim9: Solaris email notification fails when or 9.1.3 patch is applied
Users stop recieving email notification after updating server to
CMS-XML Repeat notifications stop running in Cluster environment (TS_THREADID gets stuck)
TS_NOTIFICATIONEVENTS table will be stuck. After this, the notification will no longer run, and users will not receive emails for these events. This has been seen mostly with scheduled reports but can also happen with repeating notifications.
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 View item link in a email notification is broken for a hand held device
To work around this problem: Stop your TeamTrack Web server. On the TeamTrack Web server, navigate to the Serena/TeamTrack/template/html2 directory.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs