Windows Server 2022 WSUS Fatal Error: The schema version of the database is from a newer version of WSUS

M. Hasan Alizade 11

Hi,
I recently upgraded Windows Server from 2016 to 2022!
In post-install processes, I receive the following error for the WSUS service:

Log file is located at C:\Users\m-alizadeh\AppData\Local\Temp\\WSUS_PostInstall_20220223T152505.log
Post install is starting
Fatal Error: The schema version of the database is from a newer version of WSUS 
than currently installed.  You must either patch your WSUS server to at least 
that version or drop the database.

Furthermore, in the WSUS console there is the following error:

The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 192.168.0.1:8530

Source
System

Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
** this exception was nested inside of the following exception **


System.Net.WebException -- Unable to connect to the remote server

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

***I did the following actions, which were unsuccessful:

I removed the WSUS service, deleted the updates storage folder!
I renamed SUSDB.MDF in the "WID\Data" folder
I restarted the IIS Service as well as the application pool of WSUS
I re-installed the WSUS service but it did not work!

It would be highly appreciated if anybody could help me.
Thanks in advance***

J.C.D Lippold 5 Reputation points

2024-03-01T11:35:47.4033333+00:00

I would like to add that if the solution that @Pedro Herrera mentioned does not work you should delete the SUSDB database from SQL and then restart the post install config. It will recreate the database en post install will run succesfully.

9 answers

Pedro Herrera 236 Reputation points

2022-05-21T19:29:09.81+00:00

1) Go to C:\Program Files\Update Services\Database

2) Take ownership of VersionCheck.sql from "TrustInstall"

3) Open file in notepad

4) On line 3 change "DECLARE @scriptMinorVersion int = (11)" to "DECLARE @scriptMinorVersion int = (51)"
the "11" is a typo

5) Restore ownership, if cant the make "Everyone" owner

6) Re-run post install config

7) Have a beer.
Please sign in to rate this answer.

47 people found this answer helpful.
Adam J. Marshall 9,506 Reputation points MVP

2022-05-26T19:20:37.373+00:00

I can confirm that on a brand new install of 2022 Datacenter, with May 2022 Media from Microsoft's Business Center,

C:\Program Files\Update Services\Database\VersionCheck.sql
has the following:

DECLARE @scriptMajorVersion int = (20348)
DECLARE @scriptMinorVersion int = (11)

and installs successfully, performs the post-install configuration tasks successfully (from server manager's launch post-install tasks link), and performs the initial sync successfully.

I'm not sure where you're getting your information from.

Corinne Peterman 1 Reputation point

2022-05-27T18:50:56.257+00:00

I can also confirm this worked for me for a Windows 2022 install that had the post install fail.

Updating that line from Pedro Herrera's solution allowed my post installation steps to succeed.. Thank you so very much for posting it.

--Cori

Adam J. Marshall 9,506 Reputation points MVP

2022-05-27T19:26:53.717+00:00

@Corinne Peterman Can you let me know what version of Server 2022 you have (Standard/Datacenter), and what was the scenario you had that this method fixed? Did you have it installed prior and this is a re-installation? Was this brand new, from media, with only the WSUS role added where it failed? What language of OS were you using? EN-US?

I'm trying to figure out why the change would be required, in what scenario. Like I said above, I literally installed Server 2022 Datacenter as a VM, added WSUS, and it worked out of the box (not attached to a domain).

Corinne Peterman 1 Reputation point

2022-05-27T20:13:34.35+00:00

Hi Adam--

The Windows 2022 was a brand new installation for a new WSUS/SCCM install. The add/remove roles from GUI was used to install WSUS, not powershell as I was feeling lazy that day. Installed ok but failed on post installation steps repeatedly.

The server:
Edition Windows Server 2022 Standard
Version 21H2
Installed on ‎2/‎22/‎2022
OS build 20348.740

Language English

The SQL version:
Microsoft SQL Server 2019 (RTM-CU15) (KB5008996) - 15.0.4198.2 (X64)

The error we received in the post installation log:

DB is a higher version than the config scripts

The schema version of the database is from a newer version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database.

Once I edited the file as listed to change the Minor version to 51, I clicked to run the post-installation steps again and it completed successfully and created the site in IIS finally.

Eduardo Wagner Neto 1 Reputation point

2022-05-29T23:03:58.437+00:00

@Pedro Herrera

It worked like a charm!!!Thxxx

Adam J. Marshall 9,506 Reputation points MVP

2022-06-01T16:13:16.027+00:00

Thank you - I have now been able to replicate. I'll be making a blog post on this.

Adam J. Marshall 9,506 Reputation points MVP

2022-06-02T12:23:32.837+00:00

I don't know why, but I can't replicate it 100% of the time. I'll post about it anyways as it did fix it that time.

Rachid Benatich 1 Reputation point

2022-09-15T09:00:30.65+00:00

Thank you so much!!

Mike DeShane 0 Reputation points

2023-02-03T00:31:10.7+00:00

We are facing this issue and we take ownership of the file but after modifying the file we are unable to save it as it says we don't have the adequate permissions.

CH 0 Reputation points

2023-02-09T19:01:05.04+00:00

Pedro, you saved my bacon. Cheers.

David Broadfoot 0 Reputation points

2023-03-19T14:56:16.6233333+00:00

Thank You

Loic VEIRMAN - MSSEC 0 Reputation points

2023-04-15T16:28:22.49+00:00

April 2023 : this bug is still there... Howdy, MS, don't you fell you should at least test things ??? You make things very awfull to use...

Kolkka, Tommi 0 Reputation points

2023-05-16T17:13:20.9533333+00:00

The beer tasted so good

Marvin Julson 0 Reputation points

2023-08-16T21:47:37.4866667+00:00

Thanks Pedro. Worked great. I'll pass on the beer though. ;)

Hans, DE01 0 Reputation points

2023-08-18T12:10:11.8+00:00

Works like a charm, Thank you!

Peter GRIFFITHS (The Maelor School) 0 Reputation points

2023-10-31T08:39:58.1966667+00:00

@Pedro Herrera this worked for me thanks! though I deviated at step 7 and had coffee instead.

Valdimilson Rocha 0 Reputation points

2024-04-19T18:27:54.07+00:00

I recently had this problem in SCCM version 2303.

It was fixed with your tutorial.

Thanks for the help.

Kovacs, Paul 0 Reputation points

2024-04-30T16:48:17.4133333+00:00

Worked like a Charm!!

Muthuswamy Raju 0 Reputation points

2024-06-04T02:56:20.9633333+00:00

Thank you, it worked for me. I am setting up WSUS server for the first time.

pooya hashemi 0 Reputation points

2024-07-24T11:21:37.6833333+00:00

that worked for me thanks a lot
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 9,506 Reputation points MVP

2022-06-02T13:29:37.523+00:00

I've written a blog on how to fix this.

https://www.ajtek.ca/wsus/wsus-post-deployment-configuration-failed-windows-server-2022/

Hope this helps the next person who has this problem.
Please sign in to rate this answer.

9 people found this answer helpful.
Loic VEIRMAN - MSSEC 0 Reputation points

2023-04-15T16:30:43.4+00:00

Hi Adam, you should update your blog post = the bug also occurs with a WID DD (2k22, Standard, EN/US). The script also don't work if ran with e "domain administrator" account (not a script issue, just a warning).

Adam J. Marshall 9,506 Reputation points MVP

2023-05-03T15:49:52.3566667+00:00

What do you mean "WID DD" - what's the DD? - and also what error/issue do you get with running it as a domain admin? My testing of the script was run with the appropriate account that had permissions, and that user was a domain admin.

Loic VEIRMAN - MSSEC 0 Reputation points

2023-05-03T16:06:57.9833333+00:00

Sorry, not DD but DB (database). The script is fine, the purpose here was just to mantion that the issues occurs either with a WID db or a SQL one. The fix is exactly the same.

Adam J. Marshall 9,506 Reputation points MVP

2023-05-03T16:19:05.1333333+00:00

Article updated. I took out some information in that article and I'll make it into another as it doesn't necessarily relate to that error anymore but more so general information.

Enzo La Bruzzo 0 Reputation points

2023-05-20T20:00:08.77+00:00

Hello Adam,

The script doesn't work for me, should I change something in the script to be able to adapt it to my server? Thank you

Adam J. Marshall 9,506 Reputation points MVP

2023-05-20T20:50:12.5766667+00:00

Thanks for the heads up. The last modification I made to the page caused an issue with the script. I've fixed it. It should be 3 lines - the first 2 starting with Start-Process and the last one starting with (Get-Content

Please try it again and see if that fixes it.

Luc FULLENWARTH 1 Reputation point

2023-10-10T09:39:43.7433333+00:00

There was an issue with the file permission, which I changed another way.
But except that, the solution fixed my WSUS issue. Thank you Adam! :)

Sivaji Ganesh 1 Reputation point

2023-10-31T11:41:57.4133333+00:00

You saved my day. Thank you.

Pine 0 Reputation points

2024-10-25T18:11:13.7566667+00:00

Yes. this worked for me.

Vitalii Litovchenko 0 Reputation points

2024-10-29T16:53:46.3433333+00:00

Thanks a lot for the solution. It worked for me like charm.

JEmlay 26 Reputation points

2024-10-29T17:02:33.9233333+00:00

Pine and Vitalii - make sure you thank Pedro Herrera, the person that actually found a fix for this problem.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Amandayou-MSFT 11,141 Reputation points

2022-03-02T03:14:46.327+00:00

Hi,

Thanks for your posting in Q&A.

Agree with AJTek-Adam-J-Marshall, the issue may be WSUS is not removed completely.

We need to:

Remove WSUS Role and Windows Internal Database (WID) Feature.

Remove C:\WSUS or where ever the WSUSContent folder resides.

Remove C:\Windows\WID (specifically: delete the SUSDB.mdf and SUSDB_log.ldf in C:\Windows\WID\Data). If you don't remove the WID role and its files on a reinstall, it will re-attach to the same database.

In IIS, remove the 'WSUS Administration' website and the 'WsusPool' Application Pool if they still exist.

Restart the server and re-add the WSUS And WID Roles. Let it install, and then restart the server again.

Now try to do the post-installation configuration.

If this doesn't work, disjoin the server from the domain, and restart. Try the post-installation steps again. If it works, the issue is a policy on your domain that is causing the issues. You can then rejoin the server to the domain.

After you've removed WSUS completely following the instructions above, you can then go ahead and install it again if you so choose.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

3 people found this answer helpful.
M. Hasan Alizade 11 Reputation points

2022-03-02T11:34:21.453+00:00

Thanks for your reply.

I did all the steps but the fatal error still exists!!
Post install is starting
Fatal Error: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database.

Furthermore, the WSUS server is also our Domain Controller. Is it possible to disjoin the Server from the Domain?

Amandayou-MSFT 11,141 Reputation points

2022-03-22T09:19:00.62+00:00

Hi,

Thanks for your reply.

the WSUS server is also our Domain Controller.

Yes, It is not recommended that we install WSUS on DC by Microsoft. To aviod the further problem, we could find the new Windows server 2022, and install the WSUS and let the client point to the new WSUS directly.

Best regards,
Amanda
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 9,506 Reputation points MVP

2022-03-01T14:30:57.683+00:00

Follow my guide to remove WSUS fully and reinstall. It sounds like you didn't fully remove it.

https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/
Please sign in to rate this answer.

2 people found this answer helpful.
Getrude Nyanduko 11 Reputation points

2022-07-27T12:28:23.423+00:00

Great. Thanks @Adam J. Marshall
Your solution was very clear and worked perfectly.
Was experiencing this after OS upgrade to Windows server 2022

Danno Allgrove 0 Reputation points

2024-01-25T17:58:11.7233333+00:00

It works for me, as well. Thanks bunches and bunches!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam J. Marshall 9,506 Reputation points MVP

2022-03-02T13:53:16.48+00:00

This is why Microsoft does not recommend installing WSUS on a Domain Controller. What you've done is against recommendations and what has happened is the groups WSUS needs to operate are no longer 'local' because a DC does not have any 'local' groups.

You cannot disjoin a domain controller from a domain unless you are demoting it to a member server first and then disjoining it.

You are better to try to fix this problem than to disjoin it.

Create 2 Domain Local groups

Name: WSUS Administrators
Description: Members of this group can administer the Windows Server Update Services role.
Name: WSUS Reporters
Description: Members of this group can generate reports but cannot approve updates or configure the Windows Server Update Services role.

Then try to run the postinstall again.
Please sign in to rate this answer.

1 person found this answer helpful.
M. Hasan Alizade 11 Reputation points

2022-03-09T07:52:47.77+00:00

Thanks for your explanation.

The 2 Domain Local groups existed without any members! I added domain admins, administrator, and my account to the groups.

I noticed in IIS, the 'WSUS Administration' website and the 'WsusPool' Application Pool are not created of their removal!

I am totally confused!!!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.