Microsoft KB Archive/831757

= SMS 2.0 APM fails with the entry &quot;The local device name is already in use&quot; in Smsapm32.log when you use the software installation account =

Article ID: 831757

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Service Pack 5
 * Microsoft Systems Management Server 2.0 Service Pack 4

-





SYMPTOMS
Microsoft Systems Management Server (SMS) Available Programs Manager (APM) may not be able to run a program that is advertised through SMS and that is set up to use the Microsoft Windows NT client software installation account. The following entries are typically seen in Smsapm32.log if you are experiencing this problem. These entries will not appear one right after another. NAL[1] - ERROR: failed check if device is connected. The local device name is already in use. NAL[1] - ERROR: failed to register with the connection with Connection Arbiter. The local device name is already in use. NAL[1] - ERROR: failed to make the device connection. The local device name is already in use. SCHED DATA : Return code = 0x80070055; The local device name is already in use.; Could not enable program 'Z:\SMSPKG\AAA00001\REGSVR32.EXE /S'. SCHED DATA : Handling an error condition (0x80070055) for program 'regsvr32' in package 'regsvr32'. Additionally, a status message 10003 that is similar to the following is recorded: An error occurred while preparing to run the program for advertisement &quot;AAA20000&quot; (&quot;regsvr32&quot; - &quot;regsvr32&quot;). The operating system reported error 2147942485: The local device name is already in use.



CAUSE
This problem may occur if any one of the following conditions is true:
 * You installed SMS Service Pack 5 (SP5).
 * You applied the post-Service Pack 4 (SP4) hotfix that is described in Microsoft Knowledge Base Article 810059.
 * You applied any other post-SP4 hotfix that includes Progrm32.dll version 2.0.1493.4167 or later.

This problem only occurs if a package is set up to use more than one SMS Distribution Point.

There is a problem with the way APM creates its network connections when a program that requires a drive letter is configured to use the Microsoft Windows NT client software installation account. This problem was first introduced with the hotfix that is described in Knowledge Base Article 810059. This hotfix is included in SMS SP5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

810059 SMS: Windows XP-based clients cannot run distributed programs



RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

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:

http://go.microsoft.com/?linkid=6294451

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:

http://support.microsoft.com/contactus/?ws=support

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Method 1: Use the Hotfix Installer
Note This method works only for Intel-based computers.
 * 1) Create a folder in a location that is accessible to your SMS site servers.
 * 2) Copy the SMS2.0-SP -KB831757-X86-ENU.exe update file (where   is the service pack version) to the new folder.
 * 3) From each of the primary and the secondary SMS site servers in your environment, log on to your site server by using an account with administrative credentials.
 * 4) Quit SMS Administrator if it is running.
 * 5) Run SMS2.0-SP -KB831757-X86-ENU.exe, and then follow the instructions in the wizard.

Method 2: Manually Install the Hotfix

 * 1) Create a folder in a location that is accessible to your SMS site servers.
 * 2) Run SMS2.0-SP -KB824153-X86-ENU.exe /x (where   is the service pack version), and then extract the hotfixed files to the folder that you just created.
 * 3) From each of the primary and the secondary SMS site servers in your environment, log on to your site server by using an account with administrative credentials.
 * 4) Quit SMS Administrator if it is running.
 * 5) Stop all SMS services.
 * 6) Replace the following files in the  \Bin\  folder with the versions from the hotfix:
 * 7) * Ccim32.dll
 * 8) * Clisvcl.exe
 * 9) * Cqmgr32.dll
 * 10) * Odpsys32.exe
 * 11) * Odpusr32.exe
 * 12) * Smsapm32.exe
 * 13) Replace the Swdist32.exe file in the  \Inboxes\Clicomp.src\SWDist\  folder with the version from the hotfix.
 * 14) Replace the Apasetup.exe file in the  \Inboxes\Clicomp.src\Smsapm32\  folder with the version from the hotfix.
 * 15) Replace the files Ccmcore.exe and Clicore.exe in the  \Inboxes\Clicomp.src\Base\  folder with the versions from the hotfix.
 * 16) Replace the Compver.ini file in the  \Inboxes\Clicomp.src\SWDist folder with the Compverswdist.ini file from the hotfix. You must rename the Compverswdist.ini file to Compver.ini.
 * 17) Replace the Compver.ini file in the  \Inboxes\Clicomp.src\Smsapm32 folder with the Compversmsapm32.ini file from the hotfix. You must rename the Compversmsapm32.ini file to Compver.ini.
 * 18) Replace the Compver.ini file in the  \Inboxes\Clicomp.src\Base folder with the Compverbase.ini file from the hotfix. You must rename the Compverbase.ini file to Compver.ini.
 * 19) Restart the SMS services.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



WORKAROUND
To work around this problem, do one of the following:
 * Do not configure the program to use the Windows NT client software installation account.
 * Do not configure the program to require a drive letter.
 * Configure the package for the program to use only one SMS Distribution Point.



MORE INFORMATION
The SMS Service Pack 4 (SP4) hotfix for this problem also corrects the problem that is documented in Knowledge Base Article 823470 for SMS SP4 sites. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

823470 SMS: Smsapm32.exe crashes after repeated interruptions of an advertised program

Keywords: kbqfe kbhotfixserver kbsmsadmin kbsms200presp6fix KB831757

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.