Microsoft KB Archive/841773

= BUG: SQL Server Setup stops responding when you upgrade an instance of SQL Server Desktop Engine (Windows) to SQL Server 2000 =

Article ID: 841773

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine (Windows), when used with:
 * Microsoft Windows Small Business Server 2003 Premium Edition

-



Bug #: 470856 (SQL Server 8.0)



SYMPTOMS
You upgrade a default instance of Microsoft SQL Server 2000 to SQL Server 2000 Service Pack 3 (SP3) on a computer that is running Microsoft Windows Small Business Server 2003. If you try to upgrade the instance of Microsoft SQL Server 2000 Desktop Engine (Windows) that corresponds to Microsoft Windows SharePoint Services to SQL Server 2000, SQL Server Setup stops responding. You receive the following error message:

Setup is preparing to copy files



CAUSE
The Service Control Manager (Scm.exe) experiences a time-out when it tries to stop the MSSQL$SharePoint service.

Note The MSSQL$SharePoint service is the Microsoft Windows service for the instance of SQL Server 2000 Desktop Engine (Windows) that corresponds to Windows SharePoint Services.



WORKAROUND
To work around this problem, you must manually stop the MSSQL$SharePoint service before you start the Setup program to upgrade the instance of SQL Server 2000 Desktop Engine (Windows).

Note If the Setup program stops responding with the message that is mentioned in the &quot;Symptoms&quot; section, you can manually stop the MSSQL$SharePoint service to continue the upgrade process.

To manually stop the MSSQL$SharePoint service, follow these steps:
 * 1) Click Start, click Run, type Services.msc, and then click OK.
 * 2) In the right pane of the Services window, locate MSSQL$SharePoint.
 * 3) Right-click MSSQL$SharePoint, and then click Stop.
 * 4) Close the Services window.



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



MORE INFORMATION
When this problem occurs, the full dump file of the Service Control Manager may look similar to the following: # ChildEBP RetAddr 00 0012f184 77f4262b SharedUserData!SystemCallStub+0x4 01 0012f188 77e418ea ntdll!NtDelayExecution+0xc [d:\srv03rtm\base\ntdll\daytona\obj\i386\usrstubs.asm @ 611] 02 0012f1f0 77e416ee kernel32!SleepEx(unsigned long dwMilliseconds = 0x1388, int bAlertable = 0)+0x68 [d:\srv03rtm\base\win32\client\synch.c @ 1646] 03 0012f1fc 00405bec kernel32!Sleep(unsigned long dwMilliseconds = )+0xb [d:\srv03rtm\base\win32\client\synch.c @ 1570] 04 0012f218 0040181c scm!CServiceNT::Stop(int bStopDependents = )+0x11c [..\shared\csvcnt.cpp @ 327] 05 0012ff14 00401321 scm!CApp::RunThread(void * lpv = 0x00000000)+0x41c [app.cpp @ 445] 06 0012ff34 00408a03 scm!CApp::Run(int nCmdShow = )+0x11 [app.cpp @ 246] 07 0012ffc0 77e4f38c scm!WinMainCRTStartup(void)+0xce [crt0.c @ 198] 08 0012fff0 00000000 kernel32!BaseProcessStart( * lpStartAddress = 0x00408935)+0x23 [d:\srv03rtm\base\win32\client\support.c @ 580]

Additional query words: Hangs hung upgradation WMSDE

Keywords: kbtshoot kbbug kbscm kbservice kbupgrade kbsetup kbpreinstall KB841773

-

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

© Microsoft Corporation. All rights reserved.