Latest Contributions by JonathanQuinn

I definitely stay away from licensing if I can, but I'm pretty sure a 4 core license can be used on a 4 core machine or two 2 core machines. Ultimately, talking to your account manager is the best way to go. Personally, I think migration workflows (joinSite or the DR tool), should be treated like a failover environment. You can acquire a failover license at no extra cost, as no requests are going to that failover environment. This is somewhat similar, as long as you don't run in that temporary migration status for long, I think you should be able to use the same license but again, contact your account manager for further clarification. ... View more

Great feedback from Scott Fierro‌. I'll comment on the questions: 1) Join Site does work between operating system versions. It briefly states that in the bug, but we can certainly call it out better: Perhaps you’re experiencing hardware performance issues, or you want to run a newer operating system. 2) The DR tool requires Portal, and as Scott Fierro‌ indicates, the approach is more complex than the first option. The use of the etc\hosts file can get around some of the requirements of the tool, (for example that the front-end URLs are the same). That way you don't have to worry about DNS and how traffic is routed, nor how to migrate content between deployments that have different URLs. This is described in the Etc\hosts file section: Etc\hosts file A quick word on the use of the etc\hosts file, located under C:\Windows\System32\drivers\etc on Windows and the \etc folder on Linux: it’s used to resolve hostnames by entering IP addresses and associating the IP addresses to hostnames. For example, if my machine name has an IP address of 10.0.0.1 and is resolved to enterprise.domain.com via DNS, I can add an entry to the etc\hosts file on the machine to resolve the machine’s IP address to a different hostname: 10.0.0.1 alias.domain.com If I ping alias.domain.com in a command prompt the etc\hosts file is resolving alias.domain.com to 10.0.0.1, which is enterprise.domain.com. If I had a web server running on the machine, I can reach the web server via alias.domain.com or enterprise.domain.com. This approach is slightly more complicated than migrating using the Join Site workflow as the steps are dependent on your deployment type and requires modifying the etc\hosts file to manage hostname resolution.  This approach is useful if you need to maintain availability during the migration as you can stand up that separate environment without causing downtime for your production environment. Honestly, I wouldn't suggest setting up a new system with new URLs and migrating content over. Assuming you'll be using the same URLs are previously, this is how I'd foresee this going: 1)  Set up your new environment using new URLs 2) Use the Python API, specifically the ability to migrate content between environments, to move stuff from your old environment to your new environment. Hosted services would need to be republished. 3) Since there's no easy way to update the URLs of existing content, you'll need to set up another new environment that uses the same original URLs. 4) Move everything back to the original environment to use the correct URLs If you don't intend on using the same URLs, (which is unlikely as you're simply looking to migrate to new machines), then you wouldn't have to worry about 3 and 4. ... View more

The Web Adaptor doesn't need to be on the Server machine nor in the DMZ. It can be on whatever machine you have that meets the system requirements and meets the intended purpose of the endpoint, (for example, internal vs external access). You can set the WA up on the same as the ArcGIS Server for internal traffic. ... View more

When you upload content to Portal, the physical items are stored in the content directory and information about the item is stored in the database. The database doesn't store the item itself. Are you wondering about the performance of Portal when millions of items are in the Portal? ... View more

Is this a standalone Portal, or HA? If it's HA, did you stop the standby, stop primary, and then start standby before starting the original primary? ... View more

At 10.7.1, we updated how we reindex which should resolve index related problems, (corruption, mostly). If there's a couple item difference between the store count and index count, reindexing won't fix that. The best course of action is to work with Support to identify which items it can't add to the index. ... View more

So you were able to export from your original site, what happens if you move that properties file over to your new environment, and just update the URL and credentials? Even if the path is incorrect for the SHARED_LOCATION and BACKUP_LOCATION, leave it be and see if the DR tool can successfully read the path and validate it. It does sound like some sort of encoding problem: https://coderanch.com/t/702603/java/Malformed-uxxxx-encoding ... View more

Yes, all single backslashes should be escaped, but I've never seen that type of error before. What program are you using to edit the file? I don't think there's any other encoding/characters for a backslash, like there is for an apostrophe, (' vs ‘). What locale are you on? ... View more

Can you share the paths you're using for the SHARED_LOCATION property and scrub hostnames if necessary? I'm wondering if this is a forward/backward slash problem. ... View more

Seems like there are significant problems with the internal database and possible other files: 2019-07-17 15:27:35 PDT: [4340]: LOG:  archive command failed with exit code 1 2019-07-17 15:27:35 PDT: [4340]: DETAIL:  The failed archive command was: copy "pg_xlog\00000001000000250000007E" "C:\arcgisportal\backup\walarchive\00000001000000250000007E" 2019-07-17 15:27:36 PDT: [4340]: FATAL:  archive command was terminated by exception 0xFFFFFFFF <Msg time="2019-07-14T03:16:06,432" type="WARNING" code="217065" source="Portal" process="1536" thread="1" methodName="" machine="" user="" elapsed="">Error checking status of web server. java.util.concurrent.ExecutionException: org.xml.sax.SAXParseException; lineNumber: 129; columnNumber: 9; XML document structures must start and end within the same entity.</Msg> Are you taking scheduled backups or snapshots of the environment? ... View more

There are a couple of strategies you can use to migrate Enterprise to a new machine: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/migrate-to-a-new-machine-in-arcgis-enterprise/ https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/migrate-to-a-new-machine-in-arcgis-enterprise-two/ The second approach, that uses the DR tool, does support different backend machine names, but the public URL must remain the same. ... View more

There shouldn't be a need for the install user of Portal to be in the sudoers group, especially for an error that implies a locale problem: https://stackoverflow.com/questions/52539100/why-did-this-postgres-database-upgrade-fail I'd suggest you reach back out to your Support team and have them escalate to Esri Inc. if necessary. ... View more

Ah so it's closed as Known Limit, and a bit of Googling suggests it's a limit based on the format of the username and what property it's pulled from within AD? https://social.technet.microsoft.com/Forums/ie/en-US/63d2795c-8c28-4a22-9820-18190bfcdcf9/not-able-to-create-username-having-more-than-20-characters-in-active-directory?forum=winserverDS Anyway, not sure why the bug isn't searchable, but the workaround may take advantage of the userPrincipleName attribute which can be 64 characters. The sAMAccountName attribute can only be 20 characters. Not an AD expert by any means, so my explanation may be incorrect. ... View more

So the Portal machine has multiple hostnames? When you registered the Web Adaptor, did you use the alias or the hostname.domain.com to reach the web adpator registration page (ex https://alias.domain.com/[portal web adaptor]/webadaptor/portal)? ... View more