Skip to main content

Project Server Help Blog

Go Search
Project Server Help Blog
Project Server Experts Community
MSProjectExperts
Training Schedule
Contact Us
  

Project Server Help Blog > Posts > Project 2007 Client Damages Project Server E-Global Bug in SP2
 

 MS Project and Project Server Resources

 
Project 2007 Client Damages Project Server E-Global Bug in SP2

We 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.

Comments

SP2 MSP Views

In a fully SP2 environment (PS and MSP) I have not had a problem with the e-global, however with MSP SP2 and PS Pre-SP2 I have had problems with MSP views getting "cross-wired".

In a fully SP2 environment my enterprise templates have also displayed this behaviour
at 6/16/2009 4:18 AM

Version Mis-match

Thanks for this guys. We ran into this issue with one of our clients

Would rolling back the client software to a version that did not match the server cause other problems?

Cheers
Shane
at 6/16/2009 7:05 AM

Response to Comments

The version mismatch will not be a problem. Roll back to SP1 Plus April CU and you'll be ok.

With regard to the "cross-wired" views, the problem/danger is that if you open and save the E-Global file, the mixed-up data saves to the e-global file and becomes a systemic problem rather than just an oddity in the way the client is displaying the views. Do not edit your E-Global while the client is in this state. That is the important takeaway here.

Gary
Gary Chefetz at 6/17/2009 10:13 AM

SP2 MSP Views

I am doing test for SP2 by taking multiple of scenario but didnt found this issue with EGlobal when working on enevironment MSP2007 SP2 + PS2007 SP1
Can you let me know what exactly the issue?

at 7/6/2009 1:13 AM

Aug CU

Microsoft have informed us that they will release a fix in the August CU
at 7/15/2009 5:50 AM

Add Comment

Spam Test

Unfortunately, spammers have made our lives a bit more annoying.
Please help us take a bite out of spam.

Before submitting a comment, please prove that you are not a spam bot
by using the buttons to enter the number shown below:



          

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Title


Body *


Commenter Name


Website URL

Type the Web address: (Click here to test)  

Type the description: 

Attachments