Weblogic server is not starting up ; weblogic.security.SecurityInitializationException: Authentication for user denied

-
 If the weblogic server is not starting up and giving the below error , please follow the below solution :-

Error :-


#Aug 18, 2014 12:47:25 AM PDT# #Notice# #Security# #BEA-090082# #Security initializing using security realm myrealm.#
#Aug 18, 2014 12:47:25 AM PDT# #Critical# #Security# #BEA-090403# #Authentication for user  denied#
#Aug 18, 2014 12:47:25 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied
weblogic.security.SecurityInitializationException: Authentication for user  denied
                at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
                at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
                at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
                at weblogic.security.SecurityService.start(SecurityService.java:141)
                at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User  javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
                at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
                at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
                at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                Truncated. see log file for complete stacktrace
#
#Aug 18, 2014 12:47:25 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to FAILED#
#Aug 18, 2014 12:47:25 AM PDT# #Error# #WebLogicServer# #BEA-000383# #A critical service failed. The server will shut itself down#
#Aug 18, 2014 12:47:25 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to FORCE_SHUTTING_DOWN#


Solution :-

1) Create boot.properties file in below location .
/u01/app/oracle/config/domains/Vinay/servers/AdminServer/security/boot.properties

2)Also create “security”directory if it is not there.
3) Write username & password in below format and restart the server
username=xyz
password=abc
4) If you check again boot.properties after restart , the username & password is encrypted now.

Comments

Post a Comment

Popular posts from this blog

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

ORA-22990: LOB locators cannot span transactions

-
Below is the error reported in BPEL opmn logs :- ############ <2010-02-07 10:50:59,852> <:logerror>Error while invoking bean "cube engine": Cannot update lob column.The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: BEGIN INSERT INTO cube_scope( cikey, domain_ref, scope_bin ) VALUES ( ?, ?, '0' ) RETURNING scope_bin INTO ?; END; ORABPEL-04040 Cannot update lob column. The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Oth
Read more