I'm trying to upgrade our 11.1 Enterprise to 11.3 using PowerShell DSC. Multi machine deployment (Portal, ArcGIS Server, Relational Data Store, Spatiotemporal Data Store, Web Adaptor host). All hosts have the ArcGIS 4.4.0 PowerShell module.
This week I deployed 11.1 using DSC with no issues, now trying to upgrade this test environment before moving to production. DSC is failing on the portal upgrade:
Trace-DSCJob : 11/23/2024 9:08:20 AM: The SendConfigurationApply function did not succeed.
At C:\Program Files\WindowsPowerShell\Modules\ArcGIS\4.4.0\ArcGIS.psm1:263 char:5
+ Trace-DSCJob -Job $Job -JobName $ConfigurationName -DebugMode $De ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Trace-DSCJob
Logs Directory: C:\Users\svc_arcgis\Logs
Finished DSC Job:- PortalUpgrade. Time Taken - 00:02:45.6950068
PortalUpgrade - Failed
Portal Upgrade Install Step Failed
At C:\Program Files\WindowsPowerShell\Modules\ArcGIS\4.4.0\ArcGIS.psm1:2840 char:9
+ throw "Portal Upgrade Install Step Failed"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Portal Upgrade Install Step Failed:String) [], RuntimeException
+ FullyQualifiedErrorId : Portal Upgrade Install Step Failed
The error message does not point me in a particular direction. Checking event logs on the Portal host show error 28809 - Could not validate credentials for domain\svc_arcgis.
This is an Active Directory domain account and is used as the service account for our 11.1 deployment. I've confirmed with our IT that the account is not locked out/disabled and the password we have is correct.
Has anyone encountered this error when upgrading Enterprise with DSC?
Hi @tigerwoulds
A stab in the dark - it's possible Powershell DSC or Portal is interpreting the backslash in username as an escape character. You could either try double backslash, or use the format username@domain instead.
Additionally, I would try to run powershell (or any other application) as the service account just to confirm the service account credentials are all good.