• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

I totally hosed Sharepoint Services

I'm totally of of ideas and I need you help.

Long story short, I hosed a perfectly good Sharepoint Services 3.0 server by promoting it to a domain controller.  Before I began my "hack and slash" repair, I stopped the SQL service and coppied all of the SQL databases to another location.

To "fix" this problem I DCPROMO'ed the server back to a member server, uninstalled SQL and Sharepoint, and did repair installs on .NET 2.0 and 3.0.  I then reinstalled Sharepoint and used the included SQL database engine.  This fresh install of Sharepoint runs just fine.  I can connect to the basic "starter" site and teh admin web sites.  My problem is restoring the origional config and content databases and sites.  

I tried stopping the SQL service (<servername>\microsoft##ssee) and copying the origional database in place and restarting SQL. Yes, I coppied all of them - master, model, sharepoint_config, wss_content... etc.  SQL started fine but I can no longer connect to the user or admin sites.  I just get "cannot connect to config database." and my SQL error log starts to fill with "Login failed for user nt authority\netowrk service".  

I've tried everything I can think of to get the old databases working.  It appears from other logs that besides the login errors, the Sharepoint site is looking for the fresh install databases.  I'm a SQL Server DBA by trade but I don't have much experience with Sharepoint.  I really need to get the origional config and content databases running so I can get the origional sites back.  

Any ideas?
1 Solution
Tim HumphriesCommented:

I think you should have left master and model alone and not copied over the sharepoint config db. Try again, this time do not overwrite any of these and then 'restore' your site from your backup of the wss_content database (do you have copies of services and profile dbs too, as you'll need those?)

msdurhamAuthor Commented:

I can't do that because each of the Sharepoint databases are named with the SID as part of the DB name.  So, instead of WSS_CONTENT I have WSS_Content_596cf0d1-214b-47f2-b315-398827975a2f.  The "before" and "after" databases all have unique SIDs.

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now