JPS-02592: Failed to push ldap config data to libOvd

JPS-02592: Failed to push ldap config data to libOvd

Getting below error in logs “JPS-02592: Failed to push ldap config data to libOvd for service instance “idstore.ldap” in JPS context “default”, cause: org.xml.sax.SAXPar”

ERROR:

<Feb 2, 2018 3:03:14 AM UTC> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception st

ack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information

. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance “idstore.ldap” in JPS context “default”, cause: org.xml.sax.SAXPar

seException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>

<Feb 2, 2018 3:03:14 AM UTC> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance “idstore.ldap” in JPS context “default”, cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance “idstore.ldap” in JPS context “default”, cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.

at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)

at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)

at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)

at weblogic.security.SecurityService.start(SecurityService.java:141)

SOLUTION:

The ‘adapters.os_xml’ file has become corrupted which resides under :

..\Oracle\Middleware_Home\user_projects\domains\EPMSystem\config\fmwconfig\ovd\default

The file size is zero when compared to the working file (i.e. 3KB).

Step 1: Make sure Weblogic Admin Server is stopped correctly,  Check processes and ‘kill’ any running java process for Weblogic Admin Console.

Step 2: Delete the adapters.os_xml file in the directory:

..\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\ovd\default

Step 3: Replace the corrupted adapters.os_xml file either by:

3a. Obtain backup copy from last backup and replace in:

..\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\ovd\default

OR

3b. If no backup copy available – copy adapters.os_xml

From:  ..\Oracle\Middleware\oracle_common\modules\oracle.ovd_11.1.1\domain_config\ovd\default

To:      ..\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\ovd\default

Step 4: Start Weblogic Admin Server

Step 5: Start all EPM web applications.

For more such weblogic issues and resolution click here.

Latest Weblogic Interview Questions and Answers