SharePoint user "does not exist or is not unique" when restoring site

We backed up the site on our development server and restored it to our production server on a different domain.
To clean up all users on the site, we used web.SiteUsers.Remove () for all users on the web root in our dev site. When taking a backup and restoring to the production server using stsadm, we get a "user does not exist or is not unique" error during the restore process, which does not work (in the stsadm -o restore command itself).

Any pointers to a solution to this or what we are doing wrong is appreciated. We are trying to remove users from the site collection before restoring them to production.

Respectfully,

+1


source to share


3 answers


Perhaps you can use stsadm -o migrateuser

( http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=75 ) or stsadm -o deleteuser

before restoring? You can see the link.



+1


source


We have a problem with your issue while installing Reporting Services. In the WSS_Content DB, some tables (.AllLists, .Webs that I can recall) had entries referencing the user in our .UserInfo table that didn’t go out in our domain. It turns out that it was a user on the development domain. Our SQL people had to run through the DB to set these records to the ID (WARNING! DO NOT SUPPORT! SEE UPDATE BELOW!) Of a user that exists on the domain. I would say your site has similar links that MOSS tries to list on import. Here's a link that sets us on the right track:

http://objectmix.com/sharepoint/298701-stsadm-export-user-cannot-found-zone-authentication.html



UPDATE (17APR09): Someone has already sorted out the author's check / reprogram bit without having to manually edit the DB:

http://blog.krichie.com/2008/09/12/resetting-the-author-on-a-sharepoint-site-or-wherefore-art-thou-author-redux/

+1


source


If you're just reaching out to AD users, then this tool called Sharepoint AD Information Sync can help you. Just as its names say the sync function is special.

Otherwise, I would rather close my mouth because I have no experience with backups.

0


source







All Articles