Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 840464 - Last Review: September 18, 2011 - Revision: 3.0
You receive the "Error Number: 0x80040e4d" error message and you cannot publish new projects after you move the ProjectServer database to a new server or to a new instance of SQL Server in Microsoft Project Server 2002 and in Project Server 2003
In Microsoft Project Server 2002 and in Microsoft Office Project Server 2003, you may find that after
you move the Microsoft Project Server database to a new server or to a new
instance of Microsoft SQL Server, you cannot publish new project plans or build
On-Line Analytical Processing (OLAP) cubes. Error messages that have
descriptions that are similar to the following are logged in the event log.
Project Server 2002
File:
Drive:\Proj10\WebClient\source\utility\pjadorsutil2.cpp
Line: 1691
Error Number: 0x80040e4d
Description: Assert
Detected. The error code was also included. ___________________________________
Description: Access denied while opening project
'<PC10DSN>\resglobal'
File:
Drive:\Proj10\WebClient\source\utility\pjadorsutil2.cpp
Line: 1691
Error Number: 0x80040e4d
Description: Assert Detected. The
error code was also included.
___________________________________
Description: Access denied while opening project
'<PC10DSN>\
ProjectName.published'
Project Server 2003
File: Drive:\Office\Dev\Project\WebClient\Source\Utility\Pjadorsutil2.cpp
Line: 1691
Error Number: 0x80040e4d
Description: Assert Detected. The error code was also included.
This issue occurs if both of the following conditions are
true:
- You moved the Microsoft Project Server database to a new
server or to a new instance of SQL Server.
- The connection settings for the existing data source name
(DSN) on the server are not updated to use the new location of the
database.
To resolve this issue, create a new DSN that is named
PC10DSN and that uses the new location of the SQL Server database. To do this,
follow these steps:
- Delete the existing DSN that is named PC10DSN. To do this,
follow these steps:
- Click Start, point to
Administrative Tools, and then click Data Sources
(ODBC).
- Click the System DSN tab.
- In the System Data Sources table,
click PC10DSN, and then click
Remove.
- When you are prompted to confirm the removal, click
Yes.
- Create a new DSN that is named PC10DSN. To do this, follow
these steps:
- Click Add.
- In the Create New Data Source dialog
box, click SQL Server, and then click Finish.
The Create a New Data Source to SQL Server Wizard starts.
- In the Name box, type
PC10DSN, type the description that you want in the
Description box, and then click the server that you want to
connect to in the Server box.
- Click Next, and then follow the
instructions on the remaining pages of the wizard to create the DSN.
- Click OK.
For more information about Project Server 2002, visit the
following Microsoft Web site:
APPLIES TO
- Microsoft Office Project Server 2003
- Microsoft Project Server 2002
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