Issues that may occur on a Microsoft Windows Small Business Server 2003-based computer after you remove an MSDE 2000 SP4 instance, a SQL Server 2000 Desktop Engine (Windows) SP4 instance, or a SQL Server 2000 SP4 instance

Article translations Article translations
Article ID: 920899 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario. You remove a Microsoft SQL Server 2000 Service Pack 4 (SP4) instance on a Microsoft Windows Small Business Server 2003-based computer. Then, all Microsoft SQL Server Desktop Engine (also known as MSDE 2000) instances and SQL Server Desktop Engine (Windows) instances may stop responding on the computer.

In this scenario, you may experience one or more of the following symptoms:
  • You cannot connect to the Microsoft Windows SharePoint Services companyweb Web site. Additionally, when you try to open the Web site, you receive the following error message:
    Cannot connect to the configuration database.
  • In the Application log, you may also receive error messages that resemble the following:
    Event Type: Error
    Event Source: Windows SharePoint Services 2.0
    Event Category: None
    Event ID: 1000
    Date: 1/11/2005
    Time: 5:34:37 PM
    User: N/A
    Computer: ServerName
    Description: #50070: Unable to connect to the database STS_Config on ServerName\SharePoint. Check the database connection information and make sure that the database server is running.
    Event Type: Error
    Event Source: Windows Server Update
    Event Category: Update Services Service
    Event ID: 421
    Date: 1/11/2005
    Time: 5:34:37 PM
    User: N/A
    Computer: ServerName
    Description: Connection to database failed. Reason=SQL Server does not exist or access denied. Connection string: Data Source=ServerName\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling=’true’;Max Pool Size=100
    Event Type: Error
    Event Source: Microsoft Firewall
    Event Category: Log
    Event ID: 7
    Date: 1/11/2005
    Time: 5:34:37 PM
    User: N/A
    Computer: ServerName
    The Microsoft Firewall was unable to open ADO connection. The MSDE Error description is: Invalid connection string attribute. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. For more information about this event, see ISA Server Help.
  • The Windows Small Business Server 2003 Monitoring and Reporting MMC snap-in does not function as expected. Reports may not contain the expected information.
  • If Microsoft Windows Server Update Services (WSUS) is installed as in Windows Small Business Server 2003 R2, the update functionality will stop working.
  • If Microsoft Internet Security and Acceleration (ISA) Server 2004 is installed, client computers may be unable to access the Internet or any server resources. This includes both outgoing and incoming connections.
  • The Volume Shadow Copy Service (Shadow Copy) copies may fail.
  • Backups that use the NTBACKUP program may include warnings. System state backups may not work.
  • The VSSADMIN LIST WRITERS command may take a very long time to complete.
  • Other programs that use a SQL Server database back end, such as Microsoft Small Business Accounting, may stop working.
Additionally, consider the following scenario. You perform one or more of the following tasks on a computer that is running Windows Small Business Server 2003 R2:
  • You remove all the SQL Server Desktop Engine (Windows) SP4 and MSDE 2000 SP4 instances.
  • You install SQL Server 2000 SP4, and then you remove SQL Server 2000 SP4.
In this scenario, when you try to open WSUS or when you try to open Windows Small Business Server 2003 Update Services on a Windows Small Business Server 2003-based computer, you may receive the following error message:
Failed to load msxmlsql.dll
Additionally, the Small Business Server Monitoring and Reporting snap-in may fail to open, and the following event may be logged:
Event Type: Error
Event Source: ServerStatusReports
Event Category: None
Event ID: 1
Date: 9/30/2006
Time: 4:05:15 PM
User: N/A
Computer: ServerName
Description: Server Status Report: URL: http://localhost/monitoring/perf.aspx?reportMode=0
Error Message: Failed to load msxmlsql.dll.
Stack Trace: at Micro
For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
918767 Programs may fail when you remove an instance of SQL Server 2000, MSDE 2000, or SQL Server 2000 Desktop Engine (Windows)

CAUSE

  • You receive the "Cannot connect to the configuration database" error message when you remove an instance of SQL Server 2000 SP4. In this case, the Shared Memory protocol option is turned off.
  • Typically, the "Failed to load msxmlsql.dll" error message occurs when one or both of the following conditions are true:
    • You remove all the Microsoft SQL Server Desktop Engine (Windows) SP4 and MSDE 2000 SP4 instances.
    • You remove a SQL Server 2000 SP4 instance.
    In this case, you can remove the Msxmlsql.dll file from the computer. However, other SQL programs may still require this file. If you receive this error message, you must restore the Msxmlsql.dll and Msxmlsql.rll files. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
    918767 Programs may fail when you remove an instance of SQL Server 2000, MSDE 2000, or SQL Server 2000 Desktop Engine (Windows)

WORKAROUND

If you cannot connect to any MSDE 2000 instance or SQL Server Desktop Engine (Windows) instance on the Windows Small Business Server 2003-based computer, you may have to turn on the Shared Memory protocol option. To do this, follow these steps:
  1. Click Start, click Run, type cliconfg, and then click OK.
  2. In the Client Network Utility dialog box, click to turn on the Enable shared memory protocol check box, and then click OK.
  3. Restart the computer.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to remove SQL Server 2000, MSDE 2000, or the SQL Server 2000 Desktop Engine (Windows), click the following article number to view the article in the Microsoft Knowledge Base:
918767 Programs may fail when you remove an instance of SQL Server 2000, MSDE 2000, or SQL Server 2000 Desktop Engine (Windows)

Properties

Article ID: 920899 - Last Review: December 3, 2007 - Revision: 2.3
APPLIES TO
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
Keywords: 
kbtshoot kbprb KB920899

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com