After Changing OVD 11g LDAP Adapter Ping Protocol from LDAP Back to TCP in ODSM, the Adapter no Longer Shows in ODSM and Log Shows: Error Parsing at line #0: 0.[[ org.xml.sax.SAXParseException: XML-24534: (Error) Element 'pingbindpass' not expected.
(Doc ID 1983541.1)
Last updated on NOVEMBER 24, 2019
Applies to:
Oracle Virtual Directory - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Virtual Directory (OVD) 11g 11.1.1.7.0 with Oracle Directory Services Manager (ODSM).
Initially set an OVD LDAP adapter with Ping Protocol Setting of LDAP (with credentials) in ODSM and verified it works.
After later changing it back to TCP protocol in ODSM and saving the adapter, plus restarting the processes, the following exception occurs in the wls_ods1-diagnostic.log:
[2015-02-17T19:46:15.086+00:00] [wls_ods1] [ERROR] [OVD-60373] [com.octetstring.vde.config.parsers.ConfigErrorHandler] [tid: SyncProfileMBean] [userId: <anonymous>] [ecid: <ECID>] [APP: odsm#11.1.1.2.0] [DSID: xxxxx] Error Parsing at line #0: 0.[[
org.xml.sax.SAXParseException: XML-24534: (Error) Element 'pingbindpass' not expected.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:257)
...<snip>....
In addition, the LDAP adapter is no longer visible in any ODSM Adapters or Home tabs, though it is still in the adapters.os_xml file and the Data Browser > Client View namespace entry for it still works/expands.
There is no occurrence of "pingbindpass" in the adapters.os_xml, which is expected since the protocol was switched back to the TCP default protocol. Also no occurrence of "pingbindpass" can be found in any file in the FMW home.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |