locked
DB is a higher version than the config scripts RRS feed

  • Question

  • Environment - Windows 2016 with wsus role

    SQL 2016 on windows 2016 independent

    after installation when I open wsus I get below error

    2017-08-17 20:13:26  Postinstall started
    2017-08-17 20:13:26  Detected role services: Api, Database, UI, Services
    2017-08-17 20:13:26  Start: LoadSettingsFromParameters
    2017-08-17 20:13:26  Content local is: True
    2017-08-17 20:13:26  Content directory is: D:\WSUS
    2017-08-17 20:13:26  SQL instname is: SQLlab01
    2017-08-17 20:13:26  End: LoadSettingsFromParameters
    2017-08-17 20:13:26  Start: Run
    2017-08-17 20:13:26  Fetching WsusAdministratorsSid from registry store
    2017-08-17 20:13:26  Value is S-1-5-21-547171103-2153463536-3194532430-1000
    2017-08-17 20:13:26  Fetching WsusReportersSid from registry store
    2017-08-17 20:13:26  Value is S-1-5-21-547171103-2153463536-3194532430-1001
    2017-08-17 20:14:28  Configuring content directory...
    2017-08-17 20:14:28  Configuring groups...
    2017-08-17 20:14:28  Starting group configuration for WSUS Administrators...
    2017-08-17 20:14:28  Found group in regsitry, attempting to use it...
    2017-08-17 20:14:30  Writing group to registry...
    2017-08-17 20:14:30  Finished group creation
    2017-08-17 20:14:30  Starting group configuration for WSUS Reporters...
    2017-08-17 20:14:30  Found group in regsitry, attempting to use it...
    2017-08-17 20:14:30  Writing group to registry...
    2017-08-17 20:14:30  Finished group creation
    2017-08-17 20:14:30  Configuring permissions...
    2017-08-17 20:14:30  Fetching content directory...
    2017-08-17 20:14:30  Fetching ContentDir from registry store
    2017-08-17 20:14:30  Value is D:\WSUS
    2017-08-17 20:14:30  Fetching group SIDs...
    2017-08-17 20:14:30  Fetching WsusAdministratorsSid from registry store
    2017-08-17 20:14:30  Value is S-1-5-21-547171103-2153463536-3194532430-1000
    2017-08-17 20:14:30  Fetching WsusReportersSid from registry store
    2017-08-17 20:14:30  Value is S-1-5-21-547171103-2153463536-3194532430-1001
    2017-08-17 20:14:30  Creating group principals...
    2017-08-17 20:14:30  Granting directory permissions...
    2017-08-17 20:14:30  Granting permissions on content directory...
    2017-08-17 20:14:30  Granting registry permissions...
    2017-08-17 20:14:30  Granting registry permissions...
    2017-08-17 20:14:30  Granting registry permissions...
    2017-08-17 20:14:30  Configuring shares...
    2017-08-17 20:14:30  Configuring network shares...
    2017-08-17 20:14:30  Fetching content directory...
    2017-08-17 20:14:30  Fetching ContentDir from registry store
    2017-08-17 20:14:30  Value is D:\WSUS
    2017-08-17 20:14:30  Fetching WSUS admin SID...
    2017-08-17 20:14:30  Fetching WsusAdministratorsSid from registry store
    2017-08-17 20:14:30  Value is S-1-5-21-547171103-2153463536-3194532430-1000
    2017-08-17 20:14:30  Content directory is local, creating content shares...
    2017-08-17 20:14:30  Creating share "UpdateServicesPackages" with path "D:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
    2017-08-17 20:14:30  Deleting existing share...
    2017-08-17 20:14:30  Creating share...
    2017-08-17 20:14:30  Share successfully created
    2017-08-17 20:14:30  Creating share "WsusContent" with path "D:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2017-08-17 20:14:30  Deleting existing share...
    2017-08-17 20:14:30  Creating share...
    2017-08-17 20:14:30  Share successfully created
    2017-08-17 20:14:30  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."
    2017-08-17 20:14:30  Deleting existing share...
    2017-08-17 20:14:30  Creating share...
    2017-08-17 20:14:30  Share successfully created
    2017-08-17 20:14:30  Finished creating content shares
    2017-08-17 20:14:30  Stopping service WSUSService
    2017-08-17 20:14:30  Stopping service W3SVC
    2017-08-17 20:14:30  Configuring database...
    2017-08-17 20:14:31  Configuring the database...
    2017-08-17 20:14:31  Establishing DB connection...
    2017-08-17 20:14:31  Checking to see if database exists...
    2017-08-17 20:14:31  Database exists
    2017-08-17 20:14:31  Switching database to single user mode...
    2017-08-17 20:14:31  Loading install type query...
    2017-08-17 20:14:31  DECLARE @currentDBVersion       int
    DECLARE @scriptMajorVersion     int = (14393)
    DECLARE @scriptMinorVersion     int = (0)
    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

    2017-08-17 20:14:31  Install type is: UnsupportedFuture
    2017-08-17 20:14:31  DB is a higher version than the config scripts
    2017-08-17 20:14:31  Swtching DB to multi-user mode......
    2017-08-17 20:14:31  Finished setting multi-user mode
    2017-08-17 20:14:31  Disposing Connection
    2017-08-17 20:14:31  Clearing Connection Pools
    2017-08-17 20:14:31  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)

    Thursday, August 17, 2017 10:36 AM

All replies

  • Hello,

    When you install WSUS role, did you select SQL Server connectivity service?

    You may try disable the firewall and run the post installation. 

    In addition, you may use WID as database and check the result. 

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 18, 2017 2:13 AM
  • When I install the role I selected wsus & SQL server connectivity. WID was not selected.

    I have not tried with WID yet.

    Friday, August 18, 2017 9:46 AM
  • I uninstalled the role and re-installed with WID & WSUS services. It works with local database but not with remote SQL server.
    Friday, August 18, 2017 11:02 AM
  • Hello,

    We recommend that you use SQL Server with WSUS in the following cases:

    1. You require an NLB WSUS solution.

    2. You already have at least one instance of SQL Server installed.

    3. You cannot run the SQL Server service under a local non-system account or by using SQL Server authentication. WSUS supports Windows authentication only.

    To use a remote SQL server as database, you may follow the link below:

    https://microspecialist.wordpress.com/2013/10/28/installing-wsus-on-server-2012-step-by-step/


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 23, 2017 9:03 AM