SBS SQL Databases No Longer Connecting
The SBS 2008 databases, including SBSMONITORING, MICROSOFT###SSEE and SUS databases are no longer connecting. One of the errors I receive is "The configuration of the AdminConnection\TCP protocol in the SQL instance MICROSOFT##SSEE is not valid." This started when I had to move the data from one physical drive to another. I shut down all database services, copied the data to the new location, removed the logical drive letter from the old path and added it to the new path (hoping this would just work). Unfortunately, these databases and their respective sites no longer are connecting. I cannot open the companyweb, nor is Update Services operational. Is there some type of configuration in SQL or the registry that uses Arc paths to the physical drive? Again, the new path has the exact same logical drive path as the original location (in this case J:\Windows\SYSMSI\SSEE\MSS
ASKER
I went into Disk Manager, removed the logical path (J:) from the old HD and added that path to the new HD. As you can tell, I'm not a DB Admin. I dismounted the WSUS db, but didn't for the other sites (because I don't know how). I think I have the WSUS db back online, so now it is just Sharepoint sites that are messed up.
Wow. Was SQL installed to J as well? I'm guessing so, which is why none of the services started. I suggest you switch everything back, if possible.
You said you have WSUS running now. So are the SQL services now starting?
You said you have WSUS running now. So are the SQL services now starting?
ASKER
ACH1LLES: I can't move it back because the original physical drive is gone. My OS partition on that drive ran out of space, and the J: drive didn't have enough free space to float to the OS, so I had to remove the J: partition and move it's data to another drive. It was in a critical state, so I didn't get to put a lot of preparation behind the process.
It does appear that the SQL services are starting, but even after an IIS Reset, the companyweb isn't back online. Which service do I need to restart to allow companyweb to be published? Thank you for all of your help.
It does appear that the SQL services are starting, but even after an IIS Reset, the companyweb isn't back online. Which service do I need to restart to allow companyweb to be published? Thank you for all of your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have it reconnected and all the databases remounted, but I still can't get companyweb back online. Is there something else I'm missing?
IIS is started? Is the app pools for SharePoint started in IIS?
ASKER
IIS is started, and it appears the app pools for SharePoint are also started in IIS.
What is the exact error when you try to bring up Central Admin? What about companyweb?
ASKER
Central Admin: The website declined to show this webpage
companyweb: The webpage cannot be found
companyweb: The webpage cannot be found
What else was on the drive that you dropped? Were the IIS virtual directories on there? Or are you 100% positive it only contained SQL stuff?
ASKER
It contains program files for backup software (which is working properly), Exchange server transport roles (which is also working properly), SQL databases and WSUS data/databases (which appears to be working properly).
ASKER
I'll reboot the server tonight to ensure that all of the ducks are starting in the order as they are intended.
ASKER
Unfortunately, that wasn't the fix it needed. Companyweb is still not operational.
It's tough to know exactly what piece of the puzzle isn't working. Unfortunately the mistake you made was pretty drastic.
Do you have a "wss" folder in C:\inetpub\ ?
Do you have a "wss" folder in C:\inetpub\ ?
By the way, if you need remote assistance, I'm available.
ASKER
Yes, there is a WSS folder within the wwwroot directory of inetpub. One thing different I do notice from my backups is that there is a new folder with the wws\VirtualDirectories called 33229. Originally, I only had 4721, dated from the original install. This new directory is empty. Is there a way to determine if the site has bound itself to this empty directory?
Look at the properties of the site(s) in IIS
Did you dismount and re-mount all your databases, from the new location?