<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure

d21e212f-e7c9-4b03-90a9-c658c911541a

Friends,

Getting below error when i restart the server.

<Dec 31, 2014 5:33:58 AM EST> <Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>

<Dec 31, 2014 5:34:07 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException>

<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

<Dec 31, 2014 5:34:07 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>

<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

I have changed the jar files path in build.properties file as its required to import new jars as part of Documentum server upgradation. But getting above errors.. Do i have to update Config.xml file or any other file.. Please suggest.

MarioCadiz-Oracle

For the registry, I had the same issue today, related to [wlsdomain]/security/SerializedSystemIni.dat

In some cases, that file is corrupted, so you should try to restore it from a copy.

If there is no copy, try these steps: How to Recover SerializedSystemIni.dat File? (Doc ID 1602857.1)

My case was pretty simple, WLS had no access to that file cause somehow permissions were changed.

Example:

----rwxrwx  1 oracle oracle    64 Oct  4 16:09 SerializedSystemIni.dat

so solution was restoring the permissions:

chmod 640 SerializedSystemIni.dat

But how critical is this file for WLS ?

The SerializedSystemIni.dat file contains the hashes for the passwords. It is associated with a specific WebLogic domain so it cannot be moved from domain to domain.

If the SerializedSystemIni.dat file is destroyed or corrupted, you must reconfigure the WebLogic domain. Therefore, you should take the following precautions:

    * Make a backup copy of the SerializedSystemIni.dat file and put it in a safe location.

    * Set permissions on the SerializedSystemIni.dat file such that the system administrator of a WebLogic Server deployment has write and read privileges and no other users have any privileges.
Ref: https://docs.oracle.com/cd/E28280_01/web.1111/e13707/domain.htm#SECMG412