nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Enterprise 11.0: webgisdr restore fails

NicolasGIS

Hello,

Since I upgraded from ArcGIS Enteprise 10.9.1 to 11.0, I can successfully create a webgisdr backup but cannot restore it. Whenever I try to restore, it fails for ArcGIS Server with the following error:

Failed to restore the ArcGIS Server:

{
"code": 500,
"messages": ["Import site failed with the following error. The store implementation is not connected to a config store. Please call the connect method before invoking any other method.", "Import operation failed and an attempt to rollback the site to its original state also failed. The site may be functional but it is recommended that you unregister all machines in the site and create a new site based off the configuration store that was backed up at 'C:\\Users\\foo\\AppData\\Local\\Temp\\tmp-ags-site-14599189019367108479128716508001500\\config-store' and the server directories backed up at 'C:\\Users\\foo\\AppData\\Local\\Temp\\tmp-ags-site-14599189019367108479128716508001500\\directories'."],
"status": "error"
}

Was able to reproduce on simple sandbox machine with a base ArcGIS Enteprise deployment on which that workflow used to work at 10.9.1.

Any idea ? Maybe @JonathanQuinn ?

All tests done on Windows Server 2019.

Thanks !

Najděte více příspěvků označených jako

Accepted answers

ChristopherPawlyszyn

Curious to hear your results as well but here's what I've found in my testing.

I was able to reproduce this issue with the latest build by first creating a site for ArcGIS Server, exporting the site, creating a hostname.properties file (with the same FQDN defined as the original machine name) and restarting the service, then attempting to import the exported site.

I've created an issue internally for tracking this behavior and I expect preventing the hostname.properties file from being created during an upgrade using PowerShell DSC should be a viable workaround for the time-being.

When using the standard PowerShell DSC release branch, the hostname.properties file exists prior to site creation, so doesn't cause the failure condition from what I can tell.

All comments

NicolasGIS

I did some additional testing and noticed that this issue occurs only when done on an upgraded ArcGIS Enterprise deployment.

ArcGIS Enterprise base deployment 11.0 -> export webgisdr -> import webgisdr -> successul

ArcGIS Enterprise base deployment 10.9.1 -> export webgisdr -> import webgisdr -> successul -> Upgrade base deployment to 11.0 -> export webgisdr -> import webgisdr -> failed.

ChristopherPawlyszyn

Were you using a hostname.properties file at 10.9.1, by chance?

Starting to look into this further.

NicolasGIS

Thanks @ChristopherPawlyszyn for your reply.

I am deploying my environment using ArcGIS Powershell DSC and it does seem to use hostname.properties file:

https://github.com/Esri/arcgis-powershell-dsc/blob/4a33aabf965e2098699bddc499ce1d05003e992d/Modules/ArcGIS/DSCResources/ArcGIS_Portal/ArcGIS_Portal.psm1#L486-L493

Thanks for having a look

ChristopherPawlyszyn

@NicolasGIS I deployed a 10.9.1 environment and upgraded to 11.0 with PowerShell DSC and did not reproduce the issue you're describing.

In your scenario for the upgrade, did you use PowerShell DSC as well or perform the process manually?

NicolasGIS

Thanks @ChristopherPawlyszyn for your reply and time.

It's really weird... Following your reply I tried again from scratch with the same result: ArcGIS Server fails to restore.

In ArcGIS Server logs, I have plenty of errors such as:

akka.pattern.AskTimeoutException: Recipient[Actor[akka://akka-rediscovery/user/AkkaAppServerActor#-1696377499]] had already been terminated. Sender[null] sent the message of type "com.esri.arcgis.discovery.admin.rediscovery.util.Message".

But I don't think it is the root cause.

The only difference I see between you and I, is that I use my own fork of ArcGIS DSC because of issue 132:
https://github.com/Esri/arcgis-powershell-dsc/issues/132

I prevent DSC from configuring the hostname:

I had open a BUG regarding this issue:
https://my.esri.com/#/support/bugs/BUG-000124901

As you asked about the hostname.properties file, do you think it could be related ?

Regarding the issue itself, I don't know where to look for. Any idea what I could do to troubleshoot this issue ?

Finally, to answer to your question, the upgrade was done with Powershell DSC.

Thanks !

ChristopherPawlyszyn

Interesting, I'm not sure of the hostname.properties file as the cause just something I wanted to try to rule-out. I will try again with that modification to the module and see if I am able to reproduce it.

Is there any evidence of a machine name change (FQDN or IP address) during the upgrade process or following the export/import workflow?

NicolasGIS

FYI, @ChristopherPawlyszyn, I tried 2 additional tests:

- Manual install of 10.9.1 -> webgidr export -> webgisdr import -> OK -> Manual upgrade to 11.0 -> webgisdr export -> webgisdr import -> OK

- DSC Install of 10.9.1 -> webgidr export -> webgisdr import -> OK -> Manual upgrade to 11.0 -> webgisdr export -> webgisdr import -> OK

So it looks like the issue only occur when upgrading using DSC. Does it help ?

What could DSC be possibly doing differently than a manual install that would prevent ArcGIS Server from importing the site backup ?!

I will make it crash once again, and search any evidence of a machine name change to answer your question.

Thanks !

ChristopherPawlyszyn

I'm curious if you've commented-out the related hostname.properties section in the ArcGIS_ServerUpgrade.psm1 file as well:

https://github.com/Esri/arcgis-powershell-dsc/blob/master/Modules/ArcGIS/DSCResources/ArcGIS_ServerUpgrade/ArcGIS_ServerUpgrade.psm1#L73-L80

If not, there is an additional indication that the hostname.properties file being added during the upgrade may be at fault, especially in light of your additional testing results.

NicolasGIS

Well spotted. I was about to test 😉.

Let me give it another run with this modification and I come back to you !

Thanks !

ChristopherPawlyszyn

Curious to hear your results as well but here's what I've found in my testing.

When using the standard PowerShell DSC release branch, the hostname.properties file exists prior to site creation, so doesn't cause the failure condition from what I can tell.

NicolasGIS

So I commented out the configuration of the hostname.properties file in ArcGIS Upgrade section as well as you suggested:

https://github.com/Esri/arcgis-powershell-dsc/blob/master/Modules/ArcGIS/DSCResources/ArcGIS_ServerUpgrade/ArcGIS_ServerUpgrade.psm1#L73-L80

And it now works !

So the root cause is now understood: great 🙂

Many many thanks for your support to identify the root cause !

Do you think there could be a way to "fix" a corrupted ArcGIS Server site ? What would be your recommandation ?

Thanks !

ChristopherPawlyszyn

If the config-store-connection.xml file exists in ../Server/framework/etc you can simply copy the config-store and directories from the temporary location back into place and restart the ArcGIS Server service. If that file is missing, you may need to grab one from a working deployment and update the contained path to match the site location for this machine.

NicolasGIS

Thanks for your reply Christopher.

In the end, I ended up recreating the ArcGIS Enterprise deployment from scratch at 11.0 and importing the webgisdr backup.

Many thanks for your precious support and good avices ! You had a good intuition from the beginning that hostname.properties file was involved !

Thanks

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.