Unable to Save New Resources to resglobal

[dwolf]

We are running Project Server 2003 with SP1. We have been up and
running for about a year.

I am the Project Server Admin and for the last week, when I try to add
new resources to the global resource pool, I get a dialog box message
back stating:

[Microsoft][ODBC SQL Server Driver][SQL Server]The attempted insert or
update failed because the target view either specifies WITH CHECK
OPTION or spans a view that specifies WITH CHECK OPTION and one or more
row resulting from the operation did not qualify under the CHECK OPTION
constraint.

Clicking the OK button produces another box:

Project Server was unable to find the specified resource.
If the problem continues, contact your server administrator.

The resglobal is then locked out and must be checked back in through my
Web Access Admin account.

I have tried to add the resource through the Web Access and have no
problem doing so.

My IT department has tried rebooting both the SQL and Project Servers
without improvement. They have tried a SQL trace and come up with an
indication that the problem may lie with the Web_Admin table and the
Active Directory authentication. We are not using the Active Directory
auto-synch feature.

Other possible clues... We have had issues of late when accepting hours
into projects where the email account and windows account of seemingly
random users disappear from files even though they appear to be intact
in the global resource file.

Using the Windows Account Button in the Resource Information Screen
General Tab to validate the Windows Account brings up the correct
information and the publication proceeds without further incident.

Any suggestions would be greatly appreciated. We are running out of
options.

--DWolf

 

[dwolf]

Solution Found:

Original problem with duplicate resource required deletion through SQL
directly. Reource was deleted in MSP_RESOURCES table and
MSP_WEB_RESOURCES table, but NOT in MSP_CALENDAR table. Result was
that project would no longer accept input of new resources through
Project Professional interface.

To find the errant entry we ran a query against the three tables using
the RES_UID numbers (RES_EUID in the MSP_CALENDAR table) and looked for
exceptions.

--DWolf

 

[dwolf]

Solution Found:

Original problem with duplicate resource required deletion through SQL
directly. Reource was deleted in MSP_RESOURCES table and
MSP_WEB_RESOURCES table, but NOT in MSP_CALENDAR table. Result was
that project would no longer accept input of new resources through
Project Professional interface.

To find the errant entry we ran a query against the three tables using
the RES_UID numbers (RES_EUID in the MSP_CALENDAR table) and looked for
exceptions.

--DWolf