{"id":4456,"date":"2012-07-12T15:50:03","date_gmt":"2012-07-12T07:50:03","guid":{"rendered":"http:\/\/www.sharepointboost.com\/blog\/?p=4456"},"modified":"2023-07-31T11:39:28","modified_gmt":"2023-07-31T03:39:28","slug":"sharepoint-access-denied-error-when-recreating-user-id-in-ad","status":"publish","type":"post","link":"https:\/\/www.boostsolutions.com\/blog\/sharepoint-access-denied-error-when-recreating-user-id-in-ad\/","title":{"rendered":"SharePoint “Access Denied” Error when Recreating User ID in AD"},"content":{"rendered":"

Recently I discovered an interesting thing about SharePoint user management, reusing SharePoint user IDs results in an “Access Denied”<\/strong> error.<\/p>\n

This can be replicated using following steps<\/span>:<\/p>\n

    \n
  1. Have user “A<\/strong>” as a SharePoint user.<\/li>\n
  2. Delete user “A<\/strong>” from site collection.<\/li>\n
  3. Delete user “A<\/strong>” from Active Directory.<\/li>\n
  4. Create a new account in AD with the same user “A”<\/strong> name.<\/li>\n
  5. Add user “A<\/strong>” back to SharePoint.<\/li>\n<\/ol>\n

    When logging into SharePoint using A’<\/strong>s account, results in an “Access Denied<\/strong>” error. After refreshing AD, restarting IIS, user A’<\/strong>s is still access denied.<\/p>\n

    Analysis ? I ran a complete test to see what was actually going on<\/span><\/strong>:<\/p>\n

    1. First, I add user “DeleteUser<\/strong>” to a site collection, then I go to Content Database of site collection and open the UserInfo table.<\/p>\n

    \"\"<\/a><\/p>\n

    2. I then delete “DeleteUser<\/strong>” from the site collection.<\/p>\n

    3. I check database again and find that the tp_Deleted<\/strong> column is set to the user’s ID, tp_IsActive<\/strong> column is set to 0<\/strong> and tp_Token<\/strong> is set to NULL<\/strong>.<\/p>\n

    \"\"<\/a><\/p>\n

    <\/a>4. Everything is normal till now, but then I add a new “DeleteUser<\/strong>” in AD and add it back to SharePoint.<\/p>\n

    5. However, we can see “DeleteUser<\/strong>” is back with the same data as it had before being deleted.<\/p>\n

    \"\"<\/a><\/p>\n

    The Issue<\/span><\/strong>:<\/p>\n

    The reused “DeleteUser<\/strong>” account can no longer access the SharePoint site! If we check the column tp_SystemID<\/strong> for which SID is being used in SharePoint, we find that this SID has not been changed. This is the explanation given by Microsoft: “when you added the user information to SharePoint, SharePoint updated the user’s existing entry in the UserInfo<\/strong> table instead of creating a new entry. However, the user security identifier (SID) in the old entry is no longer correct.” (please refer to kb982949<\/a>)<\/p>\n

    Resolution<\/span><\/strong>:<\/p>\n

    I resolved the issue by deleting the “DeleteUser<\/strong>” entry in database and added this user again in SharePoint. However, this is not a very good way, as I have to reassign user’s permissions.<\/p>\n

    The right way is SharePoint 2010 Management Shell<\/span><\/strong>:<\/p>\n

    1. On the server that is running SharePoint, open Management Shell and type the following command<\/p>\n

    <\/strong><\/p>\n

    stsadm.exe -o migrateuser -oldlogin Domainname\\OldUserName -newlogin Domainname\\NewUserName ?ignoresidhistory<\/strong><\/p>\n

    <\/strong>2. Press the “Enter<\/strong>” button.<\/p>\n

    \"\"<\/a><\/p>\n

    <\/a>3. After running the command, the database entry tp_SystemID<\/strong> changed and DeleteUser<\/strong> can once again logon.<\/p>\n

    \"\"<\/a><\/p>\n

    Note<\/span><\/strong>: Run this command only from user accounts that are in the same domain. Otherwise, you may experience other permission problems. This command automatically updates the account name and the command maintains the appropriate permissions for the account.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Recently I discovered an interesting thing about SharePoint user management, reusing SharePoint user IDs results in an “Access Denied” error. This can be replicated using following steps: Have user “A” as a SharePoint user. Delete user “A” from site collection. Delete user “A” from Active Directory. Create a new account in AD with the same […]<\/p>\n","protected":false},"author":22,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[125],"tags":[425,424,426],"_links":{"self":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/4456"}],"collection":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=4456"}],"version-history":[{"count":5,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/4456\/revisions"}],"predecessor-version":[{"id":9207,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/4456\/revisions\/9207"}],"wp:attachment":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=4456"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=4456"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=4456"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}