Having problems removing a managed server from WL console

Background:
Running the 11 g R1 (11.1.1.5) server on Linux.
Installed OIM, OAM, OVD, OID, WL. (other components may be added later)
Have not yet integrated OIM and OAM.
The Problem:
We were running into a problem on our oim server, that warranted removal and reinstallation.
we were attempting to remove the oim_server1 instance from the weblogic admin console.
went to deployments, and deleted the entry there for oim_server1
Then went to environment | servers
     The oim_server1 now shows as "FAILED_NOT_RESTARTABLE"
     and we can not remove this instance frome the admin instance.
     If we attempt to remove it, It gives the errors
          The server oim_server1 is a running server and may not be deleted.
          All of the servers selected are in a state which is incompatible with this operation.
Restarted the WL Admin server, then went back into the console. This did not change the status of the managed server.
Tried going to
/data01/app/oracle/product/Middleware/user_projects/domains/IDMDomain/servers/oim_server1/tmp
and removing the *.lok file...
No luck.
How do we get around this, so we can remove the incorrectly configured oim_server1 ?
Edited by: 992276 on Mar 6, 2013 11:30 AM

i was in the EXACT same situation but on weblogic 10.3.3.
* two servers in FAILED_NOT_RESTARTABLE
* try to delete them from admin console and i get the "is a running server and my not be deleted..../incompatible with this operation" messages
i tried lots of things and but i could not get rid of those servers.
### What ended up working. ###
i just started the servers. there is no way they should have started. i had already even deleted the server directories. but they started. and then i shut them down. and at that point i was able to delete them.
hope this helps you or somebody. it seemed like such an unlikely solution. but it worked for me.
Edited by: user8825653 on Mar 15, 2013 8:25 AM

Similar Messages

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

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.

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

Unable to start Managed server from admin console using nodemanager

I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman

Configure Managed Server from Admin Console - Java arguments

Hi There;
I am configuring a managed server from the admin console and the one item that me up is when I add the following into the Arguments sections:
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol'|'oracle.fabric.common.classloaderurl.handler'|'oracle.fabric.common.uddiurl.handler'|'oracle.bpm.io.fs.protocol.
Note The command line script used double quotes (") but the console gave an error - Arguments may not contain '"' This sounded reasonable so I switched the double quotes to single quotes.
Switching to single quotes allowed me to bypass the error.
The managed server fails when I start it from the console:
Error message:
oracle.fabric.common.classloaderurl.handler ' is not recognized as an internal or external command, operable program or batch file.- it is like it ignores the values after the single quotes and fials.
How can I configure this parameter?
note: I am running weblogic 10.3.6 on widows 2008. it is a SOA Managed Server I am trying to setup to run from the Admin Console.
J

Try leaving out the quotes
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol
See also the documentation: URL (Java Platform SE 7 ) "interpreted as a list of packages separated by a vertical slash character |"

Having problems starting Weblogic Managed Server

Hi,
I am new to WebLogic and I was looking at the webservices examples in samples dir and I took the example and just moved it to one of my currently deployed Web Application folder and changed the dir strutcure instead of the samples dir strutcure, compiled and deployed as standalone Application(not as part of my currently deployed Web App). It worked fine.
Then since there would be a need for reuse of lot of the current Web App. in the web services we are trying to implement, I tried to put the ear that got created in the WEB-INF/lib of the currently deployed exploded dir. It was pretty dumb to put the ear there, just thought, worst case it wont work, I thought I could pull the ear out of there. But seems like this changed the entire config.xml and ever since that my admin server got changed to myserver, I corrected all the problems with the admin server and admin server and node server they come up just fine. When trying to bring up Managed server, I get the following excpetion
Jul 16, 2004 4:00:37 PM EDT> <Debug> <HTTP> <BEA-101158> <Exception thrown while loading epic_dev: java.lang.NullPointerException
java.lang.NullPointerException
     at weblogic.utils.enumerations.FileEnumeration.getNextFile(FileEnumeration.java:155)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreFiles(FileEnumeration.java:102)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreElements(FileEnumeration.java:134)
     at weblogic.utils.jars.ExplodedJarFile$1.hasNext(ExplodedJarFile.java:112)
     at weblogic.utils.classloaders.ExtractionHelper.extractClassFiles(ExtractionHelper.java:117)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5119)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:4991)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:560)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:511)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:594)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:623)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:2896)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
<Jul 16, 2004 4:00:37 PM EDT> <Info> <Deployer> <BEA-149061> <Module epic_dev of application appsdirepic_dev_dir failed to transition from unprepared to prepared on server betsy_dev.>
<Jul 16, 2004 4:00:37 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application appsdirepic_dev_dir due to error weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
Could someone help me with resolving this.(This is only the dev machine, I played thannkfully!).
And also would like to get suggestions on setting up the new webserverces that we are trying to do. If I need to reuse lot of class files from current appl., how do i go about implementing this webservice? Should this be part of the existing application? or Web service could be a separate application and somehow we could look at the web app which is in the same domain.
Any help is appreciated.
Thanks
Anna

There was an access problem in the application I was trying to deploy and it had nothing to do with EAR file, once the access problem is taken care of, I could deploy the app just fine.

Starting managed server from admin console

          Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
          I did the same way as you said here but still getting following error.....Could you
          address me where I did a mistake
          Starting WebLogic Server ....
          Connecting to http://localhost:7001...
          <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
          Server "MyServer1" for domain "mydomain">
          <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
          'Fatal initialization exception
          Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          Start server side stack trace:
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          ***************************************************************************Start
          server side stack trace:
          java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          '>
          The WebLogic Server did not start up properly.
          Exception raised: weblogic.management.configuration.ConfigurationException: connecting
          to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
          [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
          HTTP to server: 'localhost', port: '7001']
          java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
          to server: 'localhost', port: '7001'
          at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
          at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
          at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
          at weblogic.net.http.HttpClient.New(HttpClient.java:149)
          at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
          at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
          at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          --------------- nested within: ------------------
          weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
          - with nested exception:
          [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
          HTTP to server: 'localhost', port: '7001']
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          Reason: Fatal initialization exception
          <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
          online successfully invoked on server 'MyServer1', pid: 1892>


Change the "Listen Address" attribute of the admin server to be its machine
          name or IP address. I think you currently have it set to "localhost".
          Hopefully this should fix atleast one of the exceptions below.
          -- Anand
          "Janavi" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
          >
          > I did the same way as you said here but still getting following
          error.....Could you
          > address me where I did a mistake
          >
          >
          > __________________________________________
          > Starting WebLogic Server ....
          > Connecting to http://localhost:7001...
          >
          > <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
          Managed
          > Server "MyServer1" for domain "mydomain">
          > <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
          the server:
          > 'Fatal initialization exception
          > Throwable: java.lang.ClassCastException:
          weblogic.security.acl.DefaultUserInfoImpl
          >
          >
          > Start server side stack trace:
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          > at
          weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          > at
          weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
          a:164)
          >
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          >
          >
          ***************************************************************************S
          tart
          > server side stack trace:
          > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
          > at
          weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
          > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
          > at
          weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
          a:164)
          >
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > <<no stack trace available>>
          > '>
          >
          > The WebLogic Server did not start up properly.
          > Exception raised:
          weblogic.management.configuration.ConfigurationException: connecting
          > to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
          exception:
          >
          > [java.net.ConnectException: Tried all: '1' addresses, but could not
          connect over
          > HTTP to server: 'localhost', port: '7001']
          > java.net.ConnectException: Tried all: '1' addresses, but could not connect
          over HTTP
          > to server: 'localhost', port: '7001'
          > at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
          > at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
          > at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
          > at weblogic.net.http.HttpClient.New(HttpClient.java:149)
          > at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
          > at
          weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
          9)
          >
          > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > --------------- nested within: ------------------
          > weblogic.management.configuration.ConfigurationException: connecting to
          http://localhost:7001/wl_management_internal2/Bootstrap
          > - with nested exception:
          > [java.net.ConnectException: Tried all: '1' addresses, but could not
          connect over
          > HTTP to server: 'localhost', port: '7001']
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          >
          > t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > End server side stack trace
          >
          > <<no stack trace available>>
          > Reason: Fatal initialization exception
          >
          > <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
          <WindowsProcessControl:
          > online successfully invoked on server 'MyServer1', pid: 1892>
          > _______________________________________
          >

How do I remove an unwanted server from the console window?

Hi all, hope someone can help, as I'm rapidly running out of hair to pull out :-(
I have one upstream server, set up perfectly on Windows Server 2012, and six downstream servers all running Windows Server 2008 R2 Enterprise. Five of my downstreams are set up and working as expected, but one is behaving a little strangely.
Here is an example of one of my downstream servers which is configured correctly:
Just showing the upstream server, as you would expect.
Now here's my problem downstream server:
As you can see, not only does it list the upstream server, as expected, it also shows itself as a server. I have tried right-clicking it and choosing 'Remove from Console', but it just comes back after closing and reopening the console.
Any advice would be greatly appreciated,
Carl...

On all downstream servers, except ServerDOWN4 only the ServerUP01 is seen in the WSUS console. On ServerDOWN4, you can see ServerUP01 and ServerDOWN04 in the WSUS console.
Is this normal?
No, and the short answer here is that apparently the consoles were configured to connect to the wrong server, and on 'DOWN4', TWO servers were configured in the console.
But here's a more significant question....
Why, on WS2012 and WS2008R2 servers are you using the standalone console anyway? If you use
SERVER MANAGER, which is the expected behavior, the *LOCAL* server will be automatically displayed.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

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

Restart Managed Server from Adminserver FAILED_NOT_RESTARTABLE

Hi all,
I've got problems restarting the managed server from the adminkonsole ('Control'-Tab) and from within wlst while connected to the adminserver 'start('mymanaged','Server','t3://localhost:80', block='true') connected with the adminserver.
In the logfile of the administration occurs a nullPointerException:
java.lang.NullPointerException
     at javax.mail.internet.MimeUtility.decodeText(MimeUtility.java:480)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.mimeDecode(DeploymentServiceServlet.java:788)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.authenticateRequest(DeploymentServiceServlet.java:523)
     at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:194)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
The nodemanager-log shows an IOException:
<02.02.2007 12:08:42> <Warning> <Exception while starting server 'sunetweb': 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:246)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:463)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run()V(Unknown Source)
In the console, the serverstate of the managed server is:
FAILED_NOT_RESTARTABLE
But in config.xml both servers have set auto-restart:true.
Starting from within wlst connected to Nodemanager instead works (nmStart("mymanaged", 'c:/win32app/bea/user_projects/domains/mydomain').
Also the serverstart with a command file works.
I want to restart the managed server from the console and from wlst connected to admin server.
What is wrong ?
Thanks, kind regards,
Thomas

Hi Jin,
I use wlst now to do what I want.
For a gentle restart of the managed server I connect to the Administration server and then run:
#shutdown mymanaged gently
shutdown(name='mymanaged',entityType='Server',ignoreSessions='true',timeOut=5, force='false')
#start the sever again
start('mymanaged','Server','t3://localhost:80', block='true')
Still it is not possible to restart the managed server from console (stopping works).
But wlst works for me.
I won't follow this problem further.
Thanks a lot.
Kind regards,
Thomas

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

Hi I am having problems removing mail from trash folder. Can anyone help please

Hi I am having problems removing mail from trash folder. I can send mails to the folder but cannot delete them permanently from the trash folder. I am using Iphone 3G and anm up to date with OS. Can anyone help please

Check that there isn't a different Trash folder to the one with the proper Trash symbol on it.
If you see one in your list of folders rather than a separate one, highlight it, then click on Mailbox...Use this mailbox for...Trash

I recently had to swap out my iphone 4s and I am having problems restoring photos and videos from icloud. I get a message on my phone that says " the URL you are requesting is not found on this server". Pics and videos have been deleted too.

I recently had to swap out my iphone 4s and I am having problems restoring photos and videos from icloud. When I restored my phone from icloud, half of my pics and videos have been deleted, the pics that were restored on my phone are very blurry, and the videos won't play. I get a message on my phone that says " the URL you are requesting is not found on this server". I have erased and reset my phone twice, but every time I do it, more pics and videos are deleted. I have backed up to icloud and iphoto, however, some of the pics are no longer on iphoto either. Is there someway to get the videos to play on my phone again? Make the photos not as blurry as they are now and to restore the pics and videos that have been lost? I really would love to have them back, this phone is supposed to be the best and right now it doesn't seem to be. Please help if you can.

I too have noticed that once i restored from iCloud. Pictures blurry and videos wont play!
Need help too!!

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

Having problems removing a managed server from WL console

Similar Messages

Maybe you are looking for