none
User Synchronization (Add Operation) Constant Failure RRS feed

  • Question

  • Project Server 2010: Currently we are seeing nightly failures on the job 'User Synchronization (Add Operation) for Project Web App App Root Site and Project Sites'. The ULS log indicates that it fails due to a deadlock:

    PSI: SqlException occurred in DAL:  <Error><Class>51</Class><LineNumber>17</LineNumber><Number>1205</Number><Procedure>MSP_WEB_SP_QRY_IsUserValidForWssSync</Procedure>  <Message>  System.Data.SqlClient.SqlError: Transaction (Process ID 231) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

    Checking the activity and logs on the database server this is really the only process that runs at this time. Also if we try to run it manually at any time it will fail almost every time. It almost looks like it gets into a deadlock with itself

    Has anybody seen anything similar or have any idea what we can further check here?


    Regards, Stig
    Tuesday, May 10, 2011 8:43 AM

Answers

  • After testing with checked-out resources we do not have a clear conclusion. We forced two resources to be checked out on a test instance. The User Synchronisation job ran successfully overnight. Whether this is because checked-out resources do not affect the job or it is just a coincidence is hard to tell.

    Anyway, in production we changed the jobs to run at another time and that seems to have had an effect as the job has now run successfully for the last three days. This is a bit strange since we have checked that no other jobs are running at the time it was originally scheduled. Maybe there is some other job that project server runs that we are aware of.

    It seems to be resolved now.


    Regards, Stig
    • Marked as answer by Stig Friday, May 13, 2011 8:30 AM
    Friday, May 13, 2011 8:30 AM

All replies

  • Hello Stig

    Sounds like resource is checked out and resource updates need to occur.

    Make sure all your Resources are checked in.  Very similiar to checking in projects, that need checking back in.

    Cheers!


    Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA
    www.WhartonComputer.com
    Tuesday, May 10, 2011 7:20 PM
    Moderator
  • Thanks for the tip, Michael.

    I will make sure that all our resources are checked in tonight and we'll see overnight. Seems a bit strange though that this would give an error with WSS membership, but stranger things have happened.


    Regards, Stig
    Wednesday, May 11, 2011 8:25 AM
  • After testing with checked-out resources we do not have a clear conclusion. We forced two resources to be checked out on a test instance. The User Synchronisation job ran successfully overnight. Whether this is because checked-out resources do not affect the job or it is just a coincidence is hard to tell.

    Anyway, in production we changed the jobs to run at another time and that seems to have had an effect as the job has now run successfully for the last three days. This is a bit strange since we have checked that no other jobs are running at the time it was originally scheduled. Maybe there is some other job that project server runs that we are aware of.

    It seems to be resolved now.


    Regards, Stig
    • Marked as answer by Stig Friday, May 13, 2011 8:30 AM
    Friday, May 13, 2011 8:30 AM