Today one of my customer was trying to start the WebLogic Server ( Production Instance) , though he was trying to start the server in a standard way, but it was failing due to below error : 

 ####<Oct 22, 2012 12:14:43 PM BST> <Warning> <Security> <BanifB1> <> <main> <> <> <> <1350904483998> <BEA-090066> <Problem handling boot identity. The following exception was generated: weblogic.security.internal.encryption.EncryptionServiceException: weblogic.security.internal.encryption.EncryptionServiceException: [Security:090219]Error decrypting Secret Key java.security.ProviderException: setSeed() failed>

And it started failing into below causes.

####<Oct 22, 2012 12:16:45 PM BST> <Critical> <WebLogicServer> <BanifB1> <AdminServer> <main> <<WLS Kernel>> <> <> <1350904605837> <BEA-000386> <Server subsystem failed.

Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException

java.lang.AssertionError: java.lang.reflect.InvocationTargetException

weblogic.security.internal.encryption.EncryptionServiceException: weblogic.security.internal.encryption.EncryptionServiceException: [Security:090219]Error decrypting Secret Key java.security.ProviderException: setSeed() failed

weblogic.security.internal.encryption.EncryptionServiceException: [Security:090219]Error decrypting Secret Key java.security.ProviderException: setSeed() failed

at weblogic.security.internal.encryption.JSafeSecretKeyEncryptor.decryptSecretKey(JSafeSecretKeyEncryptor.java:121)

Customer was facing this issue without any changes in the system, it was stable suddenly started seeing this issue last night.

When we checked, customer was manually entering the username and password, config.xml had the entries encrypted

However when verified, customer had the boot.properties at the Servers/AdminServer/security folder and DomainName/security didn't have this file.

Adding boot.properies fixed the issue.

Regards

Shailesh Dyade