T
Tom Eckels, PMP
a couple of weeks ago we experienced data corruption with projects. this
caused published updates not to propogate to the online data views including
project-center/view a project and individual time-sheets. at the time we
noticed that mssdmn.exe was unexpectadly terminating on the database server;
today we saw the corruption again where published changes were not updating
online views, with similiar error messages regarding mssdmn.exe.
I am trying to determine if the corruption issues are related to MSSDMN.exe
Searching microsoft knowledge base, I see issues where mssdmn.exe may fail
parsing microsoft word documents; is anyone aware of a similiar issue with
Microsoft Projects being published to the Project server
We have Microsoft Project Server 2003; Web Access is running on one server,
the sql database is running on a 2nd server, and the sharepoint services are
running on a third server. we use microsoft sql 2000 with sp3; All servers
are windows server 2003.
I will now have to re-export and re-import the project to correct the issue;
I am trying to see if we can find a root cause to avoid the problem in the
future.
caused published updates not to propogate to the online data views including
project-center/view a project and individual time-sheets. at the time we
noticed that mssdmn.exe was unexpectadly terminating on the database server;
today we saw the corruption again where published changes were not updating
online views, with similiar error messages regarding mssdmn.exe.
I am trying to determine if the corruption issues are related to MSSDMN.exe
Searching microsoft knowledge base, I see issues where mssdmn.exe may fail
parsing microsoft word documents; is anyone aware of a similiar issue with
Microsoft Projects being published to the Project server
We have Microsoft Project Server 2003; Web Access is running on one server,
the sql database is running on a 2nd server, and the sharepoint services are
running on a third server. we use microsoft sql 2000 with sp3; All servers
are windows server 2003.
I will now have to re-export and re-import the project to correct the issue;
I am trying to see if we can find a root cause to avoid the problem in the
future.