Siebel Anywhere Administration Guide > Troubleshooting for Siebel Anywhere >

Failed Upgrade Kit Locks the Siebel Administrator's Account

If the Siebel administrator's account is locked out due to a failed upgrade kit, then the following procedure will help you recover.

It is also sometimes possible to log in as a Web Client that does not have version checking or upgrades, and take corrective measures to resolve the issue related to the failed upgrade.

To unlock the Siebel administrator's account

1. Edit the Siebel administrator's CFG file by changing the value of the ComponentName parameter to None.

   This change prevents the Siebel client from performing any version checking. If you dynamically associated the Siebel administrator account with a configuration, then create a service request (SR) on My Oracle Support. Alternatively, you can phone Oracle Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support.

   CAUTION:  Dynamically associating the Siebel administrator account with any configuration is not recommended, because it sometimes prevents the administrator from logging in.

2. If the upgrade kit failed while the Upgrade Wizard was running, then delete the file upgwiz.ucf in the bin directory.

   The Siebel client always checks for the existence of the file upgwiz.ucf in the bin directory to find out if it was in the middle of an upgrade.

3. Log in to the Siebel Business Applications to determine the reason for the failed upgrade, and take corrective measures.

   Presumably, the other subscribers to your original configuration are also affected.

4. Test your solutions using the Siebel Test Client configuration.
5. After testing the upgrade kit thoroughly, distribute the correct upgrade kit to every appropriate configuration.

   Remember to change the value of the ComponentName parameter to its original value in the CFG file.