Microsoft KB Archive/814683

From BetaArchive Wiki
Knowledge Base


Cannot Install Business Desk Client on Computers Without Drive C

Article ID: 814683

Article Last Modified on 11/15/2007



APPLIES TO

  • Microsoft Commerce Server 2002 Standard Edition



SYMPTOMS

When you try to install the Business Desk client on a computer that does not have drive C, setup is unsuccessful, and you receive the following error message:

Device unavailable

RESOLUTION

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Size     File name
   --------------------------------------------
   28-Feb-2003  08:12  400,098  Clientsetup.cab  
                

The Business Desk client functionality is contained in the ClientSetup.cab file. This file is located in the root directory of the Business Desk Web site or sites. To install this hotfix, replace the version of Clientsetup.cab in the root directory of the affected Business Desk Web site or sites with the version from this hotfix.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbhotfixserver kbqfe kbfix kbbug KB814683