Unable to check Resources back in - Project Server 2007

[car...@gmail.com]

I have a bunch of Resources that, in the Resource Center, are checked
out and I am unable to check them in.

I tried the "Forced check-in" option but there are no resources
showing as checked out.
When I attempt to edit the details of the resources that are checked
out I get an unknown error message with a link to troubleshooting
SharePoint services.

Any help would be greatly appreciated.

[Jonathan Sofer]

Sorry if you have already tried this but are you sure you are viewing the
Force Check-in of Enterprise Resources and not Enterprise Projects when in
the PWA>Server Settings>Force Check-in Enterprise Objects?

Also, how do you know they are checked out, have you included the "Checked
Out" column in your Resource Center view and are they showing in that column
as checked out?

Jonathan

<car...@gmail.com> wrote in message
news:1187106480.8...@q4g2000prc.googlegroups.com...

[car...@gmail.com]

On Aug 14, 9:05 am, "Jonathan Sofer" <jonathan.sofer.m...@gmail.com>
wrote:

> > Any help would be greatly appreciated.- Hide quoted text -
>
> - Show quoted text -

Thank you for the response Johnathan and no problem -- Yes I did make
sure I selected the Enterprise Resource option in the Forced Check in
option. And yes, I do have the checked out column showing in the
Resource Center list.

Caryle

[Gregg Richie]

I had the same problem once. I had to cancel the job in the queue where I
had the resources checked out. Hope this helps.

Gregg D. Richie
Engineering Project Manager
LeRoy Surveyors & Engineers, Inc.

[car...@gmail.com]

On Aug 14, 5:08 pm, Gregg Richie

> > Caryle- Hide quoted text -

>
> - Show quoted text -

Gregg,
Thanks for the suggestion but there are no jobs stuck in the queue.
ARGH!!!

Caryle

[James Fraser]

On Aug 15, 10:28 am, car...@gmail.com wrote:
> Gregg,
> Thanks for the suggestion but there are no jobs stuck in the queue.
> ARGH!!!
>
> Caryle

We ran into a similar problem once. Try running this SQL script
against the Published database to list any checked out resources:

SELECT
RES_UID,
RES_NAME,
RES_CHECKOUTBY
FROM MSP_Resources
WHERE RES_CHECKOUTBY IS NOT NULL

In the results look at the RES_CHECKOUTBY field. In our case we saw a
resource with an entry like '00-000000-000' (That's from memory, so
not exact.)
If you have a resource in that state, you can then run this script to
check them back in:

UPDATE MSP_RESOURCES
SET RES_CHECKOUTBY = NULL
WHERE RES_UID = 'Put the res_UID from the above query here'

Of course, this is SQL to modify the Project databases directly. It's
like editing the registry: There is potential for great harm to the
system. Perform this on a test instance first; be careful; and I am
not liable for any use of this.

James Fraser