D
dstrand
I have a Project/SharePoint 2007 application server on a virtual machine.
The SQL databases are on another machine. I have two instances of PWA sites.
On one of the instances, one project is corrupt. I cannot open this project
from Project 2007 Pro, it exits immediately and in the event logs is this
message:
Faulting application winproj.exe, version 12.0.4518.1014, stamp 45428184,
faulting module winproj.exe, version 12.0.4518.1014, stamp 45428184, debug?
0, fault address 0x00b10fb8.
No other projects on this or the other instance are affected.
The corrupted project can be worked with in Project Web Access with no issue
(save and publish, resources, tasks, viewing in Project center, etc) If I
try to edit or edit in read only mode from project center (which brings up
project pro 2007) project pro closes immediately though.
I sent the databases to Microsoft, and even the known good databases cannot
open this project. Microsoft gets the same results I do.
If I cannot recover a corrupted project even with known good databases, this
will not bode well for my test implementation of project, it will never make
it into production.
Anyone else have corrupted project 2007 issues?
The SQL databases are on another machine. I have two instances of PWA sites.
On one of the instances, one project is corrupt. I cannot open this project
from Project 2007 Pro, it exits immediately and in the event logs is this
message:
Faulting application winproj.exe, version 12.0.4518.1014, stamp 45428184,
faulting module winproj.exe, version 12.0.4518.1014, stamp 45428184, debug?
0, fault address 0x00b10fb8.
No other projects on this or the other instance are affected.
The corrupted project can be worked with in Project Web Access with no issue
(save and publish, resources, tasks, viewing in Project center, etc) If I
try to edit or edit in read only mode from project center (which brings up
project pro 2007) project pro closes immediately though.
I sent the databases to Microsoft, and even the known good databases cannot
open this project. Microsoft gets the same results I do.
If I cannot recover a corrupted project even with known good databases, this
will not bode well for my test implementation of project, it will never make
it into production.
Anyone else have corrupted project 2007 issues?