Forum Discussion
Solved
Upgrade Windows Server 2019 Evaluation Issue
Every time I try to upgrade our evaluation datacenter I get this error. DISM.log 2023-05-10 13:32:23, Info DISM PID=1812 TID=2520 Scratch directory set to 'C:\Users\sajellis\AppData\Local\Tem...
- Dave,
So this command:
Dism /online /Set-Edition:ServerDataCenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula
is the same thing as downloading the Windows Server 2019 iso and running it on the computer.
I downloaded that iso, ran it, installed the Windows Server 2019 Datacenter (Desktop Experience) and kept files and apps.
The server went through the upgrade process.
I then used the slmgr /ipk and slmgr /ato command and everything was fine.
Thank you again for assisting me in finding the resolution.
What channel is the product key? OEM, retail, volume? Just to confirm you're using a KMS key that fails?
I’m using the KMS Client Product Key for Windows Server 2019 Datacenter from the link you sent in your first reply.
I run the command in the picture of my post, it will go through without errors normally, I reboot the server then put in the slmgr /ipk and slmgr /ato.
It has worked fine with other servers before and after this server. But for some reason this server will not go through the first command.
I hope that makes sense.
I run the command in the picture of my post, it will go through without errors normally, I reboot the server then put in the slmgr /ipk and slmgr /ato.
It has worked fine with other servers before and after this server. But for some reason this server will not go through the first command.
I hope that makes sense.
Ok, well also note that Error: 14081 == The referenced assembly could not be found. So not a good start for this one. A repair install may sort it but time may be better spent standing up a new one, patch fully, activate and move on.
- Dave… Mr. Patrick…
How did you ascertain
“The reference assembly could not be found”?
This is the first time I am seeing that, also, what does that mean exactly? Something important is missing? The DISM and CBS logs lead me down a path of trying to fix update components.Most likely is a broken dontnet framework, you can try other things like installing windows updates or resetting windows update. Additional resources for Windows Update - Windows Client | Microsoft Learn and the repair install, then beyond that it may be time to clean install it.