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 Logging into Request Center get "Error getting catalog: Service Unavailable"
When you log into Request Center you may see the following error: Error getting catalog: Service Unavailable or you might see this error in the Application Event Viewer.
CMS-XML Cannot start Active Diagnostic (SBM Logging Services) and get error "Cannot connect to the Active Diagnostics database. Runtime configuration is currently unavailable.”
Cannot start Active Diagnostic (SBM Logging Services ) and get error "Cannot connect to the Active Diagnostics database. Runtime configuration is currently unavailable.”
CMS-XML Logging into Repository or Composer gives "Authentication Failed: Unable to contact Authentication Service"
Users are able to log into the SBM Application Engine ( http://servername/tmtrack/tmtrack.dll ?), however, no one can log into the Repository ( http://servernmae/mashupmgr ) or connect using Composer. Composer gives error: Connection attempt failed.
CMS-XML Logging into Repository gives error "Authentication error: A Soap fault occurred while contacting the authentication service"
When trying to log into the SBM Application Repository, the user gets the following error:
CMS-XML ResMan server schema failed during upgrade of Common Services, but no error was logged during the upgrade
During the upgrade itself, there are no errors logged when the ResMan (Resource Manager), work center or SLS schemas are upgraded. If there are any problems during the upgrade, you will not see the errors until you try to log into work center.
CMS-XML Notification Server gets a Null Pointer Exception when debug log is turned on in the Configurator Mail Services section - Error: "While job executing java.lang.NullPointerException"
There is exception when debug log level is ON. This can be ignored and does not have functional impact.
CMS-XML Relationship service will not start - errors in relationshipservice.log as follows: THERE ARE MORE THAN ONE CYPHER QUERIES WITH NAME
C:\Program Files\Serena\SBM\Common\jboss405\server\default\ log \relationshipservice. log WARN 25-03-2015 10:33:56 [CypherQueriesLoaderImpl] -- cypherQueryIsAlreadyAdded(): THERE ARE MORE THAN ONE CYPHER QUERIES WITH NAME: getOneLevelDependentCIs WARN 25-03-2015 10:33:56 [CypherQueriesLoaderImpl] -- cypherQueryIsAlreadyAdded(): THERE ARE MORE THAN ONE CYPHER QUERIES WITH NAME: getAssosiatedCrs
CMS-XML Orchestrations failing and server.log shows ORA-12519: TNS:no appropriate service handler
Orchestrations failing and server. log shows ORA-12519: TNS:no appropriate service handler
CMS-XML Warnings in ODE.log when requests to services contain empty Body
Warnings in ODE. log when requests to services contain empty Body
CMS-XML Web Services call from Notification causes Event Log errors
In Business Mashups 2009 R1, when you invoke aewebservices71 from a Notification, and use the UpdateItemWithName, the webservices executes properly, however, you receive a series of errors in the Application Event Log . The errors in the Application Event Log would contain phrases similar to the following: Error occurred in file:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs