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 Workcenter: When you view a notification it is not marked as Read
Workcenter: When you view a notification it is not marked as Read
CMS-XML It is not possible to localize the 'Read' and 'Unread' strings in the Work Center Notifications view.
It is not possible to localize the ' Read ' and 'Unread' strings in the Work Center Notifications view.
CMS-XML Read timed out Error message for MailClient email submit : ERROR ForkJoinPool-1-worker-1 2018-10-23 19:18:38,129 [notificationsrv.MailSubmitParser.MailClient] -- MailBox: "mailboxname", Could not create item "test item" at project "Projectname". Error: Read timed out
Go to Configurator>Mail Services > Notification Server>Common Options>Web Services Invocation Timeout and increase the value. You need to Apply for this to take affect. Note this will restart services so should be done outside of main working hours.
CMS-XML Problem: Notify is sending duplicate messages and is not sending all of the messages.
Notify stops scanning a project when it finds a user who needs more messages sent than what the settings specify in SEND AT MOST in the Notify Options. Notify also does not increase the NFYTID field in the trkusr table for that user so that when it scans the database again the next time it sends out the same messages and then quits again. (i.e.
CMS-XML Subject Line in Notification Message is not Truncated Properly
Different SMTP servers handle the length of the e-mail subject line in different ways. In some cases, the text of the subject line becomes unreadable if the number of characters in the subject line exceeds a certain amount. By altering the TS_SYSTEMSETTINGS table in the SBM database, you can try different subject lengths to determine the length at which the subject becomes readable for the version of your e-mail reader .
CMS-XML Unable to read notification e-mails with a memo field in the subject line
Manager 4.0Release Manager 4.0.1Requirements Manager 4.0.1SBM 10.1.1.4 Service Manager 4.0Service Manager 4.0.1
CMS-XML Notification events for archived items give Application Log error: "Record xx, in Table xxx could not be found"
The complete warning messages from the Event Viewer Application Log is: NOTIFICATION_NAME: ( notification ) context - Unable to read item with id xx from database. And:
CMS-XML ECP SERNET approval notifications are not sent, after upgrading to ZMF 5.5.1.
2005/05/26 07:21:40 Disconnect Smtp connection. 2005/05/26 07:21:40 Shutdown() - Socket operation on non- socket 2005/05/26 07:21:40 CloseSocket() - Socket operation on non-socket
CMS-XML (Notifications) Record %ld, in Table %ld could not be found.It could be that we were evaluationing the TeamTrack change history in the middle of submitting this item.
The problem is that a sub-relational field has two references: (1) relational field in current table, and (2) sub-field, the field with actual required data which is located in the table:record referenced by relational field. The problem is that notification server reads from db only sub-field and does not read relational field.Thus the relational field value is always zero and it cannot go into other table and continue evaluation of rules.
CMS-XML Notification Server sends out duplicate notification emails
11/14/2011 12:24:55: (Messages) EOD: Received error 0 from server webmail.mycompany.com. Data is: No data received on socket
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs