Queue Error when changing Admin group members

[oldbradfordian]

I am using MS Project Server 2007, and now when I add a user to the Admin
group, I get an error as follows:

------------------------------------------------------------
Your SynchronizeSingleUserMembershipInWss job failed. Its current state is
FailedNotBlocking. It was 50% complete. It entered the queue at 06/24/2008
16:03:28.

Error summary/areas:
Queue
GeneralQueueJobFailed
Error details:

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="1976e00b-1dcc-4262-a0ba-a1b20337dd73"
JobUID="d02c4861-7310-4949-bb3b-e11affa7e819" ComputerName="PROJECT2007"
GroupType="SynchronizeSingleUserMembershipInWss"
MessageType="SynchronizeSingleUserMembershipInWssMessage2" MessageId="2"
Stage="" />
</class>
</general>
</errinfo>

--------------------------------------------------------------------

The following info is also logged in the Office SharePoint Server, category
"Project Server Queue", Type "Error", Event ID: 7704.

I also notice that intermittently some Admin users cannot login (they get an
Access Denied message).

This problem started occurring yesterday. We have been running OK wiithout
any errors for a couple of months until now.

Does anyone have any ideas what is causing this error and what I can do to
fix it?

Thank you.

 

[Jonathan Sofer]

When you save changes to a security group or to a user, all users in that
group are removed from PWA and WSS access and re-added during the WSS_Synch
job you specified. This would explain why some users, even ones with admin
access, sometimes get access denied while their accounts are being re-added.

I can't say for sure why the queue job failed at 50%, maybe there is one
user or one site that is having issues. I would try and re-save the admin
security group and see if the queue jobs completes this time.

 

[oldbradfordian]

Thanks, Jonathan, I wasn't aware of the remove and re-add functionality.

I've re-saved the problematic users as well as all categories, security
templates and groups. However, I still have the problem.

I also have some additional information now. I repeated the same steps on a
dev sandbox (not teh same as the 'live' server), and I cannot reproduce the
error. I tried making changes just as they were made to the live server:
adding and changing users and changing their group assignments. It works just
fine, with no queue errors and no login issues. This only occurs on the live
server.

This would suggest corruption somewhere (maybe something hiccuped during a
save)? Any ideas how to try and find what's broken?

Thanks.

 

[Jonathan Sofer]

Sounds like there is some corruption possibly in one of the users you are
trying to synch or somewhere else. What service pack are you on for
starters?

Have you done any searches on the specific error codes provided in the the
queue job failure notification? I know its a stretch but it might yield
something.

 

[oldbradfordian]

Update...

The problem worsened so that the users in the Admin Group could no longer
access any project workspaces either.

But the good news is I have now fixed my problem! Here is what I did:

1. Login as an Admin user.

2. Go to "Server Settings".

3. Go to "Project Workspaces".

4. One by one, select (highlight) each project and then click on
"Synchronize".

Now all Admin users can access all the projects, and I do not get the error
message when I save Admin users.

Hopefully this info may help others if they run into a similar problem.

 

[ukraine]

1. Login as an Admin user.
2. Go to "Server Settings".
3. Go to "Project Workspaces".
4. One by one, select (highlight) each project and then click on
"Synchronize" but by turn. You must monitoring this process and runing next
synchronization only after first was ended.

It happens because a few tasks try to get access to one object that results
we have deadlock in database.