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
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
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 Error when using Web Client without Java: Failed to connect to the server using a certificate
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 DimCM: "Failed to connect to the server using a certificate" error message trying to check out using Web Client Tools
This can be caused by invalid setting for tunnelingProtocol in web.xml By default Web Client Tools is configured to use HTTP protocol via HTTP connector .
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 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 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"
b_ the HTTP connector service is running but in %DM_ROOT%\dfs\cmhttpd_config.dat file, "port" field does not the same value that the field "tunnelingPort" in %DM_ROOT%\common\Tomcat\8.0\webapps\dimensions\WEB-INF\web.xml. Then set the both fields with the same value.
CMS-XML DimCM: Web Tools: Error: Failed to connect to the server using a certificate or Failed to start Dimensions server process
1. Verify that the Dimensions CM HTTP Connector service/process is working. a. Using the url noted, verify that you can connect to the url. b. Enable logging as needed in the $DM_ROOT\cm\dfs\cmhttpd_config.dat file.
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