Unable to start managed server using Nodemanager – SecurityProvider service class name for OAMIDAsserter is not specified.

Problem:

Error “SecurityProvider service class name for OAMIDAsserter is not specified” while starting managed server from weblogic admin console. Node manager is up and running.

Below has been logged in managed server log

<Jun 28, 2017 6:55:06 AM CDT> <Notice> <Log Management> <BEA-170019> <The server log file /u01/mw_home/user_projects/domains/mydomain/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
<Jun 28, 2017 6:56:09 AM CDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OAMIDAsserter is not specified..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OAMIDAsserter is not specified.
 at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
.
.
Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OAMIDAsserter is not specified.
 at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
.
.
Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OAMIDAsserter is not specified.
.
.
>
<Jun 28, 2017 6:56:09 AM CDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 28, 2017 6:56:09 AM CDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:917)
.
.
>
<Jun 28, 2017 6:56:09 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

 

Node manager Log
<May 12, 2017 9:41:13 AM> <INFO> <ksiamdomain> <soa_server1> <Server failed during startup so will not be restarted>
May 12, 2017 9:41:13 AM weblogic.nodemanager.server.AbstractServerManager log
INFO: Server failed during startup so will not be restarted
<May 12, 2017 9:41:13 AM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
.
.
May 12, 2017 9:41:13 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'soa_server1'
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)

 

Cause:

This is due to parameter StartScriptEnabled not set in nodemanager.properties file.

 

Solution:

Run the following script to add the property StartScriptEnabled=true to the nodemanager.properties file:

ORACLE_COMMON_HOME/common/bin/setNMProps.sh

Start the Node Manager by executing the following command:

WL_HOME/server/bin/startNodeManager.sh

oracle@myserver:/u01/mw_home/oracle_common/common/bin $ ./setNMProps.sh
Appending required nodemanager.properties

 

oracle@myserver:/u01/mw_home/wlserver_10.3/common/nodemanager $ cat nodemanager.properties
#Wed Oct 05 12:06:13 CDT 2016
DomainsFile=/u01/mw_home/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/u01/mw_home/java
AuthenticationEnabled=true
NodeManagerHome=/u01/mw_home/wlserver_10.3/common/nodemanager
JavaHome=/u01/mw_home/java/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=false
LogFile=/u01/mw_home/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50

#Required NM Property overrides (append to existing nodemanager.properties)
StartScriptEnabled=true

Start Node manager and start server from weblogic admin console.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s