Azure Arc Extension causing errors with in-place upgrade from 2017 to 2022

Question

Azure Arc Extension causing errors with in-place upgrade from 2017 to 2022

Sam Kahanda 0

I am trying to do an in-place upgrade from SQL server 2017(Standard) to 2022(Standard). Everything goes well until it throws an error related to Azure Arc extension. Mine is a VM running on-prem. got nothing to do with Azure Arc. How can I get around this? I have quoted the error thrown below.

"TITLE: Microsoft SQL Server 2022 Setup

The following error has occurred:

The parameter is incorrect.

For help, click: https://go.microsoft.com/fwlink?LinkID=2209051&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xDBB00D2A%25400x294A9FD9

BUTTONS:

OK

------------------------------"

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-24T11:32:12.22+00:00

If the error is related to the Azure Arc extension, I'm inclined to think that VM is Arc-enabled. If you look in Program and Features, do you see Azure Connected Machine Agent?

It would help to see the logs. They should be in C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Logs with one folder per install attempt. The files of most interest are Summary.txt and Detail.txt.

Also, share the output of "SELECT @@version".

Did you restore the VM to the original state, or is in the state after the installation failure?
Sam Kahanda 0 Reputation points

2025-05-24T11:44:15.56+00:00

Unfortunately I had to restore the VM to bring the services online and my bad that I hadn't saved the log files. But I checked the programs and features and there is no trace of Azure agent. I tried a few other things to see if it is there and nothing at all. In fact we don't use Azure services. This is just a onprem Hyper-V server
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-24T12:17:52.5633333+00:00

It's understandable that you restored the VM. You will have to clone it and try to upgrade the clone before you try the real McCoy next time.

Again: What does "SELECT @@version" report?

1 answer

Your answer

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-24T11:32:12.22+00:00

If the error is related to the Azure Arc extension, I'm inclined to think that VM is Arc-enabled. If you look in Program and Features, do you see Azure Connected Machine Agent?

It would help to see the logs. They should be in C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Logs with one folder per install attempt. The files of most interest are Summary.txt and Detail.txt.

Also, share the output of "SELECT @@version".

Did you restore the VM to the original state, or is in the state after the installation failure?
Sam Kahanda 0 Reputation points

2025-05-24T11:44:15.56+00:00

Unfortunately I had to restore the VM to bring the services online and my bad that I hadn't saved the log files. But I checked the programs and features and there is no trace of Azure agent. I tried a few other things to see if it is there and nothing at all. In fact we don't use Azure services. This is just a onprem Hyper-V server
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-05-24T12:17:52.5633333+00:00

It's understandable that you restored the VM. You will have to clone it and try to upgrade the clone before you try the real McCoy next time.

Again: What does "SELECT @@version" report?

Answer 1

@Erland Sommarskog Thanks for checking on this and giving me valuable feedback. I found the issue and managed to complete the in-place upgrade.

The link given on the error (https://go.microsoft.com/fwlink?LinkID=2209051&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xDBB00D2A%25400x294A9FD9) is misleading as it lands on the incorrect page that is on ARC registration. The real problem was the feature "Machine Learning Services and Language Extensions". Since the upgrade wizard does not give you an option to untick this feature, I manually uninstalled the feature on the old version (using the install wizard for SQL server 2017) and then tried the in-place upgrade which went through without any issues. If I need, I think I can install the machine learning extension later on, which we don't need at this point.

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-01T22:03:09.46+00:00

I am glad to hear that you found the issue!

And I am glad to hear that you took the time to report back, so that other people can take benefit of your findings as well.

Share via

Azure Arc Extension causing errors with in-place upgrade from 2017 to 2022

1 answer

Your answer