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 SBM Configurator returns the misleading error "Connection failed" when SLM is using a fixed port
SBM Configurator returns a misleading error when the license server string includes a port number, like 27008@ServerName , which is necessary when the SLM server runs on a fixed or non-standard port.
CMS-XML SBM: Users get error "InitExtension Failed" and "License server could not be contacted"
When connecting to the APLS, you must enter the connection URL in SBM Configurator on the License Server page. However, if this URL is entered with a trailing slash, SBM will not be able to connect. The "Test Connect" link inside Confgurator will work, but SBM Tomcat will not be able to connect.
CMS-XML KM-Dim9: Cannot connect to license server (-15,10:10061 "WinSock: Connection refused"): DIMENSIONS_CHANGE (DMSYS)
[ERROR] Failed to Connect to the Dimensions Server ! Cannot connect to license server (-15,10:10061 "WinSock: Connection refused"): DIMENSIONS_CHANGE (DMSYS)
CMS-XML SLM configuration with multiple servers fails if server1 not available
If you have multiple SLM servers defined in Configurator and the first server listed becomes unavailable, you will not be able to obtain a licence from the second machine. In addition, Configurator will fail the "test connection " if you have used a semi-colon as the separator (which is the correct syntax).
CMS-XML Dim12: Linux 64-bit License Server: createJob failed: -2
License Server: createJob failed: -2 License Server: createJob failed: -2 ACL4502922E Error: Cannot open connection to host COL-SC-LINUX
CMS-XML Calling PCLI from Apache on Linux fails with Cannot connect to license server system. (-15,570:13 "Permission denied"): VersionManager (Username)
The message means the process lacks the permissions to establish the necessary TCP/IP connections .
CMS-XML Launching SBM System Administrator or SBM Login Screen give error "InitExtension Failed" "License Server XXXX could not be contacted"
If License Manager is installed on the same machine as SBM, try using "localhost" instead of the server name. If this works, there may be a firewall rule that is blocking the connection . You can work with your security team to change the firewall rule, or use localhost instead.
CMS-XML SBM Configurator cannot perform License Server Test Connection on SLM quorum or single SLM server with port number
then the Test Connection link on the License Server page of the SBM Configurator will consistently give the error Connection failed , even though the SLM server(s) can be accessed fine.
CMS-XML PCLI repeatedly requests the same license, causing the SLM License Server to (temporarily) fail for all users
The PCLI command causing the problem itself terminates, complaining about license server problems. Network clients of other server processes running on the SLM server system can no longer establish a new connection to the sever, while clients with already established connections remain unaffected. Although the server will normally recover from this event after the PCLI client causing the problem terminates, this can take some time as the TCP sockets that were used need to go through their TIME_WAIT cycle before becoming available again.
CMS-XML Dim12: License Manager: No features to serve, exiting. Exiting due to SIGNAL 27 Exit Reason 4
When starting the license manager an error occurred causing connections to Dimensions CM to fail . The message in the license log file was:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs