Microsoft KB Archive/810059

From BetaArchive Wiki

Article ID: 810059

Article Last Modified on 10/25/2006



APPLIES TO

  • Microsoft Systems Management Server 2.0 Standard Edition




SYMPTOMS

Windows XP-based clients cannot run a program that is distributed by Systems Management Server (SMS). The following error message is logged in the Smsapm32.log file when Available Programs Manager (APM) tries to run a distributed program:

SCHED DATA : Return code = 0x3; The system cannot find the path specified.~~; Could not execute program 'N:\AUS00007\TESTAPP.EXE'.

This problem only occurs on SMS clients that are running Windows XP.

CAUSE

This problem occurs if the following SMS configuration is true:

  • The Use Windows NT client software installation account setting is selected.
  • The Drive mode is set to either Requires drive letter or Requires specific drive letter.

This problem is caused by a change in the way that Windows XP deals with network connections. For additional information about this change, click the following article number to view the article in the Microsoft Knowledge Base:

180362 INFO: Services and Redirected Drives


RESOLUTION

This fix has been superseded with a later revision. To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article:

831757 SMS 2.0 APM fails with the entry "The local device name is already in use" in Smsapm32.log when you use the software installation account


WORKAROUND

To work around this problem, use one of the following procedures:

  • Method 1:
    1. Start the SMS Administrator console, and then go to the following location:

      Site Database\Packages\Packagename\Programs

    2. Double click the affected program, click the Environment tab, and then click Runs with UNC name in the Drive mode to box.
  • Method 2:
    1. Start the SMS Administrator console, and then go to the following location:

      Site Database\Packages\Packagename\Programs

    2. Double click the affected program, click the Environment tab, and then make sure that Use Windows NT client software installation account is not selected.


STATUS

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

MORE INFORMATION

If an SMS-distributed program requires a drive letter and if it is also set up to use the Windows NT client software installation account, APM first makes a network connection to the distribution point in its own user context (SMSCliToknAcct&). Note that the connection is made by Smsapm32.exe running under SMSCliToknAcct&, but that the actual account that is used to establish the connection is the SMS Client Connection Account. By default, this account is SMSClient_sitecode. When APM starts the program's command line, it does so in the context of the Windows NT client software installation account. In Windows XP, this account does not have access to the previously established network connection because it was made in a different user context.

Keywords: kbqfe kbhotfixserver kbsms200presp5fix kbfix KB810059