Results 1 to 5 of 5

Thread: WSUS Event ID 421 Reason=Timeout expired

  1. #1
    Join Date
    Feb 2006
    Posts
    97

    WSUS Event ID 421 Reason=Timeout expired

    Is there anyone who can give me some information about the error message that I have written below. I was getting this in my Server Performance Report everyday on SBS 2003. There is only 1 occurrence and it doesnt seem to be a major issue and WSUS is working fine but I want you to take a look at same:

    Source: Windows Server Update Services
    Event ID 421
    Last Occurence: 3/15/2006 5:33 AM
    Total Occurrences: 1

    Connection to database failed. Reason=Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. General network error. Check your network documentation.. Connection string: Data Source=SERVER\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100

  2. #2
    Join Date
    Jan 2006
    Posts
    2,257

    Re: WSUS Event ID 421 Reason=Timeout expired

    Follow the below method to solve the Timeout Expired error:

    1) Save addDeploymentIndex.sql to disk on the Windows Server Update Services server
    2) As administrator, run the following command.
    osql -E -S <SQL instance name> -n -b -i addDeploymentIndex.sql

    More information here - http://msmvps.com/blogs/athif/archiv.../21/76101.aspx

  3. #3
    Join Date
    Dec 2007
    Posts
    2

    Error connecting to the Windows Server Update Services database

    Hi,

    I have a Windows Server 2003 SP2 with MSDE running WSUS 2.0 in replica mode.

    When I try and access the admin console I receive the error message "Error connecting to the Windows Server Update Services database"

    When I check the event log there a loads of Event 421 errors

    Event Type: Error
    Event Source: Windows Server Update Services
    Event Category: Update Services Service
    Event ID: 421
    Date: 12/12/2007
    Time: 14:32:30
    User: N/A
    Computer: SERVERNAME
    Description:
    Connection to database failed. Reason=SQL Server does not exist or access denied.. Connection string: Data Source=SERVERNAME\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.com/fwlink/events.asp.

    Any ideas?

  4. #4
    Join Date
    Jun 2006
    Posts
    623

    Re: WSUS Event ID 421 Reason=Timeout expired

    The issue that you are facing could be caued because the account you are logged in with is not a member of the Administrators or WSUS Administrators, group on the WSUS Server, therefore is being denied access or so.

  5. #5
    Join Date
    Dec 2007
    Posts
    2
    Thanks for your input but.....

    The user account used has full domain admin rights. I have even tried to launch the Wsus Admin Console whilst logged onto the server and receive the same error message....

    Connection to database failed. Reason=SQL Server does not exist or
    > access denied..

    and an associated error appears in the event log.
    All other Wsus2.0 servers are behaving as expected.

Similar Threads

  1. Replies: 4
    Last Post: 02-04-2011, 08:27 AM
  2. 'The semaphore timeout period has expired.' error with command File.Copy
    By Chandrakant81 in forum Software Development
    Replies: 2
    Last Post: 02-02-2009, 06:54 PM
  3. Error: 0x80070079 The semaphore timeout period has expired.
    By Delil in forum Windows Vista Performance
    Replies: 1
    Last Post: 11-02-2008, 06:42 PM
  4. The Semaphore Timeout Period Has Expired
    By William McIlroy in forum Windows Server Help
    Replies: 2
    Last Post: 19-08-2007, 07:34 AM
  5. Replies: 2
    Last Post: 30-03-2007, 11:46 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,524,207.29295 seconds with 18 queries