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 KM-Dim7: Failed to connect to the Dimensions Server! Dimensions Network:No route file name on 'Host_name'
Sometimes when you have just installed Dimensions or you have moved the Dimensions installation on the server you get the above error message
CMS-XML KM-Dim7: Cannot connect to SDP Node : Error 10054
Check the following: Check the Network Administration Tool to verify that the Linux Agent has been defined in the Dimensions Server .
CMS-XML Dim12: Failed to connect to the Dimensions server. ACL4502922E Error: Cannot open connection to host HOSTNAME Logon failed for user dmsys and domain . (1326: Logon failure: unknown user name or bad password.)
The above error generally occurs when the Dimensions system admin user, dmsys, password has changed. In addition to changing the password at the network level, you will also need to modify the password which Dimensions stores in the registry.dat file.
CMS-XML SBM: Notification email are not sent. Log gives " No route to host: connect"
You might be able to narrow down the problem by going to the SBM server, and running the trace route command (for example, tracert If the trace route fails, this is a network connectivity issue and not an SBM product issue. Work with your networking team to resolve the connection issue.
CMS-XML KM-Dim7: Error: Failed to connect to the Dimensions Server! Error: Connection refused by (server host name) (10061) Check Status of Dimensions Network Daemon on and attempt reconnection
4) In the PCMS_STARTUP script ensure the DFS lines are uncommented. 5) NOTE: ensure there are no TRACE logs enabled in the pcms_startup script WINDOWS 1) Check to see if the Dimensions services are running: PVCS Dimensions services (pcms_dfs) PVCS Dimensions listener services (pcms_sdp) 2) Verify that the Network Administration Tool has been correctly updated to Register the DFS Node . a) Check "Operating System Registration".
CMS-XML MCLG: Error "Unable to open project. This server is not connected to the administration database encoded in the license key. You cannot open any projects unless the admin database host and the host encoded in the license key match exactly."
The Collage database server was started before a network connection was found. This will happen if the Collage database server initializes before a network connection has been correctly started, which means that Collage thought the IP address was, thus causing the address mismatch. In this case, restarting Collage after the network has completely come up will resolve the problem.
CMS-XML DA: Error: An existing connection was forcibly closed by the remote host
This problem will occur whenever a thread has a connection open for a long period of time and a problem outside of Tomcat or the server occurs. For example, a network problem, or the crash of a remove agent may cause this problem. This error can be ignored because the software will work to automatically re-establish the connection when the resources are again available.
CMS-XML KM-Dim9: Replicator: Error: Connect failed to (). Check status of Dimensions Network daemon on and attempt reconnection.
An error was encountered when trying to connect to the Listener on the target system.
CMS-XML DimCM: Remote node login fails with "ACL4500285E Error: Connect failed to (110)" error
curl http://<adress ip of agent>:671 whereas curl command completes successfully on server S1, it fails on server S2 with this message : curl: (7) couldn't connect to host This shows it is not a Dimensions issue but a network issue between server S2 and agent machines, leading communication to fail on port 671 between these 2 machines.
CMS-XML Dim10: Command Center ETL Job Logs Error "The network adapter could not establish the connection"
This could happen if the Dm.source.web_url_host,, and values in install_root_dir/common/tomcat/5.5/webapps/refresh-scheduler/WEB-INF/classes/oracle/ETLConfig.xml are set to a different host value from the host value in the Oracle install_root_dir/ NETWORK /ADMIN/tnsnames.ora file. To fix, make a backup of the ETLConfig.xml
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs