The Loading Of OPSS Java Security Policy Provider Failed Due To Exception.Admin Server Will Not Start

After installing OUD with weblogic using LCM tool we get this error while starting Admin Server. The error says "The Loading Of OPSS Java Security Policy Provider Failed Due To Exception".

ISSUE:
Admin Server fails to start with the message "server state to change to FORCE_SHUTTING_ DOWN".

Error Observed:

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>

<Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>

 <Notice> <LoggingService> <BEA-320400> 

 <Notice> <LoggingService> <BEA-320401>

 <Notice> <Log Management> <BEA-170019> 

<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: Cannot read from policy store. Reason is PolicyStore Error, javax.xml.stream.XMLStreamException: End Document reached prematurely.>

        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:873)

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

        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

        Truncated. see log file for complete stacktrace

 <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

 <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>

<Sep 30, 2015 7:25:37 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

CAUSE:
The "<Domain_Home>/config/fmwconfig/system-jazn-data.xml" file is corrupted.

SOLUTION:
1) Restore the "system-jazn-data.xml" from the most recent backup.
2) Copy the default "system-jazn-data.xml" from location 
"<Middleware_Home>\oracle_common\modules\oracle.jps_11.1.1\domain_config" to location 
"<Domain_Home>\config\fmwconfig" and restart the server. 

Note: Please try anyone of the solution at a time and perform the restart. In my case both the solution work.