PWA - Site Collection Information Missing.

[Dan]

Greeting Again,
We can not longer access PWA.
We can access some of the subsites.
Project Professional connectivity seems fine except we can no longer access
the Enterprise Resource Pool (associated with PWA)
We were Synching with AD but I not sure that was related.

When I view the Site Collection infromation
Central Administration > Application Management > Site Collection List
And select /PWA there is no infromation displayed.
I have several other sites and they are OK.
Any clue how to recover from this
Thanks for all the help.
--Dan

 

[Marc Soester [MVP]]

Hi Dan,

this is from a post I have picked up previously. Please note this is NOT my
response but the reponse of someone who has had a simular problem. this may
help you:

----- from post within the user group ------
There are definite issues with AD sync. Two of our customers have
been experiencing the following issue, and Microsoft said it will be
resolved with SP1 (no street date yet).

Resources will become "stranded" in the Published database. What this
means is that when you look at them in PWA, they do not appear to be
checked out. If you go to Database Administration | Force Checkin
Enterprise Objects, the resource does not appear as checked out.
However, AD will fail to sync if you look at the app server log and
will list resources as being checked out. This will prevent the
users from being able to log-on to the system.

Right now, the workaround is that the DBA or someone with database
access will need to check the actual Project Server published database
in SQL Server and manually check them back in. In the Published
database, MSP_RESOURCES table, check the RES_CHECKOUTBY column. If
the value for those checked-out resources is 0000, then it's the known
issue. You will have to manually set those resources status to NULL.

Because this happens on a daily basis to our customers, and it is so
random, they have elected to turn off AD sync at this time and
manually add resources when necessary through PWA.

I know that this is not optimal, but I wanted to share this in case
you encounter this.