Siebel Anywhere Administration Guide > Troubleshooting for Siebel Anywhere >

New Upgrade Kit Status "Request Submitted"

From time to time, you may notice that the status of a new upgrade kit remains Request Submitted after several minutes of waiting. A status of Request Submitted means that the Upgrade Kit Builder has not yet picked up the server request to build the kit. There are a number of possible causes for this delay:

• The upgrade kit may have been created when the Siebel Anywhere component was not enabled. The status will not change until the component is enabled. After the component is enabled, the request should be processed automatically.
• The server component Upgrade Kit Builder (UpgKitBldr) may be busy building a previously submitted kit. Most kits take only a few minutes to build. However, database schema kits can take as long as two hours or more to build, depending on the database type, size, and the extent of the schema changes.
• The server component Upgrade Kit Builder (UpgKitBldr) may not be running.
• The server component Server Request Broker (SRBroker) may not be running correctly.
• The server component Server Request Processor (SRProc) may not be running correctly.

The following paragraphs provide information about troubleshooting the latter problems.

Checking for Current Upgrade Kit Builder Activity

The following two procedures provide ways to check whether the Upgrade Kit Builder is busy building another kit:

To check Upgrade Kit Builder activity in a Siebel application

1. In your Siebel application, navigate to Administration - Server Management > Components.
2. In the Components list, select the Upgrade Kit Builder component.
3. Click the Tasks view tab, and inspect the status of any tasks submitted for the Upgrade Kit Builder component.

To check Upgrade Kit Builder activity using srvrmgr

• In srvrmgr, enter the following command to check on the status of Upgrade Kit Builder tasks:

  srvrmgr> list task for comp UpgKitBldr

Checking the Status of Components Related to Upgrade Kits

There are three ways to check the status of the UpgKitBldr, SRBroker, and SRProc components:

• In your Siebel application, navigate to Administration - Server Management > Components, select each applicable component, and click the Tasks view tab to inspect the status of tasks submitted for that component.
• In srvrmgr, use the following command to view the status of a component, replacing component_name with UpgKitBldr, SRBroker, or SRProc:

  srvrmgr> list comp component_name

• In the log directory, check the log files as follows:
  • Inspect the enterprise_server_name.siebel_server_name.log to verify that all the processes for UpgKitBldr, SRBroker, and SRProc were created correctly.
  • See whether there are any signs of trouble in the SRProc_task#.log file or the SRBroker_task#.log file.

Troubleshooting Server Request Processor Problems

If you find evidence that the SRProc component is not running correctly, check the following aspects of your server's configuration:

• Is database connection information correct?
• Is User Name/Password correct?
• Have you done server component synchronization? For information about this procedure, see Siebel System Administration Guide.

For more information about troubleshooting server problems, see System Monitoring and Diagnostics Guide for Siebel eBusiness Applications.