I'm running webgisdr to do a migration.
Server takes 2 minutes, Relational Data Store takes 10 minutes. Portal just never completes. The staging folder has 79GB, but it has been like that for about 6 hours now.
What version are you on? I feel like I read about something similar in a patch's "issues addressed" list.
We are on 11.2. With the goal of migrating machines and upgrading to 11.3
Did you try pressing "Enter" on the command line ? Sometimes it get stuck...
You shouldn't have any problems upgrading. One tip: backup your setup using the webgisdr utility. It will create a file with an extension of .website. If you change that extension to .zip, it has each of the individual components available to restore. This way if one component upgrade goes sideways, you can just restore that particular part instead of having to roll everything back.
Hello @CW-GIS ,
It would be great if you can share details from the logs generated by WebGISDr process (usually created where you store the properties file). It will help us in understanding at which step this is failing/which steps take such long time.
Additionally, an easy way to isolate this problem is to switch Portal logging level to "DEBUG" and run "exportsite" operation from Portal Admin endpoint by following the steps in below document :
https://developers.arcgis.com/rest/enterprise-administration/portal/export-site/#file-store-request-parameters
While this is running check Portal logs with "DEBUG" for more detailed error message which will help in understanding (If possible share that here)
Note : Remember to switch the logging back to way it was otherwise it can consume a lot of storage on the machine
The reason that this will help isolate is because it is what "WeebGISDr" essentially does in case of Portal for ArcGIS.
If you can share these, we can probably look for the root cause of this.
Hope this helps!
@k1aska wrote:You shouldn't have any problems upgrading. One tip: backup your setup using the webgisdr utility. It will create a file with an extension of .website. If you change that extension to .zip, it has each of the individual components available to restore. This way if one component upgrade goes sideways, you can just restore that particular part instead of having to roll everything back https://100001.onl/ .
You shouldn't have any problems upgrading. One tip: backup your setup using the webgisdr utility. It will create a file with an extension of .website. If you change that extension to .zip, it has each of the individual components available to restore. This way if one component upgrade goes sideways, you can just restore that particular part instead of having to roll everything back https://100001.onl/ .
I got this,...
This actually worked for us...weird.
If you haven't done this already, make sure that command prompt is not in QuickEdit mode. If it is in QuickEdit mode, then I believe it gives the appearance that it is stuck.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
