Microsoft KB Archive/308816

= FIX: Service Control Manager Shows Incorrect Status on SQL Server 2000 Desktop Engine =

Article ID: 308816

Article Last Modified on 11/14/2003

-

APPLIES TO

 Microsoft SQL Server 2000 Desktop Engine (Windows), when used with:  Microsoft Windows 98 Second Edition

 Microsoft Windows 98 Standard Edition 

-



This article was previously published under Q308816



BUG #: 354224 (SHILOH_BUGS)



SYMPTOMS
After you install a SQL Server 2000 Desktop Engine (MSDE) named instance on a Microsoft Windows 98 based computer, if you do not specify the instance name in upper case, you may encounter the following problems:

 The Service Control Manager (SCM) does not show the correct status, regardless of the way you install MSDE, either from the command prompt or from Microsoft Windows Explorer.

</li> If you click Start or Continue, SCM starts the service although the status still shows as Stopped. Similarly, the Auto-start service when OS starts option starts the service when you restart the computer; however, the status shows as Stopped in SCM.

</li> If you click Refresh Services the status does not change; however, if the Auto-start service when OS starts option is selected, clicking Refresh Services clears the Auto-start service when OS starts check box.

</li> If you try to uninstall the Desktop Engine, the following error message occurs:

Another application has exclusive access to the file 'C:\Program Files\Microsoft SQL Server\MSSQL$Instancename\Data\tempdb.mdf'. Please shut down all other applications, then click Retry.

</li></ul>

<div class="cause_section">

CAUSE
The setup program does not convert the instance name to upper case when it adds an entry for the program in the registry.

<div class="resolution_section">

RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

<div class="workaround_section">

WORKAROUND
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, you can use either of these methods:

 New Installation

Specify the instance name all in upper case.

</li> Existing Installation

For an installation that already exists, use these steps:

<ol> Modify the following registry value so that the instance name is in upper case:

HKLM\Software\Microsoft\Microsoft SQL Server\InstalledInstances

</li> Restart the operating system.</li></ol>

Now, if you stop and then restart the computer, SQL Server reflects the SQL Server service status correctly.

If an error message occurs when you try to uninstall the Desktop Engine, terminate the execution of Sqlservr.exe by using the CTRL+ALT+DEL keys, and then proceed with the uninstall.</li></ul>

<div class="status_section">

STATUS
Microsoft 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 SQL Server 2000 Service Pack 2.

Additional query words: SCM

Keywords: kbbug kbfix KB308816

-

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

© Microsoft Corporation. All rights reserved.