How to repair the Enterprise Global in Project Server 2007

May apply to 2010 version, not sure.

Help for writing this article was from the Project Server Experts blog

Symptoms: When you open the Enterprise Global from Tools, Enterprise Options, Open Enterprise Global and then go to edit a view (View, More Views) you will find that the view it brings up for editing is not the one you thought you should see, but a random view from the list.

If you can’t recover from this error from an Administrative Backup copy of your Enterprise Global File, use this document. Before you undertake the procedure below, make absolutely sure the Simple Options to try have been tested as the Enterprise Global may not be corrupt.

Simple Options to Try

1. Install the latest CU (after the August 2010 CU) on Project Pro and Server. This problem is a Project Pro Client issue, so server is not absolutely required but a best practice to install both together.

2. Delete or rename the Local Global called Global.mpt. Search for it on your PC and rename it and then open Project Pro, a new one will be auto generated. If this does not fix the issue, close Pro and rename it back deleting the Auto Generated one first.

3. Create a new Project Server account, this is the account you set up in Office Project Professional 2007 on the Microsoft Office Project Server Accounts page. You can access this page by clicking the Tools menu and then clicking Enterprise Options… Now log in with the new account and check Enterprise Global to see if problem rectified.

Last Resort, your Enterprise Global is corrupt, follow this procedure

1. Make sure you back up the Enterprise Global File  using PWA Server settings just before you make any changes to it so you always have the latest version to fall back to.

2. Start by backing up your entire system as well before you take these manual steps to recover.

3. Copy all of your Enterprise Global File objects to an mpp file. Simply by copying a server project to a drive will copy all of your enterprise views, tables and filters with the file or you can and move them to a file using the Organizer. Your enterprise custom fields are not stored in the Enterprise Global File so no worries there.

4. The next step is to run the SQL script that creates the Enterprise Global File, which you can find located in the following directory or equivalent installation directory for your system:
c:\Program Files\Microsoft Office Servers\12.0\Sql\Project Server\CORE\1033
The script to create the Enterprise Global File is named eglobal.sql.  You can run this script using Query analyzer.

5. Now open and check out Ent Global, then open the MPP file where you saved all of the artefacts and use the organizer to move everything back to the Enterprise Global File.

6. Remember to save your Enterprise Global File before you close it.

Tips and Best Practices for Handling the Enterprise Global File:

1. Run  weekly or monthly administrative backups of your Enterprise Global File

2. Always make a backup of your Enterprise Global File before making changes to it.

3. Create views and other project artefacts without opening the Enterprise Global File and open the file only when you have objects that are ready for transfer to the file.

4. Plan and manage your work so that you open your Enterprise Global File as little as possible during busy times.

5. The most common cause of corruption happens when you close the Enterprise Global File without first saving the file. To avoid this problem, always save your Enterprise Global File before closing it.