SBL-CDM-00220: Unable to download the Upgrade Kit "%1" required to upgrade your system. Please check your File System setting and available disk space

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Cons Sec
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-1896688781.

Symptoms

SBL-CDM-00200, SBL-DCK-00203

Hi,

Recently we had a new srf release, this srf contained several browser scripts too.
When our system admin created the anywhere package and distributed it, to our surprise
we did not see the browser scripts being generated in the client machine.

We came to know that this is a product bug and there was a work around in ALERT 466.
We tried to do the same that was described in this alert but this too worked.

Could you please help us in resolving this issue at the earliest.

My Contact details are :-


Phone#

Solution

Message 1

1 of 3

Issue: genbscript does work with the anywhere package in siebel 7.5.3

Resolution:I assume you want all of these kits to be pulled.

So, I would create them as follows:

Kit 1: Siebel Client Repository file _enu1 - SRF file. Change made to Generate browser scripts path based on Alert 840. Min version = null , Max version = null, new version =1; package is a mandatory package.

Kit 2; Siebel Client Customer Revision_enu 1 - browser scripts applets (total of 40 files)
Min version = null, Max version = null, New version = 1, Mandatory package

Kit 3; Siebel Client Customer Revision_enu 2 -1 rox file (reports)
Min version = 1, Max version = 1, New version = 2; Mandatory package

Kit 4: Siebel client Customer Revision_enu 3 - 1 swt file;
Min. version = 2, Max version = 2 New version=3; Mandatory package

Delete clntenu.cfg from client\bin\enu folder. Retry.

Contd.......

Message 2

2 of 3

Customer's next question was as follows

Can I deactive kit 3 and 4, change the min and max settings on upgrade kit view and active, distribute without causing any problems with future user downloading the package?

Response: Deactivate (it will set the status to Pending) then you can add Min Old and Max Old Versions, then Activate -- no need to distribute

Customer's next question was as follows

Can you also confirm that by resetting my clntrev.cfg file to 0 will also force all there packages to download. I am thinking if this is changed, user should get all three customer revision packages regardless what version of the file they have.

Response: Since your kits are Siebel Client Customer Revisions__ENU, the version information is stored in clntenu.cfg in the client\bin\enu folder. This file can be deleted and therefore the version will be 0.

Continued...

Message 3

3 of 3

Customer's next question was as follows

What are are seeing that the two test users do not have the clntenu.cfg file on their local.
When when the try to dowload the packages via server mode they get the following error:
SBL-CDM00200 - checking their filesystem settings and disk space, all seem to be okay.

Response: It is possible that the user's login name did not appear on the Upgrade Employee Configuration view. A similar login name to this user's name maybe in the list, but not this particular user's login name.

Add his name to the list and run "Distribute" for the Upgrade Configuration. He should be able to get the latest upgrade kits.

Customer Feedback: Thanks for all your help, we were able to resolve the problem.