This article was previously published under Q292644
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
After you change the database connection password for your SharePoint team Web site, you cannot use your Microsoft Office 2000 Server Extensions-based Web sites for discussions or collaborations.
When you view the Application Log from within Event Viewer, you see the following Office Web Server error message:
ADO Error 80040E4D: Login failed for user 'sa'
This behavior occurs because the Office 2000 Server Extensions-based virtual servers can no longer access the Microsoft SQL Server 2000 Desktop Engine.
NOTE: The previous version of Microsoft SQL Server 2000 Desktop Engine is named Microsoft Data Engine (MSDE).
When you use the Owsadm.exe utility to change the database connection password, the Office 2000 Server Extensions installation is not configured with the new password.
To work around this issue, configure the Office 2000 Server Extensions to use the new database connection password. To do this, follow these steps:
Start OSE Administrator (HTML). If an Enter Network Password dialog box appears, type your user name, password, and domain into the corresponding boxes, and then click OK.
On the Microsoft Office Server Extensions Administrator home page, click Database Settings.
On the Database Settings page, click Change Office Database.
Type the SQL Server name and the Database name into the corresponding boxes.
If you do not know this information, follow these steps to obtain it from 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.