Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > SharePoint 2010 Forums > SharePoint 2010 - Setup, Upgrade, Administration and Operation > Error: The specified user or domain group was not found.

Answered Error: The specified user or domain group was not found.

    •  
      Thursday, September 23, 2010 3:55 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi all,

      So I am having this issue with SharePoint Central Administration. I am not able to get into many of the services within CA due to the above error. I have narrowed it down (I'm almost positive) to a user who was an administrator on the managed metadata service and is no longer with us and was removed from the AD. I have asked to have the account added back in, of course, we don't have the SID history. It was added and I used the stsadm cmdlet migrateuser -ignoresidhistory and I get the same exact error. I've tried this logged on as several diffeerent administrators including the domain administrator account and have received the same error.

      Anyone have any ideas?

      Thanks

       

    Answers

    • Saturday, October 02, 2010 3:16 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      When all was said and done I had to call MS and the only solution they had was to recreate the configuration database and then attach the old content database, which we did. It did solve the problem although I did have to go thru and redo configurations. So far everything seems to be the same except Managed Metadata is no longer linked to the service, however, it's a simple opening of the item and saving again and all the connections are made again (providing that you recreated the managed metadata service exactly as it was before).
       

    All Replies

    • Saturday, October 02, 2010 3:16 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      When all was said and done I had to call MS and the only solution they had was to recreate the configuration database and then attach the old content database, which we did. It did solve the problem although I did have to go thru and redo configurations. So far everything seems to be the same except Managed Metadata is no longer linked to the service, however, it's a simple opening of the item and saving again and all the connections are made again (providing that you recreated the managed metadata service exactly as it was before).
       
    • Wednesday, January 05, 2011 11:20 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I have the same issue with an inactive user on our development box. Do you have any detailed steps on how to rebuild the config database?

      Thanks

       
    • Friday, January 07, 2011 5:27 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi Paul PC,

      I don't have detailed steps on how to do this and would be hesitant to lay out those steps as different setups may require a different approach, however, I can tell you generally what we did.

      1. We went thru the SharePoint 2010 Products Configuration Wizard and removed the server from the farm.

      2. Again thru the SP 2010 Config Wizard we added the server to a new farm using the same SQL server. Doing this creates a new config database.

      3. Go thru all the normal steps of setting up ur farm and then from Central Admin (or using STS admin cmdlts) add the old wss_content database from the previous sharepoint setup and remove the new wss_content (should be wss_content{guid}) from the new setup.

      Easy as that. I need to stress that this was an initial setup of a production sharepoint site that has not yet gone into production. So it wasn't a big deal for me to lose things. If this IS your production site, you may want to back everything up before doing anything like this and it wouldn't hurt to get some professional help if you're not comfortable with it.

      Good Luck!!