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 DA: DA fails to start correctly if Oracle identifier contains a hyphen
The problem was caused by the hyphen in the Oracle identifier which, in the above example, is SERVER-TP. Once the hyphen was removed, either by changing the identifier at the Oracle level or adding an alias in tnsnames.ora, Tomcat started without the error occurring.
CMS-XML DA: The installer fails to start properly if you only have the HTTPS connector active in server.xml
The problem was found to be that only the HTTPS connector was active in the server.xml and the installer only looks for the HTTP connector details. Once the HTTP connector was enabled/uncommented the installer started correctly.
CMS-XML DA: Is there any functionality for specifying a secondary Agent Relay so, if the first relay fails, a secondary one takes over?
It is possible but it should be configured on an agent level. There is an option to provide several connectivity points for an agent and it will try to fail -over when the existing connection fails . In order to configure this you should modify the file
CMS-XML After SMS compression is turned on for DA dump datasets job failed
ESM0037E * - Jobname=TMIJOS9D, RC=X"40000908". ESM0037E ************************************* We will like to reduce the amount off space the dump datasets used by having SMS compression turn on .
CMS-XML DA: DA server will not start
DA Server will not start. The following error can be found in the DA or Tomcat logs: 2018-02-16 14:10:24,331 - Failed to start Serena DA java.lang.NullPointerException at java.util.Hashtable.put(
CMS-XML DA: A remotely installed agent doesn't start properly if there is white space in the installation folder structure
However if there is a space character in the installation folder structure the following error occurs when the agent tries to start up following a remote installation: "Error installing agent to IP. Starting the agent failed with return code 127"
CMS-XML DA: java.util.ConcurrentModificationException: Persistent components/[id]/processes/[id] has been modified since the start of this transaction.
If not please make the alteration and restart Tomcat for the change to take effect. Then try to run the failing deployment again and, if the error still occurs, provide a copy of <profile>\var\log\deployserver.out and the Tomcat logs from C:\Program Files\Micro Focus\common\tomcat\8.5\logs for analysis.
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] [902 ah3srvc.c] [error] Failed creating java C:\Program Files (x86)\Java\jre1.8.0_151\bin\client\jvm.dll
CMS-XML DA510: ESPYAMON 061E Workload server serialization failure: enq macro rc=x'04'
Details: A new OS/390 2.10 system was brought up running LE version 2.10. When the ES04WLS workload server task was started , the following error message occurred and the ES04WLS task failed .
CMS-XML DA: After startup Tomcat catalina log file contains errors like: Invalid URL found in class path
The software is having problems with the space character in the URL pathname. This is causing DA startup to fail when trying to read several of the properties and XML files. DA may still start, but it will be running with default values rather than the values set for your site.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs