Okay, I did something bad. In cleaning up from the fallout of losing my FSMO-holding domain controller last week, I think I made things a lot worse. I'll try to sum up as best I can:
3 Servers, one running Win Server 2000 (LAND), one running Server 2003 (WATER2), and one Server 2008 R2. I transferred the FSMO roles to WATER2 and used dcpromo to make it my new domain controller. LAND was a backup DC to the one that failed. So now WATER2 was my main. We are phasing out the 2k server so I stupidly decided to make the 2008 machine a domain controller.
MACKENZIE also has SQL Server 2012 on it, and is our SharePoint server. I made MACKENZIE a DC then I went back and uninstalled AD from it when it turned out that having SQL on a DC was not advisable, but now I can no longer connect to the SQL Database that hosts the SharePoint 2010.
I get this error:
Failed to connect to server MACKENZIE\SHAREPOINT
Additional information:
A network-related or instance-specific error occurred while establishing a connection to the SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 -No connection could be made because the target machine actively refused it.)(Microsoft SQL Server, Error: 10061)
Help....