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 KM-Dim9: Replicator: : Failed starting server ‘’ on host .
KM-Dim9: Replicator: : Failed starting server ‘’ on host .
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"
[2018-07-20 15:43:28] [info] Running Service.. . [2018-07-20 15:43:28] [info] Starting service...
CMS-XML KM-Dim7: Installation aborts when attempting to start services.
KM-Dim7: Installation aborts when attempting to start services.
CMS-XML Error in Mashup Administrator when Click options/manage services - Error: The service 'Serena Broker Service' could not be opened. You will not be able to start or stop processes.
Error in Mashup Administrator when Click options/manage services - Error : The service 'Serena Broker Service' could not be opened. You will not be able to start or stop processes.
CMS-XML Error: VMINET 6.0: Cannot start service adminservice: Port 9090 is already in use.
When starting the JavaWebServer you receive this error message: Java Web Server ERROR: Cannot start service adminservice: Port 9090 is already in use. Change the port or shut down the other network service that is using it.
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 12.1.1 : start of z/os agent => MDHAZJ1600136W Unable to connect to service: errno: 1128
randomly, when starting the z/os agent, go these message in the output of the z/os listener : MDHLCN1600003I Console Command Listener Started
CMS-XML When starting the Mashup Manager - getting error in server.log "Trying to install already registered mbean"
Mashup Manager does not load, and checking the server.log shows: status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.jca: service=LocalTxCM ,name=serenaAdminDsn
CMS-XML SLM: Error 2 the system cannot find the specified file / License manager service fails to start
This can happen if the uninstall of a previous version did not properly remove the service, preventing the new version from installing its service entry. As a result, the old service entry will attempt to start the SLM server but fail because it incompatible with the version it is trying to launch.
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:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs