Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 292644 - Last Review: February 21, 2007 - Revision: 2.2
STS: Error Message After You Change Password: ADO Error 80040E4D: Login Failed for User 'sa'
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Â
(http://kbalertz.com/Feedback.aspx?kbNumber=256986/EN-US/
)
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.
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- In Registry Editor, expand the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Web Server\OWS Metadata Stores\SQL MDStore1
- In the right pane, record the Data value that corresponds to the DNS entry. For example:
Provider=sqloledb;Server=server name;Database=Default_Web_Site_Collab
- Quit Registry Editor.
- On the Office Server Extensions Database Settings page, type the server name that you recorded in step d in the SQL Server box.
- In the Database Name box, type the name of the database that you recorded in step d.
- In the User Id box, type sa.
- In the Password box, type the new database connection password, and then click Submit.
- Restart the server computer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about configuring SQL database passwords, click the article number below
to view the article in the Microsoft Knowledge Base:
222828Â
(http://kbalertz.com/Feedback.aspx?kbNumber=222828/EN-US/
)
Err Msg: Microsoft OLE DB Provider for ODBC Drivers Error '80040e4d'
APPLIES TO
- Microsoft SharePoint Team Services
- Microsoft FrontPage 2002 Server Extensions
| kbbug kberrmsg kbnofix KB292644 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate