Siebel CRM Anywhere Administration Guide Siebel 2018 E24720_01 |
|
![]() Previous |
![]() Next |
View PDF |
Occasionally, you might notice that the status of a new upgrade kit remains In Progress for an extended period, indicating that the upgrade kit is taking a long time to build. If this is the case, then consider the following information to help troubleshoot the situation.
Some of the reasons for a delay in status change include:
The upgrade kit is still being built. (In particular, Siebel Database Schema upgrade kits can take as long as two hours or more to build.) To monitor the progress of the upgrade kit, use one of the following options to check the latest status:
Navigate to the Administration - Server Management screen, then Components, and then Tasks. Look for the latest status of the Upgrade Kit Builder component.
In the server manager line-mode utility, enter:
list task for comp UpgKitBldr
Look for the component log file for Upgrade Kit Builder (UpgKitBldr_taskno.log) in the log directory.
Upgrade Kit Builder is not responding. Sometimes a Siebel File System error or a network connection error interrupts the operation of Upgrade Kit Builder. If you conclude that Upgrade Kit Builder is not responding, then take the following actions:
Check these server components, which support Upgrade Kit Builder: File System Manager (FSMSrvr) and Server Request Broker (SRBroker). Make sure that these components are running correctly.
Edit the record, change the status from In Progress to Error, save the record, and then delete the record before trying to rebuild. (The reason for deleting the failed record is to avoid a naming conflict.) Then, recreate the upgrade kit.