WSUS Support Forums: WSUS Connecting to database ERROR - WSUS Support Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • This topic is locked

WSUS Connecting to database ERROR

#1 User is offline   randy8080 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 11
  • Joined: 13-Mar-07

Post icon  Posted 28 Mar 2007, 06:23

Hello, I set up a WSUS server in our domain about a month ago. Everything was going great until the updates stopped getting pushed out. When I tried to connect to http://”servername”/WsusAdmin/ I get the following error message:

“Error connecting to the Windows Server Update Services database
There was an error connecting to the Windows Server Update Services database. Either the database is not available or you do not have the correct privileges to access the database.”

I went into the Event Viewer and I saw a whole bunch of error messages:

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Update Services Service
Event ID: 421
Date: 3/22/2007
Time: 10:07:16 AM
User: N/A
Computer: LVMSAPPS2
Description:
Connection to database failed. Reason=SQL Server does not exist or access denied.. Connection string: Data Source=LVMSAPPS2\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.


Event Type: Error
Event Source: Windows Server Update Services
Event Category: Update Services Service
Event ID: 421
Date: 3/22/2007
Time: 10:10:54 AM
User: N/A
Computer: LVMSAPPS2
Description:
Connection to database failed. Reason=Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.. Connection string: Data Source=LVMSAPPS2\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.


I went to Services, and MSSQL$WSUS said that it is “started” and set to “Automatic”. The SQLAgent$WSUS is set to “Automatic” but it does not say it is started.

I restarted the computer, and everything stays the same.

This server has more than one HDD. The C: drive has the MSSQL executable files, while our G: drive has the MSSQL$SUS folder and SUSDB.dat file. I had this server running for a month with no problem, I have no idea what changed.

Please help!


Thanks


Randy
0

#2 User is online   Rob Dunn 

  • Advanced Member
  • PipPipPip
  • Group: Advisory Members
  • Posts: 619
  • Joined: 06-Jun-05

Posted 28 Mar 2007, 06:30

View Postrandy8080, on Wed 28th Mar 2007, 08:23 am, said:

Hello, I set up a WSUS server in our domain about a month ago. Everything was going great until the updates stopped getting pushed out. When I tried to connect to http://”servername”/WsusAdmin/ I get the following error message:

“Error connecting to the Windows Server Update Services database
There was an error connecting to the Windows Server Update Services database. Either the database is not available or you do not have the correct privileges to access the database.”


Can you access the SQL server through other means (i.e. SQL Server Management Tool)? Are you running the WSUS server as a front-end/back-end configuration? If so, verify that your WSUS server name is in the 'WSUS Administrators' group on the SQL server.
WSUS Beginner's Admin FAQ

Computers not showing up in WSUS? See this post: http://www.wsus.info...?showtopic=9312
-------------------------------------
WSUS Extract - extract update EXE's from the WSUS content folder: WSUS Extract 1.30

UpdateHF - force client to download and install approved Windows Updates: Force Windows Update download and install 2.5 (03/26/07)

SetAuthorization - Perform a /resetauthorization and /detectnow against a remote computer where you have administrative privileges

Various Admin scripts, WSUS stuff, and HTA-driven IS tools: http://www.vbshf.com/vbshf/forum

My electronic music side-project: http://www.funender....c/maximillian_x
0

#3 User is offline   randy8080 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 11
  • Joined: 13-Mar-07

Posted 28 Mar 2007, 06:51

Thanks for the quick reply!

I checked the WSUS Admin Group, and I have the domain admin, and NT Authority Account in there. It seems like MSSQL is looking for the database in the wrong location. It was fine before, so I have no idea what changed, and I have no idea how and where to point it to :(




View PostRob Dunn, on Wed 28th Mar 2007, 09:30 am, said:

View Postrandy8080, on Wed 28th Mar 2007, 08:23 am, said:

Hello, I set up a WSUS server in our domain about a month ago. Everything was going great until the updates stopped getting pushed out. When I tried to connect to http://”servername”/WsusAdmin/ I get the following error message:

“Error connecting to the Windows Server Update Services database
There was an error connecting to the Windows Server Update Services database. Either the database is not available or you do not have the correct privileges to access the database.”


Can you access the SQL server through other means (i.e. SQL Server Management Tool)? Are you running the WSUS server as a front-end/back-end configuration? If so, verify that your WSUS server name is in the 'WSUS Administrators' group on the SQL server.

0

#4 User is online   Rob Dunn 

  • Advanced Member
  • PipPipPip
  • Group: Advisory Members
  • Posts: 619
  • Joined: 06-Jun-05

Posted 28 Mar 2007, 07:01

View Postrandy8080, on Wed 28th Mar 2007, 08:51 am, said:

Thanks for the quick reply!

I checked the WSUS Admin Group, and I have the domain admin, and NT Authority Account in there. It seems like MSSQL is looking for the database in the wrong location. It was fine before, so I have no idea what changed, and I have no idea how and where to point it to :(


So 'LVMSAPPS2\WSUS' is not the correct name of the server instance?

Is your WSUS server separate from your SQL database server (i.e. does the db reside somewhere else other than your WSUS server)? If yes, then you will need to make sure to add the name of the WSUS server to your 'WSUS Administrators' group on the SQL server.

Also, check and make sure that your SQL instance is started, wherever the db may reside. Have you restarted the server since the issue came up (either SQL or WSUS)?

Rob
WSUS Beginner's Admin FAQ

Computers not showing up in WSUS? See this post: http://www.wsus.info...?showtopic=9312
-------------------------------------
WSUS Extract - extract update EXE's from the WSUS content folder: WSUS Extract 1.30

UpdateHF - force client to download and install approved Windows Updates: Force Windows Update download and install 2.5 (03/26/07)

SetAuthorization - Perform a /resetauthorization and /detectnow against a remote computer where you have administrative privileges

Various Admin scripts, WSUS stuff, and HTA-driven IS tools: http://www.vbshf.com/vbshf/forum

My electronic music side-project: http://www.funender....c/maximillian_x
0

#5 User is offline   randy8080 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 11
  • Joined: 13-Mar-07

Posted 28 Mar 2007, 07:06

Yes, I have restarted the server. WSUS is installed on a single server. The MSSQL Folder is on the C: drive, and the WSUS "MSSQL$WSUS" folder is on our G: drive


View PostRob Dunn, on Wed 28th Mar 2007, 10:01 am, said:

View Postrandy8080, on Wed 28th Mar 2007, 08:51 am, said:

Thanks for the quick reply!

I checked the WSUS Admin Group, and I have the domain admin, and NT Authority Account in there. It seems like MSSQL is looking for the database in the wrong location. It was fine before, so I have no idea what changed, and I have no idea how and where to point it to :(


So 'LVMSAPPS2\WSUS' is not the correct name of the server instance?

Is your WSUS server separate from your SQL database server (i.e. does the db reside somewhere else other than your WSUS server)? If yes, then you will need to make sure to add the name of the WSUS server to your 'WSUS Administrators' group on the SQL server.

Also, check and make sure that your SQL instance is started, wherever the db may reside. Have you restarted the server since the issue came up (either SQL or WSUS)?

Rob

0

#6 User is online   Rob Dunn 

  • Advanced Member
  • PipPipPip
  • Group: Advisory Members
  • Posts: 619
  • Joined: 06-Jun-05

Posted 28 Mar 2007, 07:15

View Postrandy8080, on Wed 28th Mar 2007, 09:06 am, said:

Yes, I have restarted the server. WSUS is installed on a single server. The MSSQL Folder is on the C: drive, and the WSUS "MSSQL$WSUS" folder is on our G: drive


Is the MSDE service running (probably will look like 'MSSQL$WSUS')? Check the event log to see if it failed during startup, which reminds me - are there other event log entries that might show some other issue going on at the same time? I remember I had a similar problem when our SQL server ran out of drive space (thanks to misdirected backups and unknowing developers!).

Rob
WSUS Beginner's Admin FAQ

Computers not showing up in WSUS? See this post: http://www.wsus.info...?showtopic=9312
-------------------------------------
WSUS Extract - extract update EXE's from the WSUS content folder: WSUS Extract 1.30

UpdateHF - force client to download and install approved Windows Updates: Force Windows Update download and install 2.5 (03/26/07)

SetAuthorization - Perform a /resetauthorization and /detectnow against a remote computer where you have administrative privileges

Various Admin scripts, WSUS stuff, and HTA-driven IS tools: http://www.vbshf.com/vbshf/forum

My electronic music side-project: http://www.funender....c/maximillian_x
0

#7 User is offline   randy8080 

  • Member
  • PipPip
  • Group: Regular Members
  • Posts: 11
  • Joined: 13-Mar-07

Posted 28 Mar 2007, 08:16

Thanks for all the help. I ended up running the WSUS setup again, and did a reinstall. Everything works again. I am stumped as to what caused the problem in the first place. Hopefully it will not happen again.
0

Page 1 of 1
  • You cannot start a new topic
  • This topic is locked

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users