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

nettech 171 Reputation points
2023-09-29T20:18:33.44+00:00

Hi,

We currently have WSUS server on a 2012 R2 member server in our 2012 R2 domain.

We recently added a brand new 2022 member server and installed WSUS role on it. When we try to go through the configuration wizard of WSUS on 2022 it fails. Pointing us to a log file.

What options do we have in this situation?

2023-09-29 15:21:08  Postinstall started
2023-09-29 15:21:08  Detected role services: Api, UI, WidDatabase, Services
2023-09-29 15:21:08  Start: LoadSettingsFromXml
2023-09-29 15:21:08  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2023-09-29 15:21:08  Value is false
2023-09-29 15:21:08  End: GetConfigValue
2023-09-29 15:21:08  Hosting content on MU
2023-09-29 15:21:08  Database roleservice is not installed
2023-09-29 15:21:08  End: LoadSettingsFromXml
Post install is starting
2023-09-29 15:21:08  Start: Run
2023-09-29 15:21:08  Fetching WsusAdministratorsSid from registry store
2023-09-29 15:21:08  Value is S-1-5-21-2792808456-1047292482-3750426523-1000
2023-09-29 15:21:08  Fetching WsusReportersSid from registry store
2023-09-29 15:21:08  Value is S-1-5-21-2792808456-1047292482-3750426523-1001
2023-09-29 15:21:09  Configuring content directory...
2023-09-29 15:21:09  Configuring groups...
2023-09-29 15:21:09  Starting group configuration for WSUS Administrators...
2023-09-29 15:21:09  Found group in regsitry, attempting to use it...
2023-09-29 15:21:09  Writing group to registry...
2023-09-29 15:21:09  Finished group creation
2023-09-29 15:21:09  Starting group configuration for WSUS Reporters...
2023-09-29 15:21:09  Found group in regsitry, attempting to use it...
2023-09-29 15:21:09  Writing group to registry...
2023-09-29 15:21:09  Finished group creation
2023-09-29 15:21:09  Configuring permissions...
2023-09-29 15:21:09  Fetching content directory...
2023-09-29 15:21:09  Fetching ContentDir from registry store
2023-09-29 15:21:09  Value is C:\Program Files\Update Services
2023-09-29 15:21:09  Fetching group SIDs...
2023-09-29 15:21:09  Fetching WsusAdministratorsSid from registry store
2023-09-29 15:21:09  Value is S-1-5-21-2792808456-1047292482-3750426523-1000
2023-09-29 15:21:09  Fetching WsusReportersSid from registry store
2023-09-29 15:21:09  Value is S-1-5-21-2792808456-1047292482-3750426523-1001
2023-09-29 15:21:09  Creating group principals...
2023-09-29 15:21:09  Granting directory permissions...
2023-09-29 15:21:09  Granting permissions on content directory...
2023-09-29 15:21:09  Granting registry permissions...
2023-09-29 15:21:09  Granting registry permissions...
2023-09-29 15:21:09  Granting registry permissions...
2023-09-29 15:21:09  Configuring shares...
2023-09-29 15:21:09  Configuring network shares...
2023-09-29 15:21:09  Fetching content directory...
2023-09-29 15:21:09  Fetching ContentDir from registry store
2023-09-29 15:21:09  Value is C:\Program Files\Update Services
2023-09-29 15:21:09  Fetching WSUS admin SID...
2023-09-29 15:21:09  Fetching WsusAdministratorsSid from registry store
2023-09-29 15:21:09  Value is S-1-5-21-2792808456-1047292482-3750426523-1000
2023-09-29 15:21:09  Content directory is local, creating content shares...
2023-09-29 15:21:09  Creating share "UpdateServicesPackages" with path "C:\Program Files\Update Services\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2023-09-29 15:21:09  Deleting existing share...
2023-09-29 15:21:09  Creating share...
2023-09-29 15:21:09  Share successfully created
2023-09-29 15:21:09  Creating share "WsusContent" with path "C:\Program Files\Update Services\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2023-09-29 15:21:09  Deleting existing share...
2023-09-29 15:21:09  Creating share...
2023-09-29 15:21:09  Share successfully created
2023-09-29 15:21:09  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2023-09-29 15:21:09  Deleting existing share...
2023-09-29 15:21:09  Creating share...
2023-09-29 15:21:09  Share successfully created
2023-09-29 15:21:09  Finished creating content shares
2023-09-29 15:21:09  Stopping service WSUSService
2023-09-29 15:21:09  Stopping service W3SVC
2023-09-29 15:21:09  Configuring WID database...
2023-09-29 15:21:09  Configuring the database...
2023-09-29 15:21:09  Establishing DB connection...
2023-09-29 15:21:09  Checking to see if database exists...
2023-09-29 15:21:09  Database exists
2023-09-29 15:21:09  Switching database to single user mode...
2023-09-29 15:21:09  Loading install type query...
2023-09-29 15:21:09  DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (20348)
DECLARE @scriptMinorVersion     int = (11)
DECLARE @databaseMajorVersion   int 
DECLARE @databaseMinorVersion   int 
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return 
    END 
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END

2023-09-29 15:21:09  Install type is: UnsupportedFuture
2023-09-29 15:21:09  DB is a higher version than the config scripts
2023-09-29 15:21:09  Swtching DB to multi-user mode......
2023-09-29 15:21:09  Finished setting multi-user mode
2023-09-29 15:21:09  Ensuring SUSDB is set to Multi-User Mode ...
2023-09-29 15:21:09  Disposing Connection
2023-09-29 15:21:09  Clearing Connection Pools
2023-09-29 15:21:09  Microsoft.UpdateServices.Administration.CommandException: 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.
   at Microsoft.UpdateServices.Administration.ConfigureDB.CheckForUnsupportedVersion(DBInstallType installType, Boolean dbExists)
   at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal)
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
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.



Windows for business Windows Server User experience Other
{count} votes

1 answer

Sort by: Most helpful
  1. Adam J. Marshall 10,281 Reputation points MVP
    2023-10-04T17:49:30.96+00:00
    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.