WSUS installation with SQL 2019 fails at Post-deployment Configuration

[DJ-1701]

Ok, bit of an odd one... Windows Server 2019, SQL 2019 and WSUS...

 

I can add the Role of Windows Server Update Services with the WSUS Services and SQL Server Connectivity options, but once that completes and I have to do the Post-deployment Configuration stage, it tries for a little while, then falls overs, I have tried with Server Manager, I have tried in Command Prompt to execute this, it always fails and appears to have the same message either on screen or in the log file...

 

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.

 

My Google Fu can't find anything online that will help, have tried dropping the db and restarting, no joy at all. This works perfectly fine with WID instead of SQL, but we want to use this with SQL. Any ideas?

[computer_expert]

Have you tried running the post setup by opening the WSUS console rather than using server manager? I had a similar problem recently and I think this was what I did to fix it... Edited May 26, 2020 by computer_expert

[DJ-1701]

Unfortunately that failed as well.

[computer_expert]

That's odd - I've just set up a Server 2019 VM with SQL Express 2019 and it has worked first time. Does the use account use to install WSUS have permissions to the new WSUS DB?

 

Uninstall WSUS, delete the DB and check IIS to ensure the 'WsusPool' Application Pool has been removed, as well as the 'WSUS Administration' site in IIS. Also delete and recreate the location where the WSUS downloads are stored. Once you've done this, try reinstalling WSUS again.

[DJ-1701]

That's odd - I've just set up a Server 2019 VM with SQL Express 2019 and it has worked first time. Does the use account use to install WSUS have permissions to the new WSUS DB?

 

Uninstall WSUS, delete the DB and check IIS to ensure the 'WsusPool' Application Pool has been removed, as well as the 'WSUS Administration' site in IIS. Also delete and recreate the location where the WSUS downloads are stored. Once you've done this, try reinstalling WSUS again.

 

Ironically, this is a virtual server, been rebuilt quite a few times using the Domain Admin account with windows authentication to the SQL database and the VM currently has checkpoints on.

 

Uninstalled WSUS, deleted DB, checked IIS no WsusPool nor WSUS Administration. WSUS download directory deleted.

 

Reinstalled... same failure. How very, very odd...

[computer_expert]

Do you have a leftover WID DB located at C:\windows\WID\Data\susdb.mdf? That's the only thing I can think of that may be causing an issue.

[DJ-1701]

Do you have a leftover WID DB located at C:\windows\WID\Data\susdb.mdf? That's the only thing I can think of that may be causing an issue.

 

Nope, unfortunately not. Enough to drive you crazy huh?

[computer_expert]

I'd rebuild the server at this point from a fresh VM with fresh media from VLSC and try again.

 

There's some stuff in the updated section that you could verify here: https://docs.microsoft.com/en-gb/archive/blogs/reshard_sharps_blog/wsus-post-deployment-configuration-fails-on-windows-server-2012

[DJ-1701]

I'd rebuild the server at this point from a fresh VM with fresh media from VLSC and try again.

 

There's some stuff in the updated section that you could verify here: https://docs.microsoft.com/en-gb/archive/blogs/reshard_sharps_blog/wsus-post-deployment-configuration-fails-on-windows-server-2012

 

Yeah, this was from fresh ISOs from VLSC and I have rebuilt the VM a few times before I started using Snapshots. As in line with my bad luck, that's one of the articles I have followed to configure from the command prompt which also failed. Thanks very much for your helpful posts, just typical that this weirdness continues to stump me as it has for a few days now.

[computer_expert]

After a lot of messing about manually creating SUSDB in SQL Management studio I finally have the same error as your original post. I'm going to snapshot the VM and have a crack at seeing what's wrong.

[computer_expert]

I managed to get past the error in the first post by running the following in SQL management studio:

C:\Program Files\Update Services\Database\UpdateSchemaVersion.sql

 

After running that it then threw up a load of other errors which I wasn't able to fix by running other scripts in the directory above. I ended up deleting the DB via SQL management studio (but not removing the WSUS role/content directory) then running the command below in powershell which seemed to get it into a usable state.

 

wsusutil.exe postinstall SQL_INSTANCE_NAME=server\SQLEXPRESS

 

If none of that works, maybe try a fresh install but leave it in a workgroup until after WSUS is set up to see if you have a GP setting causing issues somewhere.

[DJ-1701]

I managed to get past the error in the first post by running the following in SQL management studio:

C:\Program Files\Update Services\Database\UpdateSchemaVersion.sql

 

After running that it then threw up a load of other errors which I wasn't able to fix by running other scripts in the directory above. I ended up deleting the DB via SQL management studio (but not removing the WSUS role/content directory) then running the command below in powershell which seemed to get it into a usable state.

 

wsusutil.exe postinstall SQL_INSTANCE_NAME=server\SQLEXPRESS

 

If none of that works, maybe try a fresh install but leave it in a workgroup until after WSUS is set up to see if you have a GP setting causing issues somewhere.

 

The SQL does execute successfully, and I do get a different error when trying to complete post-installation (Fatal Error: Could not find stored procedure 'dbo.spSetDefaults'), but unfortunately when deleting the DB and running the command I just get Fatal Error: Database creation failed. I will continue battling with that error and as you suggest installing when the server is in a workgroup. Many thanks for your help.

[DJ-1701]

This is so very wierd... installed from scratch on a workgroup, failed... installed from scratch with SQL 2017 instead... failed again. Same darn error.

[computer_expert]

Wow...I'd thought the workgroup would have worked!

 

Are you disabling/changing any of the SQL server settings from default?

[DJ-1701]

Just installing the Database Engine Service and apart from the default, setting the SQL collation to SQL_Latin1_General_CP1_CS_AS as will be using for SCCM after WSUS can be installed and this was mentioned as required in their instruction.

[computer_expert]

Just installing the Database Engine Service and apart from the default, setting the SQL collation to SQL_Latin1_General_CP1_CS_AS as will be using for SCCM after WSUS can be installed and this was mentioned as required in their instruction.

 

The SQL collation was going to be my next suggestion (but I had the impression this was for a standalone WSUS box!)

 

Unless that's a typo, I think you may be using the wrong collation for SCCM. I think it should be SQL_Latin1_General_CP1_CI_AS. One of the SQL setup scripts for WSUS also lists this as a requirement too.

[DJ-1701]

The SQL collation was going to be my next suggestion (but I had the impression this was for a standalone WSUS box!)

 

Unless that's a typo, I think you may be using the wrong collation for SCCM. I think it should be SQL_Latin1_General_CP1_CI_AS. One of the SQL setup scripts for WSUS also lists this as a requirement too.

 

Sorry, if I did say my master plan it might have helped... and again thank you so much, instructions do say CS, but will try CI, sounds logical if that is a requirement for WSUS that it should work!

[DJ-1701]

Bingo, bango, bongo, that was it. Many, many thanks!

 

Remove (and afterwards re-added) previous thanks to all me to give you the Rep you rightly deserve.