HELP! WebLogic won't start - "wlDefaultKeyStore.jks does not exist"

Question

Hi,
I am having the same problem with 3 different WebLogic installations not being able to start.
All of them are WebLogic 8.1 SP2, with two running under Windows 2000, and one installation under Solaris 9 SPARC.
What happens is that when I execute startWebLogic.sh/cmd, I see a msg that says "wlDefaultKeyStore.jks does not exist". Then I get a bunch of Java errors & stack traces, and finally a msg that says that WebLogic couldn't start because the username/password in boot.properties is no good.
I believe that what is happening is that for some reason, the keystore that WebLogic uses is suddenly either gone or unuseable, and then the "boot.properties" problem is a CONSEQUENCE of the problem with the keystore.
As I mentioned, this exact problem is occurring with 3 different systems, and I KNOW for sure that the boot.properties have not been altered by anyone.
The two test systems under Windows haven't been started in awhile, but the 3rd system on Solaris was in use probably a couple of weeks ago.
Has anyone encountered this problem before? I'm wondering if maybe something (I don't know what) expired.
Here's the log msgs:
<Feb 2, 2006 11:25:39 AM EST> <Info> <Security> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
<Feb 2, 2006 11:25:39 AM EST> <Info> <Security> <BEA-090143> <The WebLogic keystore provider DefaultKeyStore in security realm theRealm cannot be used for private keys because its configured private key keystore file wlDefaultKeyStore.jks does not exist.>
<Feb 2, 2006 11:25:39 AM EST> <Info> <Security> <BEA-090142> <The WebLogic keystore provider DefaultKeyStore in security realm theRealm cannot be used for trusted (root) CAs because its trusted (root) CA keystore was not configured.>
<Feb 2, 2006 11:25:39 AM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm theRealm.>
<Feb 2, 2006 11:27:15 AM EST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
PLEASE, if anyone has any idea about what might be causing this, please post them, as I now have 3 essentially dead systems!!
Thanks,
Jim

Answer 1

Hi Hoos,
I've resolved the problem, in my case, at least. It turns out that the "jks" msgs were a "red herring", i.e., they weren't related to the problem with WebLogic not starting. In fact, even after I fixed my startup problem, I still got that jks msgs, so I think that those msgs were always there, and I just never noticed them.
Ok. As for the startup problem, it turns out that I had created a 2nd security realm (for a 3rd party SSO product) in WebLogic, and WebLogic was attempting to authenticate the user "weblogic" against my own security realm instead of the original default "myrealm". It also turns out that the "weblogic" user's password had expired on my own realm, and so the authentication would fail :(... thus causing WebLogic to not start!!
Jim