WSUS sync failure with TypeInitializationException error

jamar clow 60 Reputation points
2024-03-06T12:39:48.44+00:00

What could be causing my WSUS to stop syncing with the error message "Sync failed: Unknown: TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible"?

I already tried reinstalling WSUS, but it did not fix the issue.

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,005 questions
Microsoft Configuration Manager
0 comments
Accepted answer
  1. glebgreenspan 1,445 Reputation points
    2024-03-06T13:50:45.3066667+00:00

    Hello Jamar

    The error message you are seeing indicates that WSUS is having trouble connecting to the SQL Server database. This can be caused by a variety of reasons, and here are some steps you can take to troubleshoot the issue:

    1.     Check SQL Server Configuration:

    o    Verify that the SQL Server instance is running and accessible.

    o    Check the SQL Server connection settings in WSUS to ensure they are accurate.

    o    Ensure that the SQL Server is configured to allow remote connections.

    2.     Check Network Connectivity:

    o    Verify that there are no network issues between the WSUS server and the SQL Server.

    o    Check firewall settings to make sure they are not blocking the connection.

    o    Ensure that the WSUS server can communicate with the SQL Server over the necessary port (typically 1433).

    3.     Verify SQL Server Permissions:

    o    Ensure that the account used by WSUS to connect to SQL Server has the necessary permissions.

    o    Check that the SQL Server login for the WSUS account is not disabled or expired.

    4.     Database Maintenance:

    o    Perform maintenance tasks on the SQL Server database, such as checking for corruption or running the DBCC CHECKDB command.

    o    Check SQL Server error logs for any relevant information that may help diagnose the problem.

    5.     WSUS Configuration:

    o    Double-check the WSUS configuration settings to confirm that the SQL Server information is correct.

    o    Verify that the WSUS database is functioning correctly and is not corrupted.

    6.     Restart Services:

    o    Try restarting the WSUS and SQL Server services to see if that resolves the issue.

    7.     Check Disk Space:

    o    Ensure that there is enough disk space available on both the WSUS server and the SQL Server.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest