Before I give some recommendations, I want to verify some assumptions first.
1) I am assuming by "Suddenly" that you have been using Project Server for
a little while and everything has been working.
2) I am assuming you are using the Enterprise Features of Project Server
and have used the Enterprise Global and Enterprise Resource Pool.
3) This problem with Project Pro is happening on all machines and not just
a few.
4) This error is happening with different user accounts that were once
working.
If all of the above assumptions are true then I believe you have a corrupted
Enterprise Global. You have a couple of options here depending on whether
you have a backup of the Project Server database. And you do don't you!
1) If you have a backup of your Project Server database, I would recommend
you revert to it by following the directions in the link below.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;323330
If you do have a backup but it is sufficiently old, there are ways we can
restore the database to another instance of Project Server so that we can
steal the bits and pieces that we need. However, since that is convoluted,
I am hoping you have a recent copy of your database.
2) Restore to the automatic backup of the Enterprise Global that Project
Server stores in its database.
NOTE: This information is based on a version of my Project Server database
that I believe will work for the majority of Project Server installations.
a) MAKE A BACKUP OF THE PROJECT SERVER DATABASE USING THE LINK ABOVE
BEFORE MAKING ANY CHANGES TO THE DATABASE DIRECTLY!
b) Disconnect the server from the network or otherwise ensure that
users aren't connecting to the Project Server database.
c) Open up the SQL Server Enterprise Manager (Start Menu --> Program
Files --> Microsoft SQL Server --> Enterprise Manager)
d) Navigate the tree <Servername> --> Databases --> <Project Server DB
name> --> Tables
e) Right-click on the MSP_PROJECTS table and select Open Table -->
Return All Rows.
f) Look for two rows that start with "global" followed by a date code
(similar to global20030422102642)
g) The PROJ_TYPE field to the far right identifies the project as
follows
1002 means it is the backup Enterprise Global
2 means it is the active Enterprise Global that Project
Server/Pro uses
h) You need to swap the following entries between the two globals
PROJ_READ_ONLY
PROJ_READ_WRITE
PROJ_READ_COUNT
PROJ_LOCKED
PROJ_TYPE
PROJ_CHECKEDOUT
i) Select a cell in another row besides the two you have been updating.
This will ensure the settings for the row you were just editing are saved.
j) Close the SQL Server Enterprise Manager
k) Open Project Pro and hope it connects to Project Server without
incident.
l) If it there are no more issues, immediately close Project Pro and
backup your database.
m) Make sure you setup a scheduled backup or SQL Server maintenance
plan to regularly backup the Project Server and STS databases.
3) You can try to restore a blank Enterprise Global but you will lose any
customizations you had.
a) Open Project Professional and connect to My Computer.
b) Save a blank project to your hard drive.
c) Go to Tools --> Enterprise Options --> Restore Enterprise Global...
d) Specify a valid administrator account and the blank project you
saved to the hard drive.
e) Restart Project Pro.
4) If you don't have too much information in Project Server, you could
rebuild the database by using the manual SQL scripts.
a) Open the command prompt
b) Navigate to the Support\Database directory on your Project Server
2002 CD
c) Run the SetupDB command as follows
SetupDB <SQLServer> <DatabaseName> <SQLAccount(sa)> <Password>
d) Once that runs, you should be able to connect in as Administrator
with a blank password.
Good luck!
David
