-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual Machine Upgrade Federated/Hosting Server Web Adaptor Configure fails #98
Comments
@l84tahoe One of the prereqs of Running Powershell DSC is that the installation files should be accessible on the target machines (Either installation files are placed on a file share accessible the local system account of the target machine or local to the target machine placed as specified in the JSON config file). |
@shailesh91 The files are on a local drive ( D:\ ) of each machine. The issue with that error is that I never said Machine1 should have a datastore but the script thinks it should have it. I will rerun using the -DebugSwitch right now. |
I don't think the error was on machine1 as the error doesn't specify a machine name. It would be great to have the logs generated though. |
Sorry I didn't make it clearer earlier. Here is the Powershell output showing Powershell trying to install on Machine1 when it shouldn't:
|
@l84tahoe it is a bug. I can provide you a local patch just in case you are testing right now. |
@shailesh91 I am. Will this patch also fix the webadaptor issue? |
@l84tahoe I am still unclear on the web adaptor issue. I need more logs to tell what might be going wrong. |
Sorry, here is the verbose log of the incident:
The admin account is a built in account and not a domain account. |
@l84tahoe can you try running this command for cmd
Another thing you can try is going to "https://Machine1.domain.com:7443/arcgis/portaladmin" and try logging in. |
@l84tahoe |
@shailesh91 I am able to log in using the built in admin account through |
@l84tahoe Can you try registering web adaptor through the UI, just to check if we get the same error or is something to do with configure utility. |
@shailesh91 I am waiting for the upgrade with |
@shailesh91 The portal web adaptor config failed again. Same 401 error. Server web adaptor now fails as well with this error:
And after copying your updated
After this error the config stops. |
@l84tahoe Can you try with this file. And if possible please provide verbose logs. That will be very helpful. |
@l84tahoe can email me at shgoel@esri.com . I can help you to debug the problems on skype. |
The issue was fixed in 1.1.3 and 1.1.4 release. Closing the issue. Please reopen it still persists. |
@shailesh91, maybe the Web Adaptor-part of the bug came back with the release 3.0.0 of the DSC-module. Our customer is trying to upgrade a multi-machine base-deployment from 10.7.1 to 10.8 and triggers the following error:
The server-OS is German, hence the error-messages are also in German. However, the main-part of the error-message translates exactly to: This is the corresponding Verbose-log-statement:
|
@shailesh91 and @cameronkroeker: May it be that the "/qb"-parameter is causing the problem, with an alert-window popping up? |
@shailesh91 and @cameronkroeker: Ignore my last two posts. |
We are trying to upgrade an existing ArcGIS Enterprise (10.6 to 10.6.1) on two machines in our development environment and run into a specific error when Powersehll DSC tries to configure the federated hosting server web adaptor:
[]PowerShell DSC resource ArcGIS_WebAdaptor failed to execute Test-TargetResource functionality with error message: PowerShell Desired State Configuration does not support execution of commands in an interactive mode. Please ensure that the underlying command is not prompting for user input, such as missing mandatory parameter, confirmation prompt etc. []The SendConfigurationApply function did not succeed.
Since this web adaptor doesn't get configured correctly we are having a hard time trying to get all three components to link.
We also are unable to get the datastore to configure even though the script said it was successful. I believe it's because the web adaptor for the server failed.
In the log of the datastore upgrade we see this:
and we can't find the file referenced above.
We also see this a few lines below:
Another odd error we see is that Powershell DSC tried to install datastore on the other machine and fails because the installation file is not on that machine. After that error Powershell DSC then tries to upgrade the correct machine. Here is the error:
Here is our configuration file:
The text was updated successfully, but these errors were encountered: