Article ID: 318163 - Last Review: October 25, 2006 - Revision: 3.3 SMS: Client Service Does Not Quit During ShutdownThis article was previously published under Q318163 On This PageSYMPTOMS
When you click Shut down the computer on a computer that is running the Systems Management Server (SMS) client, the SMS Client service (Clisvcl.exe) may continue to run. This may occur even after the Shutdown Computer: It is now safe to turn off your computer dialog box appears. If you do not immediately restart your computer, Clisvcl.exe may try to start optional components. These attempts may lead to the system volume being marked as dirty. If this occurs, Autochk runs the next time you start your computer.
RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:288239
(http://support.microsoft.com/kb/288239/EN-US/
)
How to Obtain the Latest Systems Management Server 2.0 Service Pack Hotfix InformationA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this fix should have the following file attributes or later: Date Time Version Size File name Platform ----------------------------------------------------------------------- 02-Mar-2001 01:30 655,463 Apasetup.exe Alpha 02-Mar-2001 00:15 2.0.1493.3251 293,648 Ccim32.dll Alpha 02-Mar-2001 00:30 1,925,229 Ccmcore.exe Alpha 02-Mar-2001 00:15 2.0.1493.3251 4,442,606 Clicore.exe Alpha 02-Mar-2001 00:10 2.0.1493.3238 125,712 Clisvcl.exe Alpha 01-Mar-2001 13:00 2.0.1493.3125 578,832 Mslmclin.dll Alpha 02-Mar-2001 00:00 2.0.1493.3236 75,024 Odpsys32.exe Alpha 02-Mar-2001 00:00 2.0.1493.3236 83,728 Odpusr32.exe Alpha 02-Mar-2001 01:30 2.0.1493.3254 387,856 Smsapm32.exe Alpha 02-Mar-2001 00:00 693,008 Swdist32.exe Alpha 02-Mar-2001 01:30 395,032 Apasetup.exe Intel 01-Mar-2001 13:00 2.0.1493.3125 259,936 Bindclin.dll Intel 02-Mar-2001 00:15 2.0.1493.3251 182,096 Ccim32.dll Intel 02-Mar-2001 00:30 1,324,075 Ccmcore.exe Intel 02-Mar-2001 00:15 2.0.1493.3251 3,402,213 Clicore.exe Intel 02-Mar-2001 00:10 2.0.1493.3238 88,432 Clisvcl.exe Intel 01-Mar-2001 22:20 2.0.1493.3216 39,264 Cqmgr32.dll Intel 01-Mar-2001 13:00 2.0.1493.3125 338,272 Mslmclin.dll Intel 01-Mar-2001 13:00 2.0.1493.3125 269,664 Ndsclin.dll Intel 02-Mar-2001 00:00 2.0.1493.3236 54,128 Odpsys32.exe Intel 02-Mar-2001 00:00 2.0.1493.3236 60,272 Odpusr32.exe Intel 25-Sep-2001 23:14 762,688 Preinst.exe Intel 02-Mar-2001 01:30 2.0.1493.3254 291,696 Smsapm32.exe Intel 02-Mar-2001 00:00 639,507 Swdist32.exe Intel 02-Mar-2001 01:30 2.0.1493.3254 67 Compverbase.ini 02-Mar-2001 01:30 2.0.1493.3254 67 Compversmsapm32.ini 02-Mar-2001 01:30 2.0.1493.3254 67 Compverswdist.ini How to Install the Hotfix with the Hotfix InstallerNOTE: You can only use this method on Intel-based computers.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5. APPLIES TO
| Article Translations
|
Back to the top
