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 Notification Server does not reset Start Date with last time service was running
CMS-XML Common Services Host for Active Diagnostics and Relationship Service Is Not Updated Properly in Cluster
SBM 10.1.4
CMS-XML ResMan server schema failed during upgrade of Common Services, but no error was logged during the upgrade
SBM 11.0.1
CMS-XML Calendar without timeranges may cause infinite loop in SLA engine - The SLA widget shows “No SLA status” for these items - CPU high on Common Services server
SBM 11.4
CMS-XML Static diagnostic test 'SBM Services' failed with "The calling thread cannot access this object because a different thread owns it" error
The static diagnostic test ' SBM Services ' fails with a "The calling thread cannot access this object because a different thread owns it" error in a distributed environment with components installed on separate servers . The failure does not necessarily indicate an actual problem.
CMS-XML RLM gives error "No match with the browser requests service URIs: http://server:8080/serena_ra/." when trying to open the login screen
When setting up RLM to use SSO with SBM , you may get the following error in the browser: SSO Gatekeeper error has occurred: No match with the browser requests service URIs: http://server:8080/serena_ra/.
CMS-XML SBM Configurator cannot perform License Server Test Connection on SLM quorum or single SLM server with port number
Release Manager 5.1 SBM 10.1.4 Service Manager 5.1
CMS-XML If you install SBM then Soo and promote the solutions without going to workcenter then get SRC errors - Error Getting Catalog: No service Catalogs found.
If you install SBM and then SOO and then promote the snapshots per the documentation then all the promotes are marked as status complete but all have the following info message in the activity log: Deploying to server "Work Center Server " at 13/01/14 10:20. Failed to complete the deployment to server "Work Center Server" at 13/01/14 10:20.
CMS-XML SBM Configurator- Notification server type: " Test Server " is not working when set the username and password
Even if the SBM Configurator, Mail Services , Notification server , E-mail server type: Test server , Directory Location uses UNC path for a Test server , it will work, but you will receive an error message in the ns.log. Please have a look at the error message below.
CMS-XML There are currently no processes scheduled to run. Mail Services currently disabled on this instance
Unsupported database server: Oracle Version: Oracle Database 12c Enterprise Edition Release - 64bit Production This message clearly shows the reason for the failure of Mail Services to execute their processes. Either SBM needs to be upgraded so that it supports the given database server version or the database server needs to be downgraded.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs