New Contributor

Hi Everyone, nice to meet you.
Please if anyone can help me with this issue, I had a onpremise server with windows server datacenter 2016 and because the policies of the company we had to upgraded to windows server datacenter 2019. I download the ISO upgrade the system and upgraded definition and update from microsoft and restart the server, so far all fine.
On this server I have SCCM running with the WSUS role for SCCM to a get the update from microsoft. the console of MECM start without problem, but WSUS get the message post-deployment configuration.

the instace of the data base is on a different server with SQL

this is the log of the error.


2021-12-22 15:38:22 Postinstall started
2021-12-22 15:38:22 Detected role services: Api, Database, UI, Services
2021-12-22 15:38:22 Start: LoadSettingsFromXml
2021-12-22 15:38:22 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2021-12-22 15:38:22 Value is true
2021-12-22 15:38:22 End: GetConfigValue
2021-12-22 15:38:22 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2021-12-22 15:38:22 Value is C:\WSUS
2021-12-22 15:38:22 End: GetConfigValue
2021-12-22 15:38:22 Content directory is C:\WSUS
2021-12-22 15:38:22 Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
2021-12-22 15:38:22 Value is fcdb2\wsus
2021-12-22 15:38:22 End: GetConfigValue
2021-12-22 15:38:22 SQL instance name is fcdb2\wsus
2021-12-22 15:38:22 End: LoadSettingsFromXml

2021-12-22 15:39:54 Changed database context to 'SUSDB'.
2021-12-22 15:39:54 Msg 3728, Level 16, State 1, Server fcdb2\wsus, Line 19
'Unique_DynamicCategory_Name_Type' is not a constraint.Msg 3727, Level 16, State 0, Server fcdb2\wsus, Line 19
Could not drop constraint. See previous errors.
2021-12-22 15:39:54 Re-Establishing Connection to execute Multi User Query ...
2021-12-22 15:39:54 Ensuring SUSDB is set to Multi-User Mode ...
2021-12-22 15:39:54 Disposing Connection
2021-12-22 15:39:54 Clearing Connection Pools
2021-12-22 15:39:54 Microsoft.UpdateServices.Administration.CommandException: Database creation failed
  at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDatabase()
  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: Database creation failed


3 Replies

Upgrade to Windows Server 2016, 2019, or 2022
Use the steps in this section for any of the following upgrade scenarios:

Upgrade either Windows Server 2016 or Windows Server 2019 to Windows Server 2022
Upgrade either Windows Server 2012 R2 or Windows Server 2016 to Windows Server 2019
Upgrade either Windows Server 2012 or Windows Server 2012 R2 to Windows Server 2016

Before upgrade
(Windows Server 2012 or Windows Server 2012 R2 only): Remove the System Center Endpoint Protection (SCEP) client. Windows Server now has Windows Defender built in, which replaces the SCEP client. The presence of the SCEP client can prevent an upgrade to Windows Server.

Remove the WSUS role from the server if it's installed. You may keep the SUSDB and reattach it once WSUS is reinstalled.

If you're upgrading the OS of the site server, make sure file-based replication is healthy for the site. Check all inboxes for a backlog on both sending and receiving sites. If there are lots of stuck or pending replication jobs, wait until they clear out.
On the sending site, review sender.log.
On the receiving site, review despooler log.

It says here to uninstall WSUS before upgrade, did you do that?

Did this anwer your question?
best response confirmed by Zamir_orozco (New Contributor)

@Harm_Veenstra thanks for the answer, we have to delete the Db and create a new one.