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 Dim CM 14.4: Web Client Tools generating error "Failed to connect to the server using a certificate" when Dimensions CM is using SDP over SSL
Failed to connect to the server using a certificate . Command execution failed. Please check the log above for more information.
CMS-XML DimCM: "Failed to connect to the server using a certificate" error message trying to check out using Web Client Tools
If HTTP Connector is disabled or is not running then Web Client Tools will return this error. To resolve this user needs to enable / start HTTP Connector , or change tunnelingProtocol value to 'sdp' to use SDP protocol instead.
CMS-XML Dim cm 14.3.3 / web client tools : Get of item fails with "failed to connect to the server using a certificate" plus "Couldn't resolve proxy name"
NCL1803331E Connection to the Dimensions CM HTTP Connector on " http://<hostname>:81
CMS-XML DimCM: Web Tools: Error: Failed to connect to the server using a certificate or Failed to start Dimensions server process
When using the Web Client with Web Client Tools , an error of the following can occur: NCL1803331E Connection to the Dimensions CM HTTP Connector on " http://SERVERNAME:80 " failed - 56 (Failure when receiving data from the peer). Failed to start Dimensions server process
CMS-XML DimCM14: cmhtppd: When doing a get from the Web Client with "client web tool" active, getting the error "failed to connect to the server using a certificate"
<description> Specifies the network protocol used by Web Client Tools . Can be one of the following:
CMS-XML KM-Dim9: Verifying System Authentication for Tool Admins
Using local login credentials on the Dimensions server , the login is failing with the error: Failed to Connect to the Dimensions Server : Failed to start the Dimensions server process.
CMS-XML Web Tools without java dependency error: Failed to connect to the server using a certificate
When enabling web tools without java dependency and using HTTPS with tunnelling SDP on port 671 you can receive the error: Failed to connect to the server using a certificate In the SDP logs you will see: do_AAA_connect() failed with -1 (Failed to obtain address for ""; No such host is known. (11001)) PcmsClntConnectWithCertificate: Connection failed
CMS-XML DimCM: Web Tools: Failed to connect to the server using a certificate
In reviewing the dmweb SDP log file, review the servername that we are connecting to. In some cases, the server name may be 'shortened' rather than include the fully qualified domain name as Dimensions is expecting. To fix this issue, add the following variable into the Dimensions CM Server's dm.cfg file:
CMS-XML Dim10: LDAP: Failed to connect to the Dimensions server. LDAP Error: (49) Invalid credentials, LDAP Server Error: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece, PRG4500325E Error: User authentication failed - LDAP bind to server failed
LDAP Error: (49) Invalid credentials LDAP Server Error: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece PRG4500325E Error: User authentication failed - LDAP bind to server failed
CMS-XML Asynch Orchestration doesn't log a failure anywhere if using SSL with a certificate/connection problem to the Target Server
The logging you do get doesn't show a problem and it looks like the orch should have run but the event never makes it to the AlfEventManager log. We should either log this connection failure somewhere or at the least make the Test Connect button fail in the Repository when there is an SSL Connection issue. This Test Connect button should also pertain to Endpoints in the Endpoint area in Repository as well as the Target Servers area.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs