Solution given by Alejandro worked like a charm ! Unbelivable that MS rolls out a CRITICAL SYSTEM with that kind of error... :(
And I`ve installed SRV2022 from THIS MONTH ISO image !!!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
It would be highly appreciated if anybody could help me.
Thanks in advance***
Solution given by Alejandro worked like a charm ! Unbelivable that MS rolls out a CRITICAL SYSTEM with that kind of error... :(
And I`ve installed SRV2022 from THIS MONTH ISO image !!!
Thanks to @Pedro Herrera for solving this!
I just did a clean install of Server 2022 May Update and the only thing I did with this server was install WSUS using WID.
en-us_windows_server_2022_updated_may_2022_x64_dvd_50c4a90e.iso
I'm here because of this error. I wish people would stop making false claims such as "If you are trying to install WSUS on a server using the Windows Internal Database (WID), you will likely NOT receive this error." It's useless information and not helpful in any way. This is very clearly and obviously happening while using WID.
Thanks again @Pedro Herrera !
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.
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.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more