WSUS problems once again, Says SQL server not running but it is.

[Davit2005]

Was working fine now cannot connect to server console. I have both the SCCM and WSUS on same server.

 

I remember having issues like this before but once it was all installed it was fine. I haven't had chance to setup WSUS properly but was going to look today so I could point clients to the server as a start to try and stop them trying to connect to Windows update by themselves.

 

Marvelous Microsoft

[Michael]

What OS are you running WSUS on?

 

Are you using MS SQL or the Windows Internal Database?

 

The reason I ask is I had a real issue with WID (Windows Internal Database) on one of my servers. In the end, even after posting on Microsoft's forums, I ended up wiping the server and starting again. The root cause appeared to be some form of registry corruption.

 

Touchwood, all is running well to the current day

[Davit2005]

2008 Service Pack 1. Not sure about wiping the server as it is also the SCCM server. May look at putting WSUS on a seperate VM at this rate and point SCCM to that if possible. Guess I was taking risk in first place of having both on same server, but I thought things should of improved and wouldn't have same issues had before once up and running :-( .

 

Setup using SQL express 2005 for some reason, I might try and use SQL express 2008 for the WSUS having them both on same server shouldn't cause an issue?

[Michael]

You may as well use WID (it's what I use). It's essentially a compact version of SQL 2005 and cuts out a lot of fat not needed.