Latest Contributions by JonathanQuinn

Ah, good find. Yes, the hostname.properties file does supercede the etc\hosts entry. Did you see the value change when you updated the hostname.properties file? ... View more

Unfortunately, the patch prevents it from occurring, rather than fixing a currently incorrect URL. The behavior if the hostname changes with the patch installed is that the URL is updated correctly. There may be some incorrect logic that detects that your hostname changed when it didn't, which we need to investigate. However, with the patch installed, you should be able to take advantage of what the software should be doing already; updating the URL to be the correct one: 1) Add an entry to the etc\hosts file on the portal machine to resolve the local IP address to the short name of the machine 2) Restart portal 3) Sign into the Portaladmin API and check the Machines API to ensure that the URL is correctly referencing the short name without portaladmin at the end 4) Remove the etc\hosts entry 5) Restart Portal 6) Make sure that the URL is referencing the FQDN.   I tested this on my end and was able to fix the issue with the patch installed. Have you gone through this with Support? ... View more

@BlairDeaver3is it feasible to write to the FileSystem and then you upload the backup manually using the AWS CLI? The reason why we don't compress the file when we upload is I don't believe there's a direct way to inspect the contents of a compressed file when it's in S3 storage like there is if the file was on the file system. This means we can't do some validation and other checks before actually downloading the backup. ... View more

Using a referrer based token is often the better approach when working with tokens, because of what @Anonymous User mentions; the IP of the request may not actually come from the machine you're making the request from. Using a referrer and including the referrer header in any requests to use the token is the preferred approach: https://enterprise.arcgis.com/en/server/latest/administer/windows/acquiring-arcgis-tokens.htm If there is a proxy server between the client application or browser and the ArcGIS Server site, tokens generated using the IP Address and IP address of this request's origin options must be bound to the IP address of the proxy server. If there are multiple load balancing proxy servers between the client application or browser and the ArcGIS Server, the HTTP Referer option should be used. ... View more

What you're doing is the correct approach; we externalized the regions information in the event there are regions you want to use that have been newly added, updated, or not covered yet. It should work once you update the file and make sure it's under the framework\etc folder. ... View more

How many items do you have in the portal? Where is the content located? When portal creates a backup, it stages files under C:\arcgisportal\temp. Do you see that directory grow in size and the number of files? Eventually it should match the number of items in the content directory before it's zipped up to a portalsite file and copied to the backup location.   ... View more

Once site creation fails with the "index service configuration failed" error, the "db" folder is left over in the C:\arcgisportal, (or equivalent path on your system). This tells portal to upgrade. If this is a new site, stop portal, delete the db folder, and try again. If it continues, I'd suggest contacting Support as index service related problems are challenging to resolve. ... View more

Members {size:1, ver:1} [ Member [ARCGIS-PORTAL.PPPP.LOCAL]:5701 - f4365794-3991-4feb-bd2a-c6a719943f32 this ] That line is an indication the cluster is getting created successfully. You can ignore most of what you see in the tomcat logs. What do the severe or warning messages in the portal logs say? ... View more

There may be some incorrect logic to determine when the hostname changes, so we're looking into that. What you can do though is: 1) Install the patch 2) Determine the IP address of the portal machine 3) In the etc\hosts file, resolve the short name of the machine to the IP address. This ensures that the Web Adaptor and everything else continues to work, because the short name will resolve to the same machine     10.0.0.1 portal #FQDN is portal.domain.com 4) Restart the portal service 5) Verify that the Machines API within the Portaladmin API returns the correct information, albeit with the short name 6) Remove the etc\hosts entry 7) Restart the portal service 8 ) Verify that the Machines API within the Portaladmin API returns the correct information, using the FQDN. You may need to unregister the standby first, as hostname changes should be blocked if the portal is HA. ... View more

Yes, a patch will be released for 10.8.1. This doesn't impact 10.7.1. If you see differently, please contact Support for them to investigate. ... View more

Does the Sharing API resolve, ex. https://portal.domain.com:7443/arcgis/sharing/rest? My assumption is it won't. Can you check the localhost logs under <install directory>\framework\runtime\tomcat\logs?   ... View more

No, it's not in 10.9 pre-release but will be in final ... View more

Yes, @HenryLindemann is correct; for a distributed deployment, (software on different machines), the SHARED_LOCATION needs to be a accessible by all machines, and the account running the software on each machine. For a single machine deployment, using a local path would work. Using a local path for the BACKUP_LOCATION would also work because it's only the DR tool that needs to write to the BACKUP_LOCATION path, (if it's on the file system, at least). ... View more