Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/240980

From BetaArchive Wiki

Article ID: 240980

Article Last Modified on 7/24/2007



APPLIES TO

  • Microsoft Systems Management Server 2003 Service Pack 1
  • Microsoft Systems Management Server 2003
  • Microsoft Systems Management Server 2.0 Service Pack 1
  • Microsoft Systems Management Server 2.0 Standard Edition



This article was previously published under Q240980


SYMPTOMS

When you double-click the Systems Management Server tool in Control Panel on a computer that is running Microsoft Systems Management Server (SMS) 2003 or Microsoft Systems Management Server 2.0, you may receive one of the following error messages.

Message 1

An error occurred while Windows was working with the Control Panel file SMSCFG.CPL

Message 2

An exception occurred while trying to run "C:\WINDOWS\system32\shell32.dll,Control_RunDLL C:\WINDOWS\system32\ccm\smscfgrc.cpl,Systems Management"

CAUSE

This problem may occur if the SMS client computer has more than 20 network adapters installed. This applies to physical adapters, virtual adapters, and dial-up adapters. For example, one type of server that may have more than 20 network adapters installed is the 3Com Edgeserver. This problem may also occur if the SMS client computer has a large number of IP addresses but only one network adapter or only a few network adapters.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

288239 How to obtain the latest Systems Management Server 2.0 service pack


RESOLUTION

Hotfix information for SMS 2003 Advanced Client

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:

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:

Prerequisites

This hotfix requires SMS 2003 Service Pack 2

Restart requirement

You do not have to restart the computer after you apply this hotfix.

File information

File name File version File size Date Time Platform
Sms2003-sp2-kb240980-x86-enu.exe 2.50.4160.2103 682,288 06-Apr-2006 18:39 x86
Sms2003ac-sp2-kb240980-x86.msp Not Applicable 261,120 01-Mar-2006 09:10 Not Applicable
Smscfgrc.cpl 2.50.4160.2103 55,296 01-Mar-2006 09:10 Not Applicable


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Systems Management Server 2.0 Service Pack 2.

MORE INFORMATION

Note This problem is also corrected in the SMS Legacy Client in Systems Management Server 2003.

To install this hotfix, follow these steps:

  1. Stop the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.
  2. Copy the updated Compver.ini file to the Inboxes\Clicomp.src\Base folder.
  3. Copy the hotfixed Clicore.exe file to the Inboxes\Clicomp.src\Base\Platform folder.
  4. Copy the updated Mslmclin.dll, Ndsclin.dll, and Bindclin.dll files to the SMS\Bin\Platform folder.


Note For Alpha-based computers, only one file, Mslmclin.dll, is included with this hotfix. This is normal.

  1. Start the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.

The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfixed files to be propagated to the clients. To speed up this process, you can stop and restart the SMS Client Service on each client. You can also create a software distribution for one of the Resource Kit tools (Setevnt.exe or Cliutils.exe), along with the appropriate parameter(s) to start a CCIM work cycle. For information about the proper syntax to use with these tools, see the Resource Kit documentation.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.


Additional query words: prodsms edge server ras dialin dialout dialup modem pool

Keywords: kbqfe kbhotfixserver kbbug kbfix kbsms200fix kbsms200sp2fix KB240980