ArcMapRuntime and DotNetSupport are not installed when upgrading despite setting Parameters in config true

[niol-zh]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request

Module Version

3.3.0

Affected Resource(s)

• ArcGIS_Server

Configuration Files

"EnableArcMapRuntime": true
"EnableDotNetSupport": true

Expected Behavior

Upgrading from ArcGIS Enterprise BaseDeployment from 10.8.1 or 10.9 to 10.9.1
With both Parameters set to true , the DotNet and ArcMap Runtime and Python 2.7 should be installed with mode -upgrading

Actual Behavior

Both are not installed and need to be manually installed.
https://enterprise.arcgis.com/en/server/latest/administer/windows/disable-arcmap-runtime.htm

Steps to Reproduce

Run
Invoke-ArcGISConfiguration -ConfigurationParametersFile <config.json> -Mode upgrading

[niol-zh]

@scma-esrich

[niol-zh]

Hi @shailesh91
thank you for verifying this issue.
Do you have any inputs or ideas for a possible workaround?
Best regards,
Olivier

[shailesh91]

@niol-esrich a possible workaround is replacing $Version with $cf.ConfigData.Version in the following lines

arcgis-powershell-dsc/Modules/ArcGIS/ArcGIS.psm1

Lines 2135 to 2136 in 6a8456b

	EnableArcMapRuntime = if($Version -ieq "10.9.1"){ if($cf.ConfigData.Server.Installer.ContainsKey("EnableArcMapRuntime")){ $cf.ConfigData.Server.Installer.EnableArcMapRuntime }else{ $True } }else{ $False }
	EnableDotnetSupport = if($Version -ieq "10.9.1"){ $cf.ConfigData.Server.Installer.EnableDotnetSupport }else{ $False }

[niol-zh]

@shailesh91
Thank you for your quick reply. With this workaround we were able to upgrade successfully.

[ZianAtFirstWatch]

The workaround resulted in a crash when I ran it with a configuration Json file that did not define the value for the EnableArcMapRuntime or EnableDotnetSupport properties. My workaround was to set those 2 values to $True and comment out the existing code inside ArcGIS.psm1 at the two lines that @shailesh91 mentioned.

Unfortunately, I have lost the error message and cannot provide it any more.

[cameronkroeker]

This bug has been addressed in v3.3.1.