Number Format Exception while starting WebLogic Server

This usually happens if your machine is running low on space and WebLogic Server corrupted a file in the embedded LDAP.

To fix this problem you can delete the file %DOMAIN_HOME%/servers/AdminServer/data/ldap/conf/replicas.prop or add ‘replica.num=0′ to the 0 byte replicas.prop file.

<May 23, 2011 8:24:21 PM UTC> <Notice> <Log Management> <BEA-170019> <The server log file c:\oracle\Middleware\user_projects\domains\base_domain\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<May 23, 2011 8:24:23 PM UTC> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
        at java.lang.Integer.parseInt(Integer.java:415)
        at java.lang.Integer.parseInt(Integer.java:497)
        at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
        at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace