I totally hosed Sharepoint Services

Posted on 2007-07-24
Last Modified: 2008-01-09
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?
Question by:msdurham
    LVL 15

    Accepted Solution


    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?)


    Author Comment


    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

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    Join & Write a Comment

    There is one common problem that all we SharePoint developers share: custom solution deployment. This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspectiv…
    Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
    Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
    This video discusses moving either the default database or any database to a new volume.

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now