Project 2007 Client Damages Project Server E-Global Bug in SP2
13 June 2009We discovered a bug in SP2 this week that causes damage to Enterprise Global items. After editing the Enterprise Global file, Project Pro crashes on most views rendering it unusable for the most part. The good news is that this can be cured by rebuilding the Enterprise Global file, but I am suggesting that everyone who has deployed Service Pack 2 for Project and Project Server, refrain from making changes to the Enterprise Global file until Microsoft releases a patch, or have administrators roll back their client installation to SP1 + February or April CU. This problem does is not related to Service Pack 2 for Project Server, so you do not have to worry about rolling back the server, which is impossible without a complete reinstall. This problem concerns anyone who has administrative access to the system and could possibly make edits to the Enterprise Global. Project Server administrators should be notified immediately about this problem.
If you have deployed SP2 and have made changes to the Enterprise Global file, you may need to rebuild the file. About a month ago, I blogged about rebuilding the e-global file to recover from corruption in the VBA stream. The instructions outlined in the post http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=58 pertain to this problem as well. We have verified that Microsoft is aware of the problem and will release a patch very soon.
Originally from Project Server Help Blog: Posts on June 13, 2009, 7:53am
Popularity: 1% [?]
Other posts like this one:
2 Responses to “Project 2007 Client Damages Project Server E-Global Bug in SP2”
June 15th, 2009 at 4:31 am
Thanks for this.
Would rolling back the client software to a version that did not match the server cause other problems?
June 21st, 2009 at 4:08 am
Hi
Microsoft said, that this is no problem to work with Server SP2, if your clients have at least SP1 Infrastructure Update.