Error when attempting to open a Project file.

[Henri]

When trying to open a password protected Project 2002 file
I get the following error after I provide the password:

-----------
The operation cannot be completed because the source file
contains invalid project data or the total number of rows
would exceed the limit of 1 048 000 rows in a project.

Validate the data in the source file, insert fewer rows,
delete some rows, or consider dividing your project into
subprojects to provide more space for tasks and resources.
-----------

After that nothing happens (file does not open).

Tried to open it with the following:
2002
2002 + hotfix mentioned in article:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/81
2/6/44.asp&NoWebContent=1
2000
2003
2003 SP1

Same error in all of them. I also went thru the
troubleshooting steps for corrupt .mpp files:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;318438&Product=PRJ

If anyone has any idea on how to resolve this I would
truly appreciate it.

Br,

-Henri

 

[Gary L. Chefetz \(MVP\)]

This issue usually occurs when a Project File *.MPP that was/is password
protected is saved and published to Project Server. Due to the password
protection, the plan becomes corrupt. See the Microsoft Knowledge Base
article - PRJ2002: Project Plan with a Password Is Damaged When You Save the
File to a New Name
http://support.microsoft.com/default.aspx?scid=kb;en-us;812644


--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

 

[Guest]

Hello,

Yes, I saw that article and included it in my post (the
link) as well. ;-) The problem is that the hotfix or the
SP1 mentioned do not help in fixing a file that has
already had that occur to them - it only helps to stop the
problem from occurring in the future. =(

-Henri

 

[Gary L. Chefetz \(MVP\)]

Henri:

That's correct. There's not way to fix corruption like this. Revert back to
a copy of the plan before you imported it into Project Server, remove the
password and import it again. This time without the password protection.
Password protection does not apply in the Enterprise environment as security
is handled by the server, not the individual.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-