Admin Server Fails to Start in Development or Production Mode After Regenerating SerializedSystemIni.dat File in WebLogic Server
Last updated on SEPTEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.1 and later
Information in this document applies to any platform.
Using Oracle WebLogic Server and having difficulties starting the Admin Server due to a login isssue. In the midst of troubleshooting, it was decided to replace all the encrypted text values specified between <credential-encrypted> tags to clear text values in the config.xml file to test the start up. This still fails, and this exception is seen in the Admin Server log file:
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
As a next step, the domain mode was changed back to development mode by setting the <production-mode> tag to false in config.xml and in the setDomainEnv.sh file. Upon doing this, the Admin Server starts but after accessing the Admin Console, attempting to change back the domain mode to production, the restart fails again. This time, the following error is seen:
<Warning> <Management> <BEA-141191> <The prepare phase of the configuration update failed with an exception. weblogic.descriptor.DescriptorException: Unmarshaller failed
At this point, the Admin Server is not starting and seems to be stuck in this inconsistent state.
After circling back to diagnose this issue properly, it was found that before seeing these errors, <Note 1602857.1>, "How to Recover SerializedSystemIni.dat File?" was followed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms