|
POST
|
Did you look at the database logs referenced in the error? They should tell you why the database won't start. There's a chance that a write was attempted and that used up the last of the disk space, corrupting the database. Do you have any backups or snapshots? I suggest you implement monitoring on the disk space of the machine or query the logs for WARNING/SEVERE messages for the future, so you can be notified of potential issues.
... View more
05-08-2020
03:44 PM
|
0
|
3
|
3149
|
|
POST
|
Do you see item ID folders within the content directory? Do the amount of folders match between the source and target environments? Does the index match up? There's validation in the import that will make sure the content in the backup and where it was restored to match. You can try to extract the backup and inspect it to make sure it contains the folders you'd expect by matching up the number of folders to the source environment.
... View more
05-08-2020
10:15 AM
|
0
|
8
|
2347
|
|
POST
|
Those backups are mainly for the software to be able to roll back, not so much for you to after the fact. I'd first suggest rolling back to a snapshot of the machines, or restoring from a backup using the WebGIS DR tool. If you did want to roll back those files yourself, theoretically you could uninstall, reinstall, create the site, stop Portal and replace the respective folders in the data directory with the ones that were backed up. I wouldn't suggest that route, though.
... View more
05-08-2020
09:26 AM
|
4
|
1
|
4903
|
|
POST
|
Looks like the bug has been closed as a Known Limit shortly after being logged with the following explanation: The spatial reference of the featureClass is correct but the values of x, y, xmin, xmax, ymin, ymax always come back as the spatial reference of the locator. It does offer a workaround, though: Right-click the X and Y fields, click Calculate Geometry, and change the units accordingly. BUG-000096273: Using a projected coordinate system under Advanced G..
... View more
05-05-2020
09:54 AM
|
0
|
0
|
1380
|
|
POST
|
Is the path actually Z:\arcgisportal\db? Is the Z:\ drive a physical drive on the machine, or is it a mapped drive? Do both environments use the Z:\ drive?
... View more
05-05-2020
09:34 AM
|
0
|
1
|
4206
|
|
POST
|
If any of the components are on different machines, then the SHARED_LOCATION must be a shared path, not a local path. The BACKUP_LOCATION can be local as long as there's enough space to hold the backup file. The time it takes to zip the backup will also be shorter if it's packaged locally.
... View more
05-04-2020
01:31 PM
|
2
|
4
|
6668
|
|
POST
|
It sounds like you federated using https://agssrv-domain.com/ags as the services URL and the admin URL? If so, that's the only URL you can use to reach Manager and the REST endpoint. Portal only knows about those URLs, so it can only generate tokens against those URLs.
... View more
05-04-2020
11:21 AM
|
0
|
1
|
2492
|
|
POST
|
There will be an explicit error, "config-store is not connected, invoke the connect() method...". In your case, you may be running into BUG-000121969 If both portal machines restart at the same time, the web server can become deadlocked. This can occur during a restore, when joining. It's fixed at 10.8.
... View more
05-04-2020
11:15 AM
|
1
|
0
|
2875
|
|
POST
|
That type of problem requires a bit of digging. When Portal starts the database, it sends the request to start it and waits for 5 minutes for it to be avaiable. If it's not, it reports that the startup timed out. The only way to see the reason why the database failed to start is through the Event Viewer logs. You can look at the timestamp of when the error occurred in Portal, and 5 minutes prior to that, you should see why the database failed to start. What version are you using? At 10.6 and earlier, you need to make sure that the db directory is the same between your source and target environments.
... View more
05-01-2020
01:54 PM
|
0
|
4
|
4206
|
|
POST
|
We recently put out a blog about upgrading while minimizing downtime: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/minimize-downtime-when-upgrading-arcgis-enter… It goes through a similar approach as what you're outlining. I'm not sure I understand the two server groups, though. do you have two separate Enterprise sites behind a load balancer, or is it currently HA, as the title of your post implies? You'll split out the machines and then configure them separately?
... View more
04-28-2020
11:24 AM
|
0
|
2
|
2724
|
|
POST
|
The DR tool shouldn't care about the owning system URL returned by the Data Store. When you registered the Web Adaptor on your new site, what URL did you use to reach the Web Adaptor registration page? Was it enterprise1.domain.com/<wa>/webadaptor or enterprise.domain.com/<wa>/webadaptor? If you used enterprise1.domain.com to reach the registration page, then that's the URL the Portal will configure for itself, even though the etc\hosts entry is in place to resolve the IP of the Web Adaptor machine to enterprise.domain,com. You need to access the Web Adaptor registration page through enterprise.domain.com.
... View more
04-28-2020
11:19 AM
|
0
|
1
|
4206
|
|
POST
|
After 20 hours, it has 100% either succeeded or failed, but the browser may have "lost track" of the request. Open a new tab and navigate to the Portal Administrator Directory. If you see a sign in page, the upgrade completed. you can sign in and if you see a Populate License dialog, that's even further confirmation it completed. You can open a new tab to the home app which will guide you through the rest of the upgrade.
... View more
04-21-2020
03:04 PM
|
0
|
1
|
1870
|
|
POST
|
You can increase the logging in the logback.xml file. You can set all log levels to DEBUG and then run the process again to see what it's hanging on. Another challenge people run into is getting into QuickEdit mode within the command prompt, which will pause any running process. that doesn't seem like the case for you though.
... View more
04-21-2020
02:46 PM
|
0
|
1
|
1193
|
|
POST
|
Portal's failover revolves around standby not being able to reach primary, so any of the ways you described will do that. There is no concept of "failover" for Server, since there are no roles. In either case above, the machine or service being unavailable will indicate to your load balancer (as long as you have HTTP health checking configured) or the web adaptor that the component is unhealthy, and it won't send traffic to it. For Data Store, yes, those scenarios will cause a failover.
... View more
04-15-2020
10:36 AM
|
1
|
1
|
1814
|
|
POST
|
You should be able to use exportSite/importSite, as long as the directories are local and are accessible on the target machine and the site is not federated to Portal.
... View more
04-15-2020
09:54 AM
|
0
|
0
|
971
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-28-2026 06:05 AM | |
| 1 | 08-26-2016 10:10 AM | |
| 2 | 02-22-2024 07:22 AM | |
| 1 | 06-07-2024 07:11 AM | |
| 4 | 12-12-2024 08:52 AM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|