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 VM 8.5.x: Configure Project shows "The LDAP connection information is not valid. Please correct." when trying to save changes
PVCS Version Manager 8.5.00
CMS-XML PVCS VM: You cannot access this project because the LDAP User DN or Password is incorrect, or the Server cannot be reached as specified.
You cannot access this project information because the bind username or password for the LDAP server Authentication is incorrect. Please verify the LDAP connection information or contact your Serena administrator for further assistance.
CMS-XML PVCS VM: How to Configure Version Manager to use LDAP over SSL (LDAPS)
You cannot access this project information because the bind username or password for the LDAP server Authentication is incorrect. Please verify the LDAP connection information or contact your PVCS Version Manager administrator for further assistance.
MS-WORD PVCS 7.5.0.0 LDAP Training
This is where configuration settings for LDAP are entered. Once these settings have been entered there is a button that will test the connection to the server. Configure Project permission is required to modify the settings on this page.
HTML Merant PVCS Version Manager Release Notes
Test Connection Fails with Large LDAP Databases When testing the connection to large LDAP databases, the test may fail and return a "Sizelimit Exceeded" error. This has been fixed.
CMS-XML LDAP connection password shown unsecure in DB
LDAP connection password shown unsecure in DB
CMS-XML SDA: log4j.properties values for debugging LDAP connection issues in SDA
SDA: log4j.properties values for debugging LDAP connection issues in SDA
CMS-XML LDAP Test Connection button gives error "LDAP bind authentication failure. No such object"
After entering all of the LDAP connection information and using the Test Connection button, the system returns an error such as: LDAP bind authentication failure with dc=xxx,dc=com(&(objectClaass=user)( sAMAccountName=bob@domain.com )): 32
CMS-XML LDAP import using secure connection fails with error 81
SBM 11 fails with error message " LDAP bind authentication failure with Search Authority-Bind: 81 Server Down" The following three errors are logged in the application event log in this order: Error occurred in file:
CMS-XML Users get "Invalid User ID or Password" when login, and LDAP Test Connection gives "Operation Error"
SBM recently switched from using the Novell LDAP library to using the WinLDAP runtime. During this change, the protocol version for the bind request was changed from 3 to 2. This causes unexpected operations errors.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs