Comments on: User cannot be found http://waitingimpatiently.com/index.php/2009/03/23/46/ Life and times of a networking programmer. .NET, TFS, Sharepoint and servers. Sun, 05 Feb 2012 21:01:17 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Chris Auer http://waitingimpatiently.com/index.php/2009/03/23/46/comment-page-1/#comment-52 Chris Auer Wed, 02 Sep 2009 19:29:46 +0000 http://waitingimpatiently.com/?p=46#comment-52 A lot of the documentation on the User Objects seems to be a hidden secret. I hope a lot of these issues are resolved in 2010. SharePoint was designed to fit in one particular box. And as you know, the world is full of MANY different boxes. Thanks for the positive notes. A lot of the documentation on the User Objects seems to be a hidden secret. I hope a lot of these issues are resolved in 2010. SharePoint was designed to fit in one particular box. And as you know, the world is full of MANY different boxes.

Thanks for the positive notes.

]]> By: frosty http://waitingimpatiently.com/index.php/2009/03/23/46/comment-page-1/#comment-51 frosty Wed, 02 Sep 2009 19:25:24 +0000 http://waitingimpatiently.com/?p=46#comment-51 Thank you for posting this as it was a critical piece to a resolution of a serious problem we had with our test users during AD migration. During our AD migration, we were given a tool that is basically a UI for the stsadm migrateuser. Much to our suprise after running the tool, several user profiles were abandoned entirely and the items that they had modified or created showed only "Person" when clicked on "User cannot be found". We discovered that at one point, account names were changed from first initial last name (FLAST) to NewID. The result of not running migrateuser from olddomain\FLAST to olddomain\NewId was that several profiles were deleted in error (and those items were shown as "Person"). To recover the associated userdisp.aspx number, we used your posted solution to "undelete" them (fantastic by the way) and then ran migrateuser olddomain\FLAST to olddomain\NewID and then we ran migrateuser olddomain\NewID to newdomain\NewID and it resolved our "Person" issue where the profiles were abandoned. The user should not log in to SharePoint during the process. Definitely not something I would recommend if you don't have to do it, but it did work with no issues. I never would have had the confidence to go in to the tables without your post, so thank you so much for posting this. I should note that permissions for these folks were lost in the first pass of migrateuser, but recreating their rights was secondary to the "person" issue. Excuse my shorthand for migrateuser etc. If you need additional info or for me to write out the exact code for migrate user etc, please let me know. I am all too aware on the lack of documentation out there on this particular subject. Thank you for posting this as it was a critical piece to a resolution of a serious problem we had with our test users during AD migration. During our AD migration, we were given a tool that is basically a UI for the stsadm migrateuser. Much to our suprise after running the tool, several user profiles were abandoned entirely and the items that they had modified or created showed only “Person” when clicked on “User cannot be found”. We discovered that at one point, account names were changed from first initial last name (FLAST) to NewID. The result of not running migrateuser from olddomain\FLAST to olddomain\NewId was that several profiles were deleted in error (and those items were shown as “Person”). To recover the associated userdisp.aspx number, we used your posted solution to “undelete” them (fantastic by the way) and then ran migrateuser olddomain\FLAST to olddomain\NewID and then we ran migrateuser olddomain\NewID to newdomain\NewID and it resolved our “Person” issue where the profiles were abandoned. The user should not log in to SharePoint during the process.

Definitely not something I would recommend if you don’t have to do it, but it did work with no issues. I never would have had the confidence to go in to the tables without your post, so thank you so much for posting this.

I should note that permissions for these folks were lost in the first pass of migrateuser, but recreating their rights was secondary to the “person” issue.

Excuse my shorthand for migrateuser etc. If you need additional info or for me to write out the exact code for migrate user etc, please let me know. I am all too aware on the lack of documentation out there on this particular subject.

]]>