Friday, March 13, 2009

Resources Checked Out And Won't Sync

This is an oldie, but a goodie! Suppose you have an automated or manually initiated Active Directory Synchronization, either on your Groups or Resource Pool. During synchronization you get a failure on a resource. The next time you try to synchronize, you get more failures, similar to this one:

Standard Information:PSI Entry Point:
Project User: DOMAINNAME\username
Correlation Id: c79f3275-d271-4d4d-b052-b5e641003f5d
PWA Site URL: http://servername/projectserver
SSP Name: SharedServices1
PSError: Success (0)
Changes were detected for a resource during Project Server Active Directory Synchronization. However, the changes could not be applied because the resource could not be checked out. The checkout failed because the resource is checked out to another user. Resource GUID: 413baade-8372-493b-b271-c417c2852d53


What’s happened is that during the process, the system will (1) check-out, (2) modify and (3) check-in the resource. However, on the first failure, the resource never got checked in. You can go to the Force Enterprise Check In and notice that the resource in question isn’t in the list as you’d expect. Don’t Panic! Here’s what to do:

Note: You will need access to the SQL Server Management Studio and an account that can write to the database to do the following:

  1. Start a new Query
  2. Select ProjectServer_Published (or whatever you named the Published DB)
  3. In the query type in the following to check back in the resources:
UPDATE MSP_RESOURCES
SET RES_CHECKOUTBY = NULL
WHERE RES_UID in (
SELECT
RES_UID
FROM MSP_Resources
WHERE RES_CHECKOUTBY = ‘00000000-0000-0000-0000-000000000000′)

No comments:

Post a Comment