System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Monitoring Siebel Server Run-Time Operations >

About Siebel Server States

After installation, a Siebel Server is always in one of the following states when connected to the Server Manager component (alias ServerMgr):

• Starting Up. Indicates that the Siebel Server is in the process of starting up. When this process is complete, the state changes to Running.
• Running. Indicates that the Siebel Server is running and that Siebel Server components can operate. This is the normal mode of operation for the Siebel Server. When the Siebel Server Service starts, it sets the Siebel Server to the Running state by default (depending on the value of the Auto Startup Mode Siebel Server-level parameter, which defaults to TRUE).

  When the Siebel Server starts, its components are enabled and the default number of tasks is instantiated for the background mode components (the number of tasks is determined by the value of the Default Tasks parameter for each component).

• Shutting Down. Indicates that the Siebel Server is in the process of shutting down. When this process is complete, the state changes to Shutdown.
• Shutdown. Indicates that the Siebel Server is running, but component tasks are not currently running (other than the Siebel Server Manager component, which is operational whenever the Server Manager is connected) and new tasks are not allowed to start. The only processes that can run when the Siebel Server is in a Shutdown state are the Siebel Server System Service itself and the Server Manager for a Siebel Server Manager client.

  Shut down the Siebel Server using the Server Manager whenever you want to shut down the:

  • Server machine on which the Siebel Server is running. This allows a clean shutdown of each Siebel Server component.
  • Siebel Server to perform maintenance.
  • Siebel Server to perform an automatic upgrade on the Siebel Server's software using Siebel Upgrade Wizard.

    NOTE:  Individual components may be shut down or disabled without having to shut down the entire Siebel Server.

If the Siebel Server is not connected to the Server Manager component (alias ServerMgr), the following states are applicable:

• Not available. Indicates that the Siebel Server has not been started. Indicates that the Server Manager cannot connect to the Siebel Server; you will not be able to run any tasks or perform any administrative functions on that Siebel Server.
• Connect Failed. Indicates that Server Manager is able to get the connect string for the ServerMgr component from the Siebel Gateway Name Server but is unable to connect to the Siebel Server.
• Handshake Failed. On startup, Server Manager sends a handshake request to the Siebel Server for the ServerMgr component. If that request fails then this state occurs. Also, if the ServerMgr component on that particular Siebel Server cannot start any more tasks (because it has reached Maximum Tasks (alias MaxTasks) number of tasks) for the administration clients, this state occurs. For more information on the MaxTasks parameter, see Siebel System Administration Guide and Performance Tuning Guide.
• Login Failed. Server Manager connects to every Siebel Server for authentication. If the authentication fails for any Siebel Server, the Login Failed state appears.
• Disconnected. When Server Manager connects to the Siebel Server, the Siebel Server starts a task for the ServerMgr component. If that task exits (because of a crash or other problems), the Disconnected state appears.

Siebel Server Status Fields

Each Siebel Server record has three fields in which the Siebel Server status appears (Table 3).