Cannot start Managed server from NodeManager

Hello All,
Software version installed:-
Oracle Jdeveloper 11.1.1.7
Weblogic 10.3.6
RCU:- 11.1.1.7
SOA suite:-11.1.1.7
OSB 11.1.1.7
OS windows 7 ultimate 64 bit
=====================
Sucessfully installed all the above software. I planned to install AIA Foundation Pack and for this i need to configure node manager do start
manage servers.
Node manager configuration sucessfully done by following  @http://neeraj-soa-tips.blogspot.in/2010/06/part-1-how-to-configure-node-manager-to.html
after this i am see node manger status as reachable in weblogic console.
From admin console under servers control tab, i tried starting soa_server1 but i am getting below error in nodemanger window.
java.io.IOException: Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\comm
on\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\
common\bin"): CreateProcess error=2, The system cannot find the file specified
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
        at weblogic.nodemanager.server.WLSProcessImpl.start(WLSProcessImpl.java:
44)
        at weblogic.nodemanager.server.WLSProcess.startProcess(WLSProcess.java:1
94)
        at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess_inn
er(AbstractServerMonitor.java:419)
        at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess(Abs
tractServerMonitor.java:358)
        at weblogic.nodemanager.server.AbstractServerMonitor.start(AbstractServe
rMonitor.java:103)
        at weblogic.nodemanager.server.ServerMonitor.start(ServerMonitor.java:25
        at weblogic.nodemanager.server.AbstractServerManager.startServer(Abstrac
tServerManager.java:210)
        at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:181)
        at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
        at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
        at weblogic.nodemanager.server.Handler.run(Handler.java:71)
        at java.lang.Thread.run(Thread.java:744)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
e file specified
        at java.lang.ProcessImpl.create(Native Method)
        at java.lang.ProcessImpl.<init>(ProcessImpl.java:385)
        at java.lang.ProcessImpl.start(ProcessImpl.java:136)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
        ... 13 more
I request everyone that if any one has idea on the above error then please throw light on me , this issue is really annoying me.
Also to make sure i tried starting startManagedWebLogic.cmd and sucessfull can see soa_server1 in running state.

Note that it is saying that it cannot the file
" Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\common\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\common\bin"): CreateProcess error=2, The system cannot find the file specified"
What is somewhat strange is that it is expecting startWebLogic to be present in ${WL_HOME}/common/bin/bin. The second /bin/ does not exist (well not in normal installations). Also the location of startWebLogic is odd, usually this should be present, in the ${DOMAIN_HOME}/bin directory. Could be there are some paths incorrect in JDeveloper.

Similar Messages

  • Facing error in starting managed server from nodemanager

    Hi All,
    I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
    <11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
    Can anyone please tell me what could be the issue. It is really urgent. Please help!!

    Hi Roshni,
    It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
    1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
    2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
    3. Save and close the file.
    4. Restart the Node Manager
    If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
    Thanks,
    Scott (PITSS)
    http://pitss.com/us

  • A lot of problem for an error: Cannot start Managed Server through NM

    Hi, all. Thank for coming here.
    My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
    my weblogic domain:
    Machine 1: Administration Server + 1 Managed server
    Machine 2: 1 Managed server
    all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
    output from console which was invoked startWebLogic.sh
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    And this is MS01 log:
    starting weblogic with Java version:
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Starting WLS with line:
    +/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Stopping PointBase server...
    PointBase server stopped.
    And this is output from console which node manager runs on:
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
    +<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
    Unable to start the server. start server error: java.net.BindException: Address already in use
    I cannot understand what's run on pointbase address ?
    All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
    Please help me.

    Thank Jay SenSharma.
    I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
    Please re-view my error log:
    Node Manager output:
    +<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:619)
    Managed server MS01's log:
    +<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
    +<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
    +<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
    WebLogic Server 10.3.2.0  Tue Oct 20 12:16:15 PDT 2009 1267925 >
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at java.lang.Class.forName0(Native Method)+
    +     at java.lang.Class.forName(Class.java:169)+
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
    +     ... 38 more+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     Truncated. see log file for complete stacktrace+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <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:916)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
    +<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
    +<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
    +<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
    ps:
    I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
    Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
    Edited by: Doubt_Man on Sep 10, 2010 3:54 PM

  • Error start managed server from admin console in SSL mode

    I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
    There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
    <Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
    <Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
    <Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
    <Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
    <Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
    <Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
    <Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
    <Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
    Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
    I am running everything on IBM UNIX server.
    I appriciate your help.
    Thanks & regards,
    Laxman.

    Hi
    From the admin console ... Are you able to check the status of Node Manager ?
    If yes ... please check the SSL configuration of managed servers ...
    Check the domain administration port also.
    Jin

  • How to start managed server from admin server both running

    I have an admin server on one machine and created a managed server on different
    machine, I am not able to start managed server from either machine. When I used
    the admin server machine to start the managed server remotely I got this message
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server (running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
    ed during initialization. Exception:java.lang.SecurityException: Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Thanks.

    "fkeita" <[email protected]> wrote in message
    news:[email protected]...
    >
    I have an admin server on one machine and created a managed server ondifferent
    machine, I am not able to start managed server from either machine. When Iused
    the admin server machine to start the managed server remotely I got thismessage
    >
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
    >
    Try running netstat to see whether another process is actually running at
    the given address/port.
    Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
    the box to see whether the ips addreses are correct.
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server(running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
    ed during initialization. Exception:java.lang.SecurityException:Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >Seems to be some issue with security credentials.
    Try running the manageed server directly (as sort of admin) by not passing
    the admin server url and bringing it just like an admin server.
    See if this works. If it works, then soemthing wrong in the way the admin
    server is receiving the request/security credentials from managed server.
    Also make sure both managed and admin servers are on the same patch/service
    pack level.
    -Sabha

  • How to start managed server from admin server both running on separate machines

              I have an admin server on one machine and created a managed server on different
              machine, I am not able to start managed server from either machine. When I used
              the admin server machine to start the managed server remotely I got this message
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
              ogic Managed Server "managedserver3" for domain "admindomain">
              <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
              create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
              java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
              a
              ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
              to
              bind to any port such that it is not reachable from the console.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception>
              When I tried to connect managed server from its machine to admin server (running
              on separate machine ) I got this error
              Starting WebLogic Server...
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
              ed during initialization. Exception:java.lang.SecurityException: Authentication
              for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              The WebLogic Server did not start up properly.
              Exception raised:
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Reason: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Thanks.
              

              I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
              server, but it did not work, and got error messages. Error messages are posted
              on my first posting.
              "pankaj" <[email protected]> wrote:
              >Use the startManagedWeblogic.cmd / .sh script to start your
              >Managed/Clustered servers
              >
              >
              >"fkeita" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> I have an admin server on one machine and created a managed server
              >on
              >different
              >> machine, I am not able to start managed server from either machine.
              >When I
              >used
              >> the admin server machine to start the managed server remotely I got
              >this
              >message
              >>
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
              ><Starting WebL
              >> ogic Managed Server "managedserver3" for domain "admindomain">
              >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
              ><Unable to
              >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
              >port:
              >8002.
              >> java.net.BindException: Cannot assign requested address: JVM_Bind
              >Perhaps
              >the
              >> a
              >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
              >port
              >8002.>
              >>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
              >failed
              >> to
              >> bind to any port such that it is not reachable from the console.>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception>
              >>
              >> When I tried to connect managed server from its machine to admin server
              >(running
              >> on separate machine ) I got this error
              >>
              >> Starting WebLogic Server...
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
              ><Server fail
              >> ed during initialization. Exception:java.lang.SecurityException:
              >Authentication
              >> for user system denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >>
              >***************************************************************************
              >> The WebLogic Server did not start up properly.
              >> Exception raised:
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> Reason: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >>
              >> Thanks.
              >
              >
              

  • Start managed server from console?

    If I try to start a new weblogic 10.3 managed server from the console then i get this error:
    "The server myserver does not have a machine associated with it.
    All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
    Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

    Hi,
    To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
    Following are the steps:
    1) Create a Managed Server (MS-1)
    2) Create a Machines (MachineA)
    3) In the above created MachineA add the MS-1 which can be done from the below console path
    Console Path:
    Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
    4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
    Path:
    wlserver_10.3/server/bin/
    5) Now you can try to start your MS-1 using the Admin Console.
    Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
    Topic: NodeManager is not reachable
    http://middlewaremagic.com/weblogic/?p=5205
    Topic: Common NodeManager Issues in WebLogic
    http://middlewaremagic.com/weblogic/?p=2887
    Regards,
    Ravish Mody

  • Starting Managed Server from Administration Console

    Hi
    I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
    I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
    But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
    Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    java.lang.ClassNotFoundException
    Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    java.lang.ClassNotFoundException
    I start the services in below order
    Weblogic Server
    node Manager
    and
    soa_server
    Thanks
    Hari

    you must set to true the StartScriptEnabled property in nodemanager.properties

  • Error when trying to start managed server from node manager

    I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
    Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
    Thanks
    <Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
    <Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
    <Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
    <Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
    <Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
    at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
    at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
    at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
    at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
    at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
    at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
    at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    Reason: com/taxware/twe/util/crypto/CryptoUtil                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Found a workaround:
    Manually, add PATH (and probably the other environment variables also) to
    ${WLS_HOME}/common/bin/commEnv.sh.

  • Not able to start managed server from command prompt

    Hi,
    I am trying to start manged server from command prompt. The command i am using is as follows:
    startManagedWebLogic.cmd MS1 [http://]&lt;Listen_Address&gt;:&lt;Admin_port&gt;
    Where MS1 is the name of my managed server.
    But i am getting following exceptions:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on C:\bea\user_pr
    ojects\domains\PB530Domain\servers\AdminServer\tmp\AdminServer.lok. Server may a
    lready be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
    va:159)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
    va:58)
    at weblogic.management.internal.DomainDirectoryService.start(DomainDirec
    toryService.java:73)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
    ager.java:459)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
    icesManager.java:164)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:711)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:482)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:440)
    at weblogic.Server.main(Server.java:67)
    >
    <Feb 10, 2009 6:48:16 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FAILED>
    <Feb 10, 2009 6:48:16 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical
    service failed. The server will shut itself down>
    <Feb 10, 2009 6:48:16 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FORCE_SHUTTING_DOWN>
    Please help me to resolve this issue.
    thanks,
    Sonal
    Edited by: [email protected] on Feb 10, 2009 5:16 AM

    Looking at your error message a little closer, I don't believe it has anything to do with port conflicts but rather that even though you are executing the startManagedWeblogic.cmd with your managed server name (MS1), the error indicates that it is trying to start the Admin Server (not MS1). Note in your error message the following: Unable to obtain lock on C:\bea\user_pr
    ojects\domains\PB530Domain\servers\AdminServer\tmp\AdminServer.lok. Server may a
    lready be running
    It is saying that it cannot start the Admin Server because it is already running (which is probably true in your case). Have you made any changes to the startManagedWeblogic.cmd or the startWeblogic.cmd scripts? I would start debugging there and try to figure out why the script is trying to start your admin server instead of MS1 as you requested on the cmd line.

  • Starting managed server with nodemanager

    Hi there,
    Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
    (1) set up the main server and able to run the server successfully.
    (2) set up one managed server, set up one machine on same server as main server.
    (3) assign machine to created managed server.
    (4) after that i've tried to run that managed server and error giving as below:
    Error from main server terminal
    ===================
    <NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
    Error from Node Manager Termal
    ====================
    <Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
    <Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    at java.lang.Thread.run(Thread.java:619)
    Thanks in advance,
    Tim

    Sorry , i forgot to mention that the OS i am using is Solaris.
    Thx

  • How to start managed server from console?

    Hi,
    After several unsuccesful attempts to start a managed server from admin console,
    which starts fine by script and stops by console, can somebody please mail me
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute or not. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

    The ServerStart element should look like below (WLS6.1sp1+). Using absolute
    path is definitely OK. Please provide us more info if you still have this
    problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
    especially config and <mgr'ed server name>_error.log
    <ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
    ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
    blogic.jar"
    Name="Server-1005280911753"
    OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
    005280991998.log"
    RootDirectory="d:\bea\load1"
    SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
    "Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
    >
    Hi,
    After several unsuccesful attempts to start a managed server from adminconsole,
    which starts fine by script and stops by console, can somebody please mailme
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute ornot. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

  • Problems starting managed server from admin console WL70 portal

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

  • HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

    hi all, i am trying to start a managed server using nodeManager, but i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for
    server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
    send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
    to negotiate an acceptable set of security parameters.. Please ensure that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try to start
    the managed server via adminserver console, i got the exception mentioned in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver, and
    nodemanager is supposed to run at localhost:5555 (and indeed it does, because
    ihave started it successfully).
    thanx in advance and regards marco

    Marco.
    Sorry, this is not a solution to your problem but i am trying to solve the same
    problem for a week now.
    I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
    same error. I know that the default certificate installed provides a hostname
    verification of weblogic.com. I turned the hostname verification off, i put in
    the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
    error when starting the managed server. I went ahead and created my own certificate
    for machine called mallik, created my own passphrase, created a new keystore,
    made the admin server view the keystore, used the same certificate for both the
    admin server and the node manager. It still fails with the same error. I went
    ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
    totally confused now what needs to be done.
    My nodeManger.hosts looks like this:
    mallik 10.100.10.130
    managedServer1 10.100.10.130
    managedServer2 10.100.10.13
    Below is the startNodeManager.cmd.
    @echo off
    @rem *************************************************************************
    @rem This script can be used to start the WebLogic NodeManager
    @rem
    @rem This script sets the following variables before starting the NodeManager:
    @rem
    @rem WL_HOME - The root directory of your WebLogic installation.
    @rem NODEMGR_HOME - The home directory for this NodeManager instance.
    @rem JAVA_HOME - Location of the version of Java used to start WebLogic
    @rem Server. This variable must point to the root directory of
    @rem a JDK installation and will be set for you by the
    @rem          installer. See the WebLogic platform support page
    @rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
    list of
    @rem supported JVMs on Windows NT.
    @rem PATH - Adds the JDK and WebLogic directories to the system path.
    @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
    @rem JAVA_OPTIONS - Java command-line options for running the server. (These
    @rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    @rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    @rem -client, etc.)
    @rem MEM_ARGS - The variable to override the standard memory arguments
    @rem passed to java
    @rem
    @rem *************************************************************************
    SETLOCAL
    set WL_HOME=C:\bea7.0\weblogic700
    set NODEMGR_HOME=%WL_HOME%\common\nodemanager
    set JAVA_HOME=C:\bea7.0\jdk131_06
    Call %WL_HOME%\common\bin\commEnv.cmd
    @rem If NODEMGR_HOME does not exist, create it
    :checkNodeManagerHome
    if exist %NODEMGR_HOME% goto checkJava
    echo.
    echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
    mkdir %NODEMGR_HOME%
    @rem Check that java is where we expect it to be
    :checkJava
    if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
    echo The JDK wasn't found in directory %JAVA_HOME%.
    echo Please edit this script so that the JAVA_HOME
    echo variable points to the location of your JDK.
    goto finish
    :runNodeManager
    if not "%JAVA_VM%" == "" goto noResetJavaVM
    rem set JAVA_VM=-hotspot
    set JAVA_VM=%COMM_VM%
    :noResetJavaVM
    if not "%MEM_ARGS%" == "" goto noResetMemArgs
    set MEM_ARGS=-Xms32m -Xmx200m
    :noResetMemArgs
    @echo on
    set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    cd %NODEMGR_HOME%
    #"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
    "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
    "%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
    "-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
    "-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
    "-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
    goto finish
    :finish
    ENDLOCAL
    I would appreciate if anybody can help me.
    Mallik.
    "Marco" <[email protected]> wrote:
    >
    hi all, i am trying to start a managed server using nodeManager, but
    i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for
    server managedServer via the Node Manager - reason: [CommandInvoker:
    Failed to
    send command: 'online to server 'managedServer' to NodeManager at host:
    'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
    was unable
    to negotiate an acceptable set of security parameters.. Please ensure
    that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
    at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
    -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost
    and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try
    to start
    the managed server via adminserver console, i got the exception mentioned
    in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver,
    and
    nodemanager is supposed to run at localhost:5555 (and indeed it does,
    because
    ihave started it successfully).
    thanx in advance and regards marco

  • Cannot start managed server via WLST - 'Overriding the ListenPort ...'

    Hello everyone
    I've created a development domain that has two machine, each of them has two weblogic server instances. On machine-2, I've started NodeManager already.
    I started WLST tool, connect to AdminServer and invoke 'start' command to start managed server on machine-2:
    start('MS-02','Server','t3://dvc.danang.vn:7003')
    but I get fail message like that
    wls:/dnict_domain/serverConfig> start('MS-02','Server','t3://dvc.danang.vn:7003')
    Overriding the ListenPort or ListenAddress is not supported.
    WLST will use the ListenPort and ListenAddress that are configured on the ServerMBean
    Starting server MS-02 ....Permission denied (publickey,password).
    Traceback (innermost last):
      File "<console>", line 1, in ?
      File "<iostream>", line 1280, in start
      File "<iostream>", line 1744, in raiseWLSTException
    WLSTException: Error occured while performing start : Error starting the server : Error occured while performing start : Server with name MS-02 failed to be started 
    Use dumpStack() to view the full stacktrace
    wls:/dnict_domain/serverConfig> dumpStack()
    This Exception occurred at Sun Oct 09 18:46:16 ICT 2011.
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be started
         at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
         at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleHandler.java:501)
         at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.java:477)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.python.core.PyReflectedFunction.__call__(Unknown Source)
         at org.python.core.PyMethod.__call__(Unknown Source)
         at org.python.core.PyObject.__call__(Unknown Source)
         at org.python.core.PyObject.invoke(Unknown Source)
         at org.python.pycode._pyx21.start$80(<iostream>:1270)
         at org.python.pycode._pyx21.call_function(<iostream>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyFunction.__call__(Unknown Source)
         at org.python.pycode._pyx28.f$0(<console>:1)
         at org.python.pycode._pyx28.call_function(<console>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyCode.call(Unknown Source)
         at org.python.core.Py.runCode(Unknown Source)
         at org.python.core.Py.exec(Unknown Source)
         at org.python.util.PythonInterpreter.exec(Unknown Source)
         at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at weblogic.management.scripting.WLST.main(WLST.java:180)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.WLST.main(WLST.java:29)
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be startedI'm wondering about "Permission denied (publickey,password)" error. Can you show me how to fix this issue?
    Any suggestion is appreciated
    Regards
    Cuong Pham

    Try removing the 't3://dvc.danang.vn:7003' argument. If this information is configured in the managed server, its unnecessary.
    Also, is the NodeManager registered with the AdminServer? You can use the command "nmEnroll([domainDir], [nmHome])" while connected to the AdminServer to if its not.

Maybe you are looking for

  • Master-Detail Relationship problem

    I've spent 1.5 days already trying to solve this problem. I'm creating a JClient application using BC4J with a Master-Detail relationship. The relationship between tables is a many-to-many thru an intersection table. I've gotten my master and detail

  • Issue with Outlook 2013-Notifications from published Calendar

    Hi Every body, I'm setting up for my little company published calendars on a Webdav servers (i'm using IIS on a 2003 server and Office 2013). Publishing calendar works fine so far. But i'm facing up a real issue: When a user add other's published cal

  • Select columns in ALV

    Hi, I'm using the 'SALV_WD_TABLE' component. Is it possible to select a column of the ALV by clicking on the column header and initiate an event? Or is it possible to set the header text as a link and define an action for it? Thanks, Anett

  • SNMP traps from BPEL

    Hi I have a requirement to send SNMP traps from BPEL. I am using FMW11.1.1.3 over weblogic. I was going through some documentation where i could see that SNMP traps can be created from the Weblogic Server console. Can some one help me on how to gener

  • My nokia 6230 turns off without cause!?

    my nokia keeps turning off, i am reasonably sure it is not the battery as this problem occours while charging aswell as without charging. Also occasisonally, it doesn't turn off completely, just goes onto a white screen and can only be stopped my the