MPS2007, Can not open project "unexcpected error ... verify argume

[Vadim Gerya, PMP]

Hi All!
While openning project in MSP 2007 Pro from PS2007 the following error
occures

"An unexecpected error occured during comand execution .
Try the following:
-Verify that argument names and value are correct and of the correct type,
-You may have run out of memory. To free up available memory, close
projects, or windows ....
"
It is OK with memory (error occures at any computer, even on server with 12
GB RAM)
Cleaning cache does not help. (even deleting from Application data folder)
Project is correctly displayed in different project views on WEB-access.
Restoring previous version from archive does not help.
Other projects are opened correctly.
Any suggestion... ? Does anybody knows other way to restore project ...?

 

[Dale Howard [MVP]]

Vadim --

Geez, this sounds like nothing short of a disaster! Last week at a client
site, I dealt with a client project that was so seriously corrupted that the
client could not open it. Every time he tried, Project Professional 2003
crashed. I thought he was SOL (Short on Luck), but then he said, "I know
the version in PWA is correct." So, here's what we did:

1. Creating a custom detailed Project view that contains the same columns
as the task Entry table in Microsoft Project Professional.
2. Displayed the project in PWA using that custom detailed Project view.
3. Exported the project data from that custom PWA View to an Excel
workbook.
4. Saved the workbook as an XLS file.
5. Launched Microsoft Project Professional in Desktop mode only.
6. Imported the XLS file as a new project, mapping the Task Name column in
Excel to the Name field in Microsoft Project (everything else mapped
automatically).
7. Saved the project as an MPP file.

Once we confirmed that the Excel workbook imported correctly into Microsoft
Project, we deleted the corrupted project from the Project Server database.
Then we closed and relaunched Project Professional, logged into Project
Server, and imported the MPP project into the Project Server system.
Because the client uses the % Work Complete method of tracking, he did not
lose any timescaled Actual Work data, which you would risk losing if you
using the Hours of work per time period method of tracking. At least at
this point, it's one way to "fall back" to a known working project, and
exporting to Excel from PWA would eliminate any corruption problems. Just a
thought. Perhaps others have some ideas for you as well. Hope this helps.

 

[Vadim Gerya, PMP]

Thanks Dale as always !
Do not so worry , we have what we have and trying to do our best...

I thought about this way an this is appropriate when using %Work Complete
tracking.
But unfortunately cutomer uses "hours per day" tracking. Actual work
TIMESCALE data is critical for customer bussiness (EPM2007 is integrated with
ERP AXAPTA and based on actual hours from EPM2007 AXAPTA generates invoices
for each week of each project customer performs)

As you know timescaled data is binary coded and no way to show one in PWA
and export to Excel.
If problem occures in future (Microsoft does not fix one or provide any
"restore" solution) I see the possibility to write C# code using PSI to get
required data. If PSI "open project" method also fails - I do not know what
to do.

 

[Gary L. Chefetz [MVP]]

IMO, this type of situation is where you look to your SQL backups. A good
backup plan includes full daily as well as some incremental during the day.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Vadim Gerya, PMP]

Hi Gary !
The probelm that we have to rollback only ONE project. If we use fresh
backup of Draft, Publish, Reporting DBs we rollback ALL projects.


PS:
Gary and Dale - thanks for your "Ultimate Learning Guide for 2007 MSP"

 

[Gary L. Chefetz [MVP]]

If you were foolish enough to restore it over your current database, that
would certainly wipe things out. However, if you restore it to a blank
database, you could fish out the specific project from that restore and work
from there.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Vadim Gerya, PMP]

Yes , that is the way.
Thank you as always Gary.