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 Cannot start Active Diagnostic (SBM Logging Services) and get error "Cannot connect to the Active Diagnostics database. Runtime configuration is currently unavailable.”
When starting Active Diagnostics, it will start quickly and immediately stop. The logs will show error:
CMS-XML DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log . If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
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 JBOSS will not start after upgrade - error in service_execution.log starts with: Failed to boot JBoss ... Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future
JBOSS will not start after upgrade - error in service_execution.log starts with: Failed to boot JBoss ... Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future
CMS-XML Windows could not start the on Local Computer. Cannot start Perforce VersionBridge (P4DTI) as an NT service
This message will appear in the Application event log : Python could find the service class in the module exceptions.AttributeError: <custom_service_name>
CMS-XML Pacific Edge Scheduler services will not start
Error 14001: The application has failed to start because its side-by-side configuration is incorrect. Please see the applicationn event log or use the command-line sxstrace.exe tool for more details.
CMS-XML Serena License Server will not start and log showing garbage characters
Stop the license service and try to rename the SerenaLicenseServer. log file.
CMS-XML Relationship service will not start - message in Configurator - SBM Relationship Service Database failed to start in the allotted time period.
Check the logs recently updated in C:\Program Files\Serena\SBM\Common\RelationshipService\data\ log . There may be an indication of the port already in use. If this is the case the bring up Task Manager and the processes and check for multiple java.exe.
CMS-XML Notification service gives error "Log entry string is too long. A string written to the event log cannot exceed 32766 characters" and must be restarted
Jun 2010 20:06:00,191 [Notification] (null) INFO 5 - Starting notification service 19 Jun 2010 20:06:00,425 [Scheduler] (null) INFO 5 - Using services host: IADSERMARUTL02P at URL http://ppm.serena.com/PPM/WebServices/peswebconfig.asmx
CMS-XML Active Diagnostics service won't start or you see a socket error in Configurator about the Active Diagnostics service.
To help troubleshoot the Active Diagnostics service , look in the MongoDb service log . (By default, located at C:\Program Files\Serena\SBM\Common\Diagnostics\MongoDb\ log \mongoDB_winservice.txt) NOTE: This file is easiest to read using WordPad.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs