Stopping Managed servers in 10.3

We are testing a couple of scenarios by having various cases
case1:Start Managed Server when the admin server is Running(passed)
case2:Stop Managed Server when the Admin Server is Running(passed)
case3:Start Managed Server when the Admin is not Available (passed)
case4:Stop Managed Server When the Admin is not available(falied)
the case 4 seems to never pass until we have to find the PID and Kill server which cannot be trapped in the log files,
we have been using the stopMangedWeblogic.sh ManagedServerName adminurl to stop, but it says the SERVER is already in SHUTDOWN state when it is still shutdown,
Can anyone let me know what is this problem, where I am trying to Shutdown the Managed Server when the Admin is not available

Yeah Here are the Thread Dumps Which I took during the shutting down process these are the Threads Blocked , in all the thread Thumps its Similar
"ExecuteThread: '4' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=03189a00 nid=28 lwp_id=1217500 waiting for monitor entry [216fa000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     - waiting to lock <36030640> (a java.lang.String)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=02f7e400 nid=27 lwp_id=1217499 waiting for monitor entry [217fa000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     - waiting to lock <36030640> (a java.lang.String)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=02f0ce00 nid=26 lwp_id=1217498 waiting for monitor entry [218fa000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     - waiting to lock <36030640> (a java.lang.String)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=02e81000 nid=24 lwp_id=1217496 waiting for monitor entry [21afa000]
java.lang.Thread.State: BLOCKED (on object monitor)
     at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:93)
     - waiting to lock <36030640> (a java.lang.String)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

Similar Messages

  • Clustered enviroments -Starting/Stopping Managed servers, NodeManager & Admin server from single node

    Hi,
    We have 5 node Weblogic cluster. At the time of some mass activities like patching we have to stop all our managed, Admin Servers and node manager and it takes a lot of time to do this by logging in to all 5 managed servers and stopping all components. Though we have node manager configured so we can stop managed servers from console itself, but still have to login to each server to stop NodeManager and Oracle Http Servers.
    Things become worse when wee have to shutdown almost 15-20 instances.
    Is there a way (using wlst or shell script) that we can do all these tasks from by logging in to just one server?
    Thanks,
    Suraj

    The simple code below would shutdown all the running Servers. Some of the APIs for ex MBeanHome are deprecated..still work though..if your concerned about that..I am working on the same using JMX API..if you want I could share that too. And also as described in the below link..you can Cluster stop and start using WLST commands.  Managing the Server Life Cycle - 12c Release 1 (12.1.1)
    <This code is from Oracle Weblogic documentation>
    import java.util.Set;
    import java.util.Iterator;
    import java.rmi.RemoteException;
    import javax.naming.Context;
    import javax.management.ObjectName;
    import java.io.*;
    import java.net.*;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.WebLogicMBean;
    import weblogic.management.configuration.ServerMBean;
    import weblogic.management.runtime.ServerRuntimeMBean;
    import weblogic.management.runtime.ServerStates;
    import weblogic.management.WebLogicObjectName;
    public class ServerStopper {
      public static void stop() throws Exception {
        MBeanHome home = null;
        //url of the Admin server
        String url = "t3://localhost:7001";
        String username = "weblogic";
        String password = "welcome1";
        ServerRuntimeMBean serverRuntime = null;
        Set mbeanSet = null;
        Iterator mbeanIterator = null;
        try {
          // Set ContextClassloader to prevent assertions
          URL[] urls = { new File("/").toURL() };
          Thread.currentThread().setContextClassLoader(new
             URLClassLoader(urls));
          Environment env = new Environment();
          env.setProviderUrl(url);
          env.setSecurityPrincipal(username);
          env.setSecurityCredentials(password);
          Context ctx = env.getInitialContext();
          home = (MBeanHome)
               ctx.lookup("weblogic.management.adminhome");
          mbeanSet = home.getMBeansByType("ServerRuntime");
          mbeanIterator = mbeanSet.iterator();
          while(mbeanIterator.hasNext()) {
            serverRuntime = (ServerRuntimeMBean)mbeanIterator.next();
            if(serverRuntime.getState().equals(ServerStates.RUNNING)){
                serverRuntime.shutdown();
        } catch (Exception e) {
          e.printStackTrace();

  • Scripts for starting/stopping managed servers

    All,
    Could someone provide me with some sample scripts for starting/stopping managed Weblogic servers?  I'm specifically looking for ways to start/stop them WITHOUT starting the AdminServer.  I'm running WLS 10.3.6 on Windows Server 2003, and I have NodeManager set to start automatically as a Windows service.
    I know how to set my managed servers up as Windows services so that they will start automatically at boot, but this requires the AdminServer to be running, which I do not want.  I just want a few scripts for starting/stopping the managed servers (and maybe some hints as to how to make them start automatically without starting the AdminServer).
    Thanks in advance,
    Tom

    Hello Puneet,
    Admin console is an web application deployed into AdminServer. Hence if you shutdown AdminServer then you wouldn't able to access Admin console.
    Managed Server would function in MSI mode, however you will not be able to make any configuration or administration activities like deployment , any configuration changes , etc.
    Hello PRISM,
    Can you confirm your requirement about why you don't want AdminServer to be running?
    As I said,  you will loose the administration capability if you don't have admin server running.
    Regards
    Rosario

  • Managed servers are started/stopped from admin console using NodeManager

    Hi,
    I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
    I have node manager setup on the two machines. I use admin console to start/stop managed servers.
    Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
    I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
    I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
    In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
    Your inputs are highly appreciated.
    Thanks in advance.
    BR,
    Ajmal

    Hi Ajmal,
    For your issue there are two solution's as shown below:
    Solution-1
    You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
    Console Path:
    Servers > Configuration > Server Start
    However this has to be done with all the managed serves.
    Solution-2
    If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
    This way whenever you start any of you managed servers from console it would pick up that lib files.
    In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
    Hope this would help you.
    Regards,
    Ravish Mody

  • Unable to start Managed servers from admin console

    Hello!
    We have a problem to start Managed Servers throw Node manager.
    We get an error:
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
    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:567)
    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:662)
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    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:567)
    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:662)
    Additional information:
    weblogic 10.3.3
    PT8.51.11
    Linux x86_64 RH5
    When we starting Manged servers manualy, it's works fine.
    Thank you.

    Hello!
    The problem is found.
    We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
    The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
    So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
    ./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
    Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
    <Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
    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:567)
    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:662)
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    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:567)
    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:662)
    There are no errors in managed servers logs.
    PIA1.out:
    <Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Attempting to start WebLogic Server PIA1
    No activity will be logged to this window.
    Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
    PID for WebLogic Server PIA1 is: 27018
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
    <Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
    What can be the reason?
    Thank you.

  • Command for STOPPING  admin and managed servers

    I am writing a script for our application, which apart from building and
    deploying application, also needs to stop and start both admin and managed
    servers. Is there any command available for properly stopping the weblogic
    servers? ( something that "initiates the shutdown")
    Thanks

    Scott, could you try specifying the protocol: t3 in the url of the
    servers.
    eg) java weblogic.Admin -url t3://172.17.13.46:7013 -username system
    -password
    xxx SHUTDOWN
    -mihir
    Scott Jones wrote:
    I have a script that shutsdown all my servers java weblogic.Admin -url
    neo.conway.acxiom.com:$S4_ONLINE_PORT SHUTDOWN -username system
    -password $S4_WLS_ADMIN_PW
    java weblogic.Admin -url neo.conway.acxiom.com:$S4_S4MT_PORT SHUTDOWN
    -username system -password $S4_WLS_ADMIN_PW
    java weblogic.Admin -url neo.conway.acxiom.com:$S4_WLS_ADMIN_PORT
    SHUTDOWN -username system -password $S4_WLS_ADMIN_PWThe first two
    lines shut down my managed server. The last shuts down my admin
    server. Scott [email protected]
    "Mihir Kulkarni" <[email protected]> wrote in
    message news:[email protected] here -
    Solaris 2.7 with WLS 60 sp1.
    I am not facing any problems, though!
    Fyi, my managed-server is not in a cluster.
    JD wrote:
    I am running on Solaris 2.7 using WL6.0sp1.
    Mihir Kulkarni <[email protected]> wrote:
    <!doctype html public "-//w3c//dtd html 4.0transitional//en">
    <html>
    Hi,
    <br>Could you please specify on which platform are youfacing this problem.Also,
    which sp of the WLS 60 are you using ?
    <p>I tried the weblogic.Admin SHUTDOWN command on NT andSolaris and
    it
    runs correctly on both. These are the results:
    <p><b>on NT:</b>
    <br>on the client:
    <br>java weblogic.Admin -url t3://172.17.13.46:7013-username system
    -password
    xxx SHUTDOWN
    <br>Shutdown initiated
    <br>The shutdown sequence has been initiated.
    <p>on the Managed server:
    <br><Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
    <The
    disabling of server
    <br> logins has been requested by system>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
    <Server
    logins have been
    <br> disabled.>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
    <Server
    shutdown has bee
    <br>n requested by system>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
    <The
    shutdown sequence h
    <br>as been initiated.>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Info><WebLogicServer> <Server
    shutdown is comme
    <br>ncing NOW and is irreversible.>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Info> <HTTP> <[HTTPstandAloneServer]
    Destroying
    <br> servlets in default servlet context>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Info> <JMS><Undeployed
    4 default connection fac
    <br>tories.>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Info> <JMS> <JMSshutdown
    is complete.>
    <br><Jun 13, 2001 11:45:49 AM PDT> <Info><WebLogicServer> <Removing
    "ClientContext
    <br>- id: '#|standAloneServer|1.992457846784', bound:'false', dead:
    'false'"
    becaus
    <br>e of hard disconnect timeout.>
    <br><Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Requesting
    all threads t
    <br>o perform their own shutdown.>
    <br><Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Shutting
    down Thread[SSL
    <br>ListenThread,5,WebLogicServer]>
    <br><Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Waiting
    20 seconds for t
    <br>hreads to complete shutdown.>
    <br><Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Shutting
    down Thread[Lis
    <br>tenThread,5,WebLogicServer]>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Info><WebLogicServer> <Stopping
    execute threads
    <br>.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '0' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '1' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '2' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '3' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '4' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '5' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '6' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '7' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '8' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '9' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '10' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '11' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '12' for queue: 'default'' stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '0' for queue: '__weblogic_admin_html_queue''stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '1' for queue: '__weblogic_admin_html_queue''stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '0' for queue: '__weblogic_admin_rmi_queue''stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
    Thread: 'ExecuteThre
    <br>ad: '1' for queue: '__weblogic_admin_rmi_queue''stopped.>
    <br><Jun 13, 2001 11:46:10 AM PDT> <Info><WebLogicServer> <Shutdown
    has completed.>
    <p><b>on Solaris platform:</b>
    <br>on client:
    <br>java weblogic.Admin -url t3://willard.beasys.com:7003-username system
    -xxx mihirk00 SHUTDOWN
    <br>Shutdown initiated
    <br>The shutdown sequence has been initiated.
    <p>on the Managed server:
    <br><Jun 13, 2001 11:52:26 AM PDT> <Alert><WebLogicServer>
    <Server
    shutdown has been requested by system>
    <br><Jun 13, 2001 11:52:26 AM PDT> <Alert><WebLogicServer>
    <The
    shutdown sequence has been initiated.>
    <br><Jun 13, 2001 11:52:26 AM PDT> <Emergency><WebLogicServer>
    <ListenThread.run() failed: java.lang.ThreadDeath>
    <br><Jun 13, 2001 11:52:27 AM PDT> <Emergency><WebLogicServer>
    <The WebLogic Server is no longer listening forconnections. You should
    probably restart it.>
    <br><Jun 13, 2001 11:52:27 AM PDT> <Alert><WebLogicServer>
    <Server
    shutdown has been requested by system>
    <br><Jun 13, 2001 11:52:27 AM PDT> <Alert><WebLogicServer>
    <The
    shutdown sequence has been initiated.>
    <p>So, it works fine for me.
    <br>Please let me know if I am missing something.
    <p>cheers,
    <br>Mihir
    <br>
    <p>Scott Simpson wrote:
    <blockquote TYPE=CITE>"JD" <[email protected]> wrote
    in message
    <br><a
    href="news:[email protected]">news:[email protected]</a>...
    <br>> I ran this problem past BEA support and as usualthey can not duplicate
    <br>the problem.
    <p>They can't duplicate the problem! Everybody on thisnewsgroup has
    the
    same
    <br>problem. How can they not duplicate it?!</blockquote>
    </html>
    [att1.html]

  • Weblogic.Admin command for stopping all Managed Servers in cluster

    Hello All,
    I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
    I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
    I am looking for a way to do that using java weblogic.Admin utility
    Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
    Thanks
    Weblogic Consultant

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Commands for STOPPING admin and managed servers

    I am writing a script for our application, which apart from building and
    deploying application, also needs to stop and start both admin and managed
    servers. Is there any command available for properly stopping the weblogic
    servers? ( something that "initiates the shutdown")
    Thanks

    sorry i haven't moved up to 6.0 yet, so i don't know much about it :(
    hope someone else can help you there
    Manmari wrote:
    thanks bhavin. I will try this on my 6.0 However what is the command for
    stopping any of my "managed servers"? Is it the same or something like
    java weblogic.Managed "t3://managedserver:7003" SHUTDOWN
    Have you tried it. I founf a note on other newsgroup that this does not work
    for maged servers. Do you know the solution? Does it work for you?
    youe help is much appreciated
    Thanks
    "bhavin patel" <[email protected]> wrote in message
    news:[email protected]..
    i don't know if this is what you are looking for, but to stop wl 5.10
    you just need to run the weblogic.Admin class
    like this
    java weblogic.Admin "t3://yourserver:7001" SHUTDOWN <username> <password>
    hth
    Manmari wrote:
    I am writing a script for our application, which apart from building and
    deploying application, also needs to stop and start both admin and
    managed
    servers. Is there any command available for properly stopping theweblogic
    servers? ( something that "initiates the shutdown")
    Thanks

  • Cisco Prime Infrastructure 2.1 can't add Cisco ISE 1.2 to "External Management Servers"

    Hi all,
    I'm trying to add Ciso ISE 1.2 (1.2.0.899 with version 13 patch) servers (primary and secondary) as "External Management Servers" in Cisco PI 2.1 (2.1.0.0.87) but there appears such message indicating that ISE server is not reachable: 
    The weird thing is that ISE servers are reachable from PI and vice-versa (I can ping each other from their CLIs)
    There were added ISE servers to PI long ago (primary and secondary ISE) and then secondary was deleted from PI. Primary ISE still persists in PI but its status is unreachable:
    But I can see info about wired clients authenticating on the switchs (NADs for ISE) - weird, status is unreachable but client info is being received from ISE.
    I tried application stop NCS/application start NCS on PI and application stop ise/application start ise on ISE - no success for that issue.
    So I can't find a way to solve that weird issue, maybe you can help me find out the cause of such things. Thanks. 

    Hi,
    -- Please Go to Administration > Logging > set the Message level to TRACE > Click save
    -- Then try to add the ISE.
    -- Once it fails, collect the logs from Administration > Logging > 
    check the "ncs-0-0.log"  & search the file for "ERROR" & paste the results here. This will give us exact reason.
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • How to start managed servers in parallel?

    Hello everyone,
    I am developing a wlst script that would start all managed servers on a particular machine (machine_name should be provided) from the admin server side. The script works fine. However, since there were some domains that have 25+ managed servers for a single machine, it takes some time to start all of them in sequence. Is there a way to trigger a start command for each of the managed servers that I need to start just like what the node manager does when i start them through admin console? Something like triggering parallel processes running on background. Here is my code snippet:
                    #It focuses only on all managed servers defined within the listen address provided
                    if (server_listenaddress == managed_server) and (server_name != admin_name):
                            if (execute_command == "start"):
                                    print 'About to start',server_name,'on',server_listenaddress,'...'
                                    print
                                    try:
                                            start(server_name)
                                            print
                                            state(server_name,'Server')
                                            print
                                            nmDisconnect()
                                    except WLSTException:
                                            print 'Server instance',server_name,'could not be started. Skipping this server..'
                                            print
                                            state(server_name,'Server')
                            else:
                                    print 'About to stop',server_name,'on',server_listenaddress,'...'
                                    print
                                    try:
                                            shutdown(server_name,force='true')
                                            print
                                            state(server_name,'Server')
                                            print
                                    except WLSTException:
                                            print 'Server instance',server_name,'could not be stopped. Skipping this server..'
                                            print
                                            state(server_name,'Server')
                    elif (server_name == admin_name):
                            #It skips to restart the admin server since this script it only to restart managed servers.
                            print 'Server',server_name,'is the admin server. Skipping...'
                            print
                    else:
                            print 'Managed server',server_name,'is not configured with',managed_server,'listen address. Skipping this server..'
    Thanks in advance for all your help!!
    regards,
    Rustan

    Works perfectly, thanks!!!
    In summary, I just modified this line:
    start(server_name)
    and changed it to:
    start(server_name, block='false')
    In Admin Console, it is set to false but in WLST, it is defaulted to true so we need to explicitly set it to false.
    "Oracle Fusion Middleware Oracle WebLogic Scripting Tool, block is always set to true."

  • Stop managed server without node manager and admin server

    What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
    (I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
    (The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
    UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
    Edited by: user12163080 on Jun 24, 2010 4:40 AM

    Hai,
    I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
    "The start command starts Managed Servers or clusters in a domain using Node Manager.
    To use the start command, WLST must be connected to a running Administration Server.
    To start Managed Servers without requiring a running Administration Server, use the
    nmStart command with WLST connected to Node Manager."
    "You shut down a server to which WLST is connected by entering the shutdown command
    without any arguments.
    When connected to a Managed Server instance, you only use the shutdown command to shut
    down the Managed Server instance to which WLST is connected; you cannot shut down another
    server while connected to a Managed Server instance.
    WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
    Server, Node Manager must be running.
    In the event of an error, the command returns"
    They are two option if you are using adminserver then we can stop the any Managed server.
    The option is if you are using the nodemanager without admin server we can stop the any Managed server.
    The last final solution to kill the particular Managed server pid.
    Regards,
    S.vinoth babu

  • Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"

    I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
    AdminConsole - running
    IBR_server1 - FAILED_NOT_RESTARTABLE
    managedServer1 - FAILED_NOT_RESTARTABLE
    UCM_server1 - FAILED_NOT_RESTARTABLE
    I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
    I'm completely unsure what to do now. The Nodemanager log shows:
    INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
    So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
    and
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
    The domains file contains
    base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
    Which is correct.
    Any idea what I'm missing here? I can provide more detail if needed. Thank you.
    EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
    Edited by: user5824683 on Oct 5, 2011 5:04 PM
    Edited by: user5824683 on Oct 5, 2011 5:09 PM

    I did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
    Starting WLS with line:
    E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
    Caused by: java.lang.ClassNotFoundException: –Xnohup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    Could not find the main class: –Xnohup. Program will exit.
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
    <Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

  • Using wlserver to start managed servers

    Hi, all. I was wondering if someone could help me out in understanding how wlserver works. I'm using WL 8.4SP4. I have a cluster with two nodes, and I have the node manager configured properly. I can log in to the Admin console and start and stop the nodes (one of which is on a seperate machine than the admin server). I would like to be able to do this using wlserver in Ant on my local machine (not the Admin server machine), but it seems like it wants to use local jar files to start the managed server locally (wants me to give it beahome and weblogichome). I want to point it to the admin server and just tell it the node in the cluster to start. Is this possible?

    I don't know what commands you use in ant script. Maybe this will help you:
    http://e-docs.bea.com/wls/docs81/admin_ref/cli9.html#1193968
    You can use weblogic.Admin (This is a java command tool utils provided by
    WebLogic) to start your managed servers. But you should do some work before
    using this tool, see
    http://e-docs.bea.com/wls/docs81/admin_ref/cli.html#1346187 "Required
    Environment for the weblogic.Admin Utility" to get more information.
    <David Matheson> wrote in message news:[email protected]..
    Hi, all. I was wondering if someone could help me out in understanding
    how wlserver works. I'm using WL 8.4SP4. I have a cluster with two
    nodes, and I have the node manager configured properly. I can log in to
    the Admin console and start and stop the nodes (one of which is on a
    seperate machine than the admin server). I would like to be able to do
    this using wlserver in Ant on my local machine (not the Admin server
    machine), but it seems like it wants to use local jar files to start the
    managed serve
    r locally (wants me to give it beahome and weblogichome). I want to point
    it to the admin server and just tell it the node in the cluster to start.
    Is this possible?

  • Node Manager installed as service does not start managed servers. WLS 10.3

    Hi All,
    I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
    In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
    <Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
    <Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
    The node manager properties file contains the following
    #Mon Apr 20 10:54:45 PDT 2009
    DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
    LogLimit=0
    PropertiesVersion=10.3
    JavaHome=C\:\\bea\\JROCKI~1
    AuthenticationEnabled=false
    NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
    LogLevel=INFO
    DomainsFileEnabled=true
    StartScriptEnabled=false
    StartScriptName=startWebLogic.cmd
    ListenAddress=localhost
    NativeVersionEnabled=true
    ListenPort=5556
    LogToStderr=true
    SecureListener=false
    LogCount=1
    StopScriptEnabled=false
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=true
    LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    The managed servers' boot.properties file and startup file are below
    boot.properties:
    #Thu Jul 23 13:48:26 PDT 2009
    CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
    TrustKeyStore=CustomTrust
    password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
    CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
    CustomTrustKeyStoreType=JKS
    username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
    startup.properties:
    #Server startup properties
    #Thu Jul 23 13:48:27 PDT 2009
    Arguments=-Xms1024m -Xmx1024m -Xnohup
    JavaHome=C\:\\bea\\jrockit_160_05
    SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
    RestartMax=2
    RestartDelaySeconds=0
    RestartInterval=3600
    BeaHome=C\:\\bea
    ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
    AdminURL=http\://localhost\:7001
    JavaVendor=BEA
    AutoRestart=true
    AutoKillIfFailed=false
    I am wondering if I left out a parameter some where.
    Any help would be greatly appreciated.
    Thanks,
    Greg

    First of all, I assume you mean "... up it does NOT start ..."?
    It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
    For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers.

  • SCOM Management Servers not working after DW upgraded to SQL 2014

    Hey guys,
    Our setup is that we have 2 Management Servers running SCOM 2012 R2 UR3 on Server 2008. I want to say exactly what our problem is, and what my guesses are at it. Any additional information you need please just ask. 
    Problem = In the SCOM console we have the management servers and Gateway servers going grey. If i go to these servers and restart the Monitoring service, it acts like it was locked up or something and has to force stop it and restart it. Once back up, everything
    works fine. Then it goes grey again at a random interval between 5-120 minutes. Recycle Repeat. I reviewed the Event Log during this and afterwards and ALOT of stuff points toward the DataWarehouse and not being able to write stuff to it. I have two suspicions. 
    Idea 1 = Another Engineer recently updated SQL on the Datawarehouse server to 2014. I recently found this had caused a problem with SCSM reporting and had to do some stuff to fix that.... so I was thinking that maybe this had something to do with it. 
    Idea 2 = Also around the same time... UR3 came out. This was auto pushed out to all the server and agents through WSUS, I also went through and manually did all the steps for this. Its still possible i suppose that I missed something. 
    Basically Im just looking to see if anyone has any advice as to what to check next, and/or see if anyone else has had this problem. Thanks guys!

    I unfortunately do not have a solution for you, but can still try to provide some info :
    1. SQL 2014 is NOT supported with system center 2012 R2! See http://technet.microsoft.com/library/dn281933.aspx
    2. You might want to try the procedure for moving the databases : http://technet.microsoft.com/en-us/library/hh278848.aspx

Maybe you are looking for

  • HELP! Illegal operand error - can't open file!  (v.2)

    I have a file that I've done about 40 hours on since last duplicating it. It's been saved multiple times, and successfully. Now, however the file seems to be corrupt. I'm getting the following error message when opening it: Cant open the illustration

  • How to find out the selection screen values

    Hi All, in BI we are having the maximum allowed cells as 500000 for a report. for some of the reports execution fetching the data morethan 500000 by different users. i could findout the report and user who has executed, But i wanted to findout for wh

  • HELP! I am having trouble when I try to paste a snap shot into a Word document!

    When I paste the picture into the Word document, the image is blurry.  What can I do to keep this from happening?

  • ITunes closes whenever I add videos

    whenever I add a new video to my library, I get a dialogue box that says 'iTunes has encountered a problem and needs to close. We are sorry for the inconvenience.' Is it the file that I'm adding, or is it iTunes? Or are both fine, and it's my compute

  • How can I use telnet our Vxworks system?

    Hello all: I am newly learning labview program ,now I want to use labview to make some actions and sent to our Vxworks system, this system support telnet server , I use Internet tool to finish this work ,but I met some questions, I didn't succeed to