Enterprise Global Views Gone Wild!

[Darrell]

All,

Our facility experienced a hard crash due to a UPS failure and now all of
the Enterprise Global views are all messed up. I also noticed some of my
updating history is missing but what I need some advice on is what would be
the easiest way to fix the EntGlobal views...

When I click on the Network Diagram in the view bar I get the Calendar view,
when I click on the Enterprise Gantt I get the Detail Gantt, when I click on
the Tracking Gantt I get a custom view...etc. Some views do display correctly
but most common views do not. So I went to View>More Views…>selected the
Enterprise Gantt>Edit and sure enough the view name is Detailed Gantt, the
table is Delay. This is the same for the other views not displaying
correctly, when you open them to edit they reference a different view and
table.

The other strange thing is when I open a project schedule it does not alert
me that there is a newer EntGlobal and the views in our project schedules do
not seem to be affected.

Anyone know an easy way to recover?
Darrell

 

[Gary Chefetz]

Darrell:

Any chance that you applied Service pack 2 to your Project client? If so,
this is a bug in SP2 for the client, and as long as you don't open the
E-Global and save it, this mess will not affect your server. See our blog
posts on this subject starting with:
http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=75

 

[TonyZink]

Hi Darrell --

Are you running Project Server 2007 with Service Pack 2 (SP2)?

If so, then you may have fallen victim to a bug in SP2 which can
corrupt your Enterprise Global Template (EGT), as described here:

http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=69

If you have scheduled administrative backups configured in your
Project Server, then hopefully you can restore a good version of the
EGT from your Archive database. If you don't have a good EGT backup to
restore, then you may need to do some manual cleanup... or rebuild
your EGT in the database from scratch. Here is an article describing
how can do this if necessary:

http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=58

The article addresses a different issue, but contains instructions on
how to rebuild the EGT using a SQL script which you will need to run
on the database server.

Until Microsoft releases a fix for this issue, here are some tips for
avoiding the problem:

http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=75

Hope this helps!

----------

Tony Zink, MCTS, MCITP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server Books: http://www.projectserverbooks.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com
Project Server Web Parts: http://www.projectdaddy.com

 

[Darrell]

ahhh.... well crap. As soon as I saw the EntGlobal was messed up I opened it
and begain looking around thinking it had been caused by our hard crash...
which may have caused the bug to surface but not caused the issue itself. I
don't think we have saved the EntGlobal because we didnt want the changes to
take effect so I think we are good until September.

Thx for the information Gary,
Darrell

 

[bikerjohn]

You may also be able to use a tool like playbooks to back up / restore your
global from your dev or training enviroment (if you have multiple
enviroments). I had the same issue and used Tony's method of restoring it
from the archive database.

 

[Marc Strother]

You may also be able to use a tool like playbooks to back up / restore your
global from your dev or training enviroment (if you have multiple
enviroments).  I had the same issue and used Tony's method of restoringit
from the archive database.








- Show quoted text -

It's nice to not be the only one with this crazy problem. Misery
loves company, I suppose. I will try out the suggested fixes Gary -
thanks for the info.

Regards,

Marc