Siebel Administration >  SBL-SVR-00005: Stale or invalid Task handle

SBL-SVR-00005: Stale or invalid Task handle

SVR-00026: Unable to allocate shared memory
SVR-01045: No components configured !
SVR-00005: Stale or invalid Task handle
SVR-00029: Shared memory has not been initialized
SMI-00044: An instance of this Siebel Server is already running

The above error message is reported in the log files when the Siebel server fails to start up. In most occasions, one or more of the above error messages also accompany it.

Cause

These errors might be reported for the following known reasons:

There is a shared memory file that is maintained by each Siebel server under the "admin" directory of its root installation ($Siebel_ROOT\adminon both UNIX and windows). This file follows the naming convention[<$EnterpriseName>.<$ServerName>.shm]. It is built upon server startup, and destroyed upon shutdown. If this file cannot be created successfully upon server startup the above error message can be reported. Possible reasons for this file to be not created successfully are:
The clean up routine upon shutdown did not clean this file possibly because of an abnormal termination of the Siebel server service.
Possible disk space issues preventing creation of this file.
Lack of permissions on this directory/folder or file by the service owner account.
A corrupt siebns.dat could result in the Siebel service not being able to start. (This corruption could be due to incorrect/corrupt entries in the file, or the "System Management" component group being accidentally disabled).

Diagnostic Steps

Ensure shut down of Siebel server service(s) are always organized and prior to the Siebel gateway server service.

Check if the above .shm file is present in spite of server shutdown, is a new version of it being created upon server startup?

Ensure adequate disk space and memory is available for the Siebel installation.

Ensure the adequate permissions (as documented in the server installation guide) are provided to the Siebel server service owner account.

Attempt to start the Siebel server service with a good, prior back up of the siebns.dat file. If it does start up successfully that would indicate that the file it was presently working with is corrupt for some reason. Forward the corrupt file to Siebel Technical Support.

Solution

If it is the order of the shutdown of the Siebel server services that was the cause for the error, revise shutdown procedure to adhere to the following order (Database Server > Web Server > Siebel Server(s) > Gateway Server).

After making a copy of the old *.shm (if it was left behind after a server shutdown), delete it and restart the service, and verify whether a new *.shm file is created and if that allowed the server to start up properly.

Provide for ample disk space and comply with the memory requirements of a typical Siebel installation.

Grant necessary privileges and permissions to the Siebel Server service owner account.

Work with Siebel Technical Support to address specific siebns.dat corruption issues.