locked
Project Server 2010 - Active Directory Sync GUID Mismatch RRS feed

  • Question

  • Hello,

    One of our Project Server users was deleted and created again in the Active Directory, creating a mismatch of the IDs when syncing Project Server with the Active Directory, is there any way to clean the IDs so my user can be synced again.

    Thanks for any help.

    Wednesday, September 25, 2013 2:49 PM

Answers

  • Hi there,

    I would get a test AD user account that doesnt exist in PWA  or any other AD account that doesnt exist in PWA, update your user in PWA > Server Settings > Manage Users, update the User Logon Account - add the Test AD account and save the user. Now edit the user again but this time remove the Test AD account from the User Logon Account field and enter the users correct AD account that has been recreated in AD then save the user. Re-test the AD sync. I would try to avoid any direct DB updates where possible :)

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    • Proposed as answer by Barbara HenhaplMVP Wednesday, September 25, 2013 5:44 PM
    • Marked as answer by PWMatherMVP Thursday, April 17, 2014 12:05 PM
    Wednesday, September 25, 2013 5:05 PM

All replies

  • Hi Angel,

    this is the only hack I would ever make in DBs directly. And so far, it is the only solution for this error I am aware of.

    You can do the following in Published DB:

    UPDATE MSP_RESOURCES SET WRES_AD_GUID = NULL WHERE WRES_ACCOUNT =
    'Domain\enternamehere'

    and run sync once more afterwards.

    Regards
    Barbara

    Wednesday, September 25, 2013 3:26 PM
  • Hi there,

    I would get a test AD user account that doesnt exist in PWA  or any other AD account that doesnt exist in PWA, update your user in PWA > Server Settings > Manage Users, update the User Logon Account - add the Test AD account and save the user. Now edit the user again but this time remove the Test AD account from the User Logon Account field and enter the users correct AD account that has been recreated in AD then save the user. Re-test the AD sync. I would try to avoid any direct DB updates where possible :)

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    • Proposed as answer by Barbara HenhaplMVP Wednesday, September 25, 2013 5:44 PM
    • Marked as answer by PWMatherMVP Thursday, April 17, 2014 12:05 PM
    Wednesday, September 25, 2013 5:05 PM
  • Hi Paul,

    thanks, great idea. I will keep it in mind. So now I lost my only case DB manipulation. :-).

    Regards
    Barbara


    Wednesday, September 25, 2013 5:48 PM
  • Thanks,

    Should I sync when I add the test user? It still isn't syncing correctly.

    • Edited by Angel Moret Thursday, September 26, 2013 3:16 PM edit
    Thursday, September 26, 2013 3:15 PM
  • No harm in try it.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, September 26, 2013 5:13 PM
  • Project Server registered the new GUID, but the user still gets an access denied page when he enters.  Does the user need to be altered from any other places?

    Friday, September 27, 2013 2:58 PM
  • Hello, Did you try and access PWA when the test AD account was associated with this user account? Could you access PWA then using the test AD account credentials? Paul

    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Friday, September 27, 2013 6:56 PM