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 Orchestrations not running even though Event Manager receives the event - "The service cannot be found for the endpoint reference (EPR)" error in server.log
This has been resolved in the past by stopping the SBM Tomcat service, deleting the contents of the " SBM \Common\ tomcat \server\default\work" directory, and restarting the SBM Tomcat service to let it recreate the contents of that directory. If that does not resolve the issue, re-deploying the process app with the orchestration may resolve the issue.
CMS-XML "Connecting to backend failed. Tomcat is probably not started or is listening on the wrong port " error in isapi_redirect.log file
file. Verify that this is SBM. If there is another tool on the server that is also running Java, you will need to stop that tool and restart SBM Tomcat .
CMS-XML SBM: SmartSearch suddenly stops indexing new items (Tomcat Cluster)
When Tomcat is setup using a cluster and Tomcat fails on one node, it will failover to the other node. If this node was also being used for the Smart Search indexing, the index will quickly become out of date. New items added after this problem will not be found by search until Tomcat is restarted and the index has a chance to catch up.
CMS-XML When restarting IIS or Tomcat service it stops but then doesn't start
SBM 11.4
CMS-XML DueDateProcess in Notification Server may freeze after database connection issues causing delay notifications to not send
In some cases, the DueDateProcess in Notification Server may freeze after database connection issues which can cause delay notifications not to send until the SBM Tomcat service is restarted . If the DueDateProcess has been frozen for a period of time and delay notification emails were not sent, you will see a series of messages in the ns.log that say "[DueDateService] -- Due Date event was removed as deprecated : NotificationEvent" which means that the delay time has already passed and the event is being removed without sending the email.
CMS-XML SBM: Tomcat will not stay running. Console log gives: Failed upgrading SLA server schema
After an upgrade, Tomcat will start, run for a few seconds, and stop . When looking in the console.log, the following error displays:
CMS-XML SBM 12: Load balance / Cluster Tomcat with Notification Engine stops responding
Workaround Option 1: Restart the Tomcat service on both servers, then start the Notification Server only on one node. However, this means the Notification Server is no longer load balancing across nodes.
CMS-XML Dim cm : after changing of SBM SSO server, web client is still pointing to the previous SBM SSO server
_ deleted contents of "work" folder of Tomcat _ stopped / restarted Dimensions cm listener and Tomcat when starting web client, it sill points to the previous SBM SSO server.
CMS-XML DIM CM: HTTP connector process does not stop on Solaris when running dmshutdown
The process may be manually killed, to identify the process ids involved please perform the following steps: Select the process which is the http connector (exclude the process using a tomcat relative path for java) : > ps -ef | grep java
CMS-XML Recommendations for Tuning Tomcat Memory Consumption and SBM Performance
If you are using SBM 11.0, Serena recommends that you add this setting to the common_config.bat file. After saving your changes, run update_tomcat_config.bat to apply the changes, and then restart SBM Tomcat .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs