Microsoft KB Archive/814373

= Microsoft Visual FoxPro 7.0 with MSDE 2000 installed may be vulnerable to the Slammer worm =

Article ID: 814373

Article Last Modified on 11/24/2006

-

APPLIES TO


 * Microsoft Visual FoxPro 7.0 Professional Edition
 * Microsoft SQL Server 2000 Desktop Engine (Windows)

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



INTRODUCTION
This article explains how you can help protect your computer from the Slammer worm when you install Microsoft SQL Server 2000 Desktop Engine (MSDE 2000). When you install Microsoft Visual FoxPro 7.0, you may choose to manually install MSDE 2000. If you install MSDE 2000, you may be vulnerable to the Slammer worm. (The Slammer worm is also known as the Sapphire worm.) For more information about the Slammer worm, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/alerts/slammer.mspx

Note By default, MSDE 2000 is not installed when you install Visual FoxPro 7.0. To install MSDE 2000, you have to run a separate installation process.



How to help protect computers that have MSDE 2000 installed from the Slammer worm
You can help protect your computer from the Slammer worm by applying Microsoft SQL Server 2000 Service Pack 3 (SP3). To download the service pack, visit the following Microsoft web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&DisplayLang=en

How to apply SQL Server 2000 SP3
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To apply SQL Server 2000 SP3 to the instances of MSDE 2000 that are installed on your computer, follow these steps:  Identify the Product Code for the MSDE 2000 instance.  For the default instance of MSDE 2000  Click Start, click Run, type regedit in the Open box, and then click OK.  In Registry Editor, locate and then select the following registry key:

 In the right pane of Registry Editor, double-click ProductCode. Note the string value in the Value data box. This value represents the Product Code. Click OK, and then quit Registry Editor.</li></ol> </li> For the named instance of MSDE 2000 <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type regedit in the Open box, and then click OK.</li> In Registry Editor, locate and then select the following registry key:

</li> In the Microsoft SQL Server key, locate and then select the registry key that represents the named instance of MSDE 2000.

Note You may have multiple named instances of MSDE 2000 installed. Each named instance has a unique registry key.</li> Locate and then select the Setup key under the named instance key.</li> In the right pane of Registry Editor, double-click the ProductCode key. Note the string value in the Value data box. This value represents the Product Code.</li> Click Cancel, and then quit Registry Editor.</li></ol>

Note If multiple named instances of MSDE 2000 exist, repeat steps b through e until you have identified the ProductCode string value of each named instance.</li></ul> </li> Identify the Microsoft Windows Installer (.msi) file that corresponds to the Product Code that you noted in step 1. To do this, use the ProductCode to Original Package Name mapping table in the following Microsoft Knowledge Base article. This table lists the Original Package Name that corresponds to the ProductCode string.

311762 How to identify which MSI file was used for an existing MSDE installation

Note To apply SQL Server 2000 SP3, you must have the name of the Windows Installer file that was used to install the instance of MSDE 2000.</li> Download SQL Server 2000 SP3 for Desktop Engine. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&DisplayLang=en

</li> Select the language in the Full Download list, and then click Go.</li> Locate the download link to the SQL2KDeskSP3.exe file. Click the download link to start the download.

Note Non-English versions of the download are listed as  _SQL2KDeskSP3.exe. In this example,  represents the language version of the download.</li> When you receive a prompt, save the file to your computer's Desktop.</li></ol> </li> Extract the SQL Server 2000 SP3 setup files: <ol style="list-style-type: lower-alpha;"> On your computer's Desktop, double-click the Setup file.</li> <li>In the License Agreement dialog box, click I Agree to accept the License Agreement.</li> <li>In the Installation Folder dialog box, type c:\sql2ksp3 in the Installation Folder box, and then click Continue.

Note If the C:\Sql2ksp3 folder does not exist, click Yes in the PackageForTheWeb dialog box.</li></ol> </li> <li>Run the Setup.exe program to apply SQL Server 2000 SP3 to an MSDE 2000 instance. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, click Run, and then type the following command in the Open box:

c:\sql2ksp3\msde\setup.exe /upgradesp c:\sql2ksp3\msde\setup\SqlRun .msi SECURITYMODE=SQL UPGRADEUSER= UPGRADEPWD=

In this example, SqlRun .msi is the Windows Installer file that you identified in step 2. For example, this file may be named SqlRun01.msi.

Note If multiple named instances of MSDE 2000 exist, repeat this step for each named instance.</li> <li>Click OK.

Note If you type an incorrect Original Package Name while you are installing SQL Server 2000 SP3, you may receive the following error message:

The instance name specified is invalid.

</li></ol> </li> <li>Restart your computer.</li></ol>

<div class="references_section">