WSUS Post Installation Error

[gmonks]

Hi,

 

Installed WSUS on Server 2012 R2 RTM today and get the following error when trying to load the post installation tasks:

 

The database is in single-user mode, and a user is currently connected to it.ALTER DATABASE statement failed.

Seems to be an SQL problem. Backup Exec uses a database but it did on the old server I'm moving it from...

 

Cannot seem to find a solution on the net. Anybody come across this?

 

Thanks

George.

[free780]

Its not that you need to give logon as a service rights to wsus. There is a ms article.

http://support.microsoft.com/kb/2832204

[gmonks]

Its not that you need to give logon as a service rights to wsus. There is a ms article.

"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012

 

That hasn't solved it.

 

This is the error I get.

 

[LawrenceGarvin]

It's difficult to imagine what would have caused the database to get stuck in SINGLE_USER mode on a WS2012/WSUS v6.x installation, but there is only ONE way to resolve this issue.

 

1. STOP the Update Services service. (The reason you cannot get your console connection to work is because the SERVICE has already consumed that one authorized "user".)

2. Open SQL Server Management Studio. (When using WID, you may need to download and install SQL Server 2012 Management Studio Express Edition.)

3. Execute this command: ALTER DATABASE SUSDB SET MULTI_USER;

4. Restart the Update Services service.

[gmonks]

It's difficult to imagine what would have caused the database to get stuck in SINGLE_USER mode on a WS2012/WSUS v6.x installation, but there is only ONE way to resolve this issue.

 

1. STOP the Update Services service. (The reason you cannot get your console connection to work is because the SERVICE has already consumed that one authorized "user".)

2. Open SQL Server Management Studio. (When using WID, you may need to download and install SQL Server 2012 Management Studio Express Edition.)

3. Execute this command: ALTER DATABASE SUSDB SET MULTI_USER;

4. Restart the Update Services service.

 

Lawrence,

 

That's what makes this situation weird. The Update Service service isn't showing....

 

 

George.

[LawrenceGarvin]

Well, that makes it simple. If there's no Update Services service, then it's not a WSUS Server, and without the service, that'll make it near impossible to connect to the database. Either the installation is corrupted, or the role was partially uninstalled. Inasmuch as it seems the WID was in SINGLE_USER mode when WSUS was being installed (we know that's where it was when the post-install wizard was launched), this thing could be all sorts of sideways. Your best option may be to start from scratch.

[Michael]

I have to agree, it looks like a corrupted installation to me. WSUS behaves in a similar way in 2008 R2 when things go wrong.

[gmonks]

Hi,

I have checked multi user mode and a host of other suggestions on another forum. Hate to say it but I give up. I've going to set up a virtual machine and just have it dedicated to WSUS. There is obviously something conflicting with my current setup. I had it running fine on a test machine.

Thanks for your help.

George.