Closed abakhtin9 closed 1 year ago
@abakhtin9
To fix the The term 'ArcGIS_WaitForComponent' is not recognized as the name of a cmdlet
error please use the following workaround (three changes). This fix will be included in a future release.
To:
ComponentHostName = $PrimaryPortalMachine
To:
Credential = $PortalAdministratorCredential
To:
[Key, ValueMap{"Server","NotebookServer","MissionServer","Portal","ServerWA","PortalWA","DataStore","SpatioTemporal","TileCache","GraphStore","ObjectStore","UnregisterPortal"}, Values{"Server","NotebookServer","MissionServer","Portal","ServerWA","PortalWA","DataStore","SpatioTemporal","TileCache","GraphStore","ObjectStore","UnregisterPortal"}] String Component;
Note: apply these changes to the module on all the target nodes and orchestrating node. After making the updates, use a fresh powershell window to re-run the Invoke-ArcGISConfiguration command.
@cameronkroeker Thank you for this - issue was resolved with the workaround!
This has been addressed in v4.1.0.
https://github.com/Esri/arcgis-powershell-dsc/releases/tag/v4.1.0
Thanks, Cameron K.
Community Note
Module Version
Affected Resource(s)
Configuration Files
Expected Behavior
After licensing Server and Portal, should have went to the next step for ArcGIS Server configuration.
Actual Behavior
After licensing ArcGIS Server, it fails to configure it:
Steps to Reproduce
Use the following command with the configuration above:
Important Factoids
Invoke-ArcGISConfiguration -ConfigurationParametersFile <filelocation.json> -Mode InstallLicenseConfigure -DebugSwitch -UseSSL -Credential GISAdmin
(using the service account), we get the following errors:References