In-Place Upgrade 2012 R2 to 2019 Post Install WSUS Fails to reinstall

Question

As the title says we moved are SCCM 2107 (primary site) from 2012 R2 to 2019. The In-place upgrade went smooth and everything looks good in the SCCM console. However, I can't seem to reinstall WSUS using the existing SQL database. Keep in mind I NEVER removed the SCCM SUP role per Microsoft's SCCM In-Place OS upgrade guide.

Here is the error:
Establishing DB connection...
2021-12-09 21:09:19 Checking to see if database exists...
2021-12-09 21:09:19 Database exists
2021-12-09 21:09:19 Switching database to single user mode...
2021-12-09 21:09:19 Ensuring SUSDB is set to Multi-User Mode ...
2021-12-09 21:09:19 Disposing Connection
2021-12-09 21:09:19 Clearing Connection Pools
2021-12-09 21:09:19 System.Data.SqlClient.SqlException (0x80131904): User does not have permission to alter database 'SUSDB', the database does not exist, or the database is not in a state that allows access checks.
ALTER DATABASE statement failed.

I've done the whole SQL query steps mentioned here: https://www.anoopcnair.com/fix-the-error-database-is-in-single-user-mode/

1. When I query, I find ZERO active users or session IDs. (And the query does run successfully.)
2. When I run ALTER DATABASE SUSDB SET MULTI_USER - I just get a user permissions issues..

I'm literally out of ideas on what to do next...

Not sure if this was the culprit too, but I messed up the first WSUS install and selected the WID role instead of SQL. However, I followed the steps to "purge" WSUS; removed the roles, renamed the WID folder, rebooted and have been trying to reinstall WSUS now using SQL role.

Source:
https://www.anoopcnair.com/sccm-server-in-place-os-upgrade/

Answer 1

@Trav Y
Thanks for your posting on Q&A.

According to this link, we should remove the WSUS role before upgrade.

Have you backup the SUSDB database before upgrading? Please try to remove the WSUS and SUP role and reinstall it on the site server. Then we could restore the SUSDB by the below command on the SSMS:

RESTORE DATABASE SUSDB  
  
FROM DISK = 'C:\backup\susdb.bak'  
  
WITH REPLACE  

Regards,
Rita

Answer 2

Any insight or thoughts?

Question - What if I de-attach the current SUSDB? And reinstall the WSUS role using a blank DB?

If installs (Role & new SQL SUSDB).

1. What happens to SUP and WSUS? Will WSUS just pull the info from SUP?
2. I could try de-attaching the new DB and re-attaching the old SUSDB?

If fails, then I restore back. Not sure what else I can do to resolve the issue..

Answer 3

Update-

r/SCCM came through again!

https://sccmentor.com/2021/07/27/in-place-upgrade-of-configmgr-site-server-from-windows-2012-r2-to-2019/

This linked helped a lot. The thing I missed was the recommendation on just rebuilding WSUS using a blank DB. Then re-attaching the original WSUS SUSDB. I ran into a few issues with site status, but the link resolved most of those issues as well.

Note: If you uninstall or install WSUS and don't reboot (even if not required.) It could break PXE booting and/or software center in SCCM. As it appears some configuration files get altered with WSUS roles. I discover that the hard way. (Sorry Service desk.)

I apologize for the delay in response too. This project went out of scope and outside of "SCCM's" maintenance window, so I had to go through the fun of approvals and e-mails notifying people of outages.

So far SCCM logs are healthy, but it's only been about 4 hours since the resolving. I plan on checking SCCM tomorrow to confirm things are still running smooth.