Latest Contributions by JonathanQuinn

That's a challenging problem because it doesn't seem like the list() function has any print statements you can use for debugging... yet. You could step through it using your IDE and add various print statements in the function so you know where it's hanging. What URL are you using to connect to the site? You can experiment with different ones to see if it's a specific machine that's a problem. ... View more

Do you have a standby or dev environment to upgrade, or are you upgrading your production environment? The only way to get to a newer version is to upgrade. We put together a blog on minimizing downtime and risk during an upgrade: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/minimize-downtime-when-upgrading-arcgis-enter…  You can use this approach to vet out the upgrade and work through any issues without impacting production. ... View more

No, the DR tool backups are not forward compatible. We do plan on supporting that at some point, but even that workflow would internally trigger an upgrade. Have you reached out to Support regarding your failed upgrade attempts? Do you recall if they all cite similar errors? ... View more

If it's only OfflinePackaging that's a problem, then it does seem like it's something specific in that workflow. Are you using a web adaptor as well? I'm not familiar with that workflow enough to know what the traffic should look like, but it seems as though Server will tell Portal what URL to use in the item when it's creating it. Does the admin URL use "arcgis", or do they both use "server1"? ... View more

How long does it take to backup? How much content do you have? Can you describe your enviroment, (distributed, HA, etc). ... View more

It's expected that the config-store-connection.json file doesn't get re-created and the Postgres processes don't start. Renaming the config-store-connection.json file puts the portal into "upgrade mode" so you can let portal reconfigure things for you. I suggest you try this workflow with the Support analyst. ... View more

Did you back up the original index directories, or did you delete them? If you backed them up, then I suggest you revert them just to get Portal back up and running. If you deleted them you could go through an "upgrade": 1) Stop portal 2) Rename the config-store-connection.json file 3) Start Portal - this puts portal in "upgrade mode" and does not expect the indices to be available 4) Within the Portaladmin API, "upgrade" the portal -> this is just moving from 10.8 to 10.8, which won't do much other than reconfigure things, such as the index, which is what's failing for you If you do go this route, discuss it with the tech support analyst first, and take a backup or snapshot prior to running this. ... View more

When creating new users, you can create them in bulk, or one at a time. Naturally, you'd want to create them in bulk if you have a lot of new users using a CSV. However, since you also want to notify users of their credentials, what you can do is with Python, write a script that loops through your CSV, calls into the createUser function of the Python API to create each user. Since you have their email information, you can craft a boilerplate message and also use Python to send an email to all new users after each are created, giving them the information they need. ... View more

In regards to internal components not being HA as they're active passive, HA in general means no single points of failure. A primary and standby database, with automatic failover, means that there isn't a single point of failure at the database tier. An environment doesn't need to be active/active at every tier for it to be HA. In regards to the problem, you're at 10.8, correct? Did you attempt to rebuild the index manually? In your case, there are two problems: split brain issue with the internal index service, and it appears you may have rebuilt the index manually, which further corrupts it. Do you have a support case open? If so, can you provide the case number? ... View more

If you're implementing disaster recovery using geographic redundancy, you can use the same license for each, as only one site is active: Configure disaster recovery for ArcGIS Enterprise—Portal for ArcGIS (10.8) | Documentation for ArcGIS Enterprise  Additional ArcGIS licenses are not required for the standby deployment because it is not actively accessed; you only make it the active deployment if the primary fails. You're somewhat in the same situation; you're setting up a new environment that won't be production, and will just be used for upgrading. Eventually, you'll cut over, but as long as you're not configuring both to be active and receiving requests as if they were both production, then you'll be fine. ... View more

Has the analyst tested the capital letters in hostnames theory? They should be able to test that in-house to see if they can reproduce the problem. ... View more

No, the portal can contain items, the restore process will delete everything and restore everything in the backup. The "failed to delete the database directory" error is strange. Does that happen consistently? If you can, try to monitor the running processes on the machine. During the restore, the PG processes should go away, so that the old DB can be backed up/deleted before the new one restored. ... View more

You could look at the logs under <install directory>\framework\runtime\ds\usr. Sometimes they can provide useful information about why the index service won't start. ... View more

The index service isn't starting. Are you on a one core machine? If so, you'll need to be on a machine with at least 2 cores starting at 10.8. If you are on a machine with at least 2 cores, troubleshooting index related issues can get complicated; I suggest you reach out to Support. ... View more