Latest Contributions by JonathanQuinn

Echoing Randall Williams‌ and George Thompson‌, latency problems can be tricky to troubleshoot outside of your IT staff. I've found that IoZone is a useful tool that you can use to take ArcGIS Server out of the picture. It simulates read/write operations against a directory and measures the throughput in kb/second. You can run it against your network share and then your local directory to at least give you an idea of what your network share throughput needs to be at to perform as well as your local directory: On the ArcGIS Server machine, install the following software:   IOZone (http://www.iozone.org/src/current/IozoneSetup.exe) cygwin (http://cygwin.com/setup-x86_64.exe)   *Note, there have been issues running IOZone with paths to the network from the machine the folder is shared to, meaning running IOZone from m1 to a share like \\m1\<path>   Sign in to the Server machine as the ArcGIS Server account and run the following command from the command line: "C:\Program Files (x86)\Benchmarks\Iozone3_414\iozone.exe" -Ra -f //networkpath/folder/file -b %USERPROFILE%\Desktop\networktest.xls * Ideally, the //networkpath/file parameter would be set to the share to your server directories, for example   //<machine>/arcgisserver/directories/file.  In this directory, it'll create a simple file called "file" and run it's tests on that file.   Run the following command as well when you're logged in with the ArcGIS Server account on that machine: "C:\Program Files (x86)\Benchmarks\Iozone3_414\iozone.exe" -Ra -f C:\arcgisserver\directories\file -b %USERPROFILE%\Desktop\localtest.xls   The parameters listed above are defined below:   -R = generates an Excel file -a = uses full, automatic mode, meaning tests files with records sizes from 4k to 16M for file sizes 64K and 512M -f = sets file path for output -b = sets file path for Excel file.   If you're interested in knowing more about the tests that it will run, they can be read up on through the following pdf.   IoZone documentation: http://www.iozone.org/docs/IOzone_msword_98.pdf ... View more

Yes, they can be deleted as they only store snapshots of your data as backups. However, they appear to be created at a pretty high frequency so there's a deeper problem. They should only be created once during "failback", where the standby is returning from a failure, or during restores. Do you have a promote.dat file in the db directory on the primary? ... View more

I concur with Bill Fox‌, I'd go with Option 1. Option 3 is good if you want to validate whether your new environment is working prior to switching over, but requires knowledge of etc\hosts file changes and there's a risk of some data loss as people can still create content on your first environment while the second is restored/validated, before you switch over. ... View more

I suggest you take a look at the Server logs when panning/zooming around in the map service: Troubleshooting map service performance with server logs—Documentation | ArcGIS Enterprise  Map service log codes—ArcGIS Server Administration (Windows) | ArcGIS Enterprise  In the second link, search for the Example: ExportMapImage section that describes the different operations involved in generating the export map images. While there's no equivalent logging in Desktop, (aside from SDEINTERCEPTS), you can at least determine what operation(s) are taking the most time in the map service by checking the log entries. ... View more

Can you open https://xyz:6443/arcgis/rest/admin/ in your browser and see if the browser indicates the certificate is mismatched? The problem is likely that the CN, or common name, of the certificate is yyy but the URL you're accessing that is assigned the certificate is https://xyz:6443/arcgis/. This indicates a certificate mismatch would be the reason for the java.security.cert.CertificateException: No name matching xyz found error. ... View more

Open the dev tools or run Fiddler when loading the page for the slpk. A request is made from Portal to the Admin API to check whether the hosting server has a tile cache data store registered. If that request fails or doesn't return expected results, then the Publish button won't appear. ... View more

Are you using a wildcard certificate? Do you have the root certificate in .cer format? You can export the certificate from your browser and import it into Portal. There's no need to reinstall to fix this problem. ... View more

The Import Existing Server Certificate option is used if you want to use your own certificate for the 6443 and 7443 endpoints for Server and Portal. The Import Root or Intermediate operation is used to tell Portal to trust certificates. You don't need to remove anything, just import your certificate using the Import Root or Intermediate operation. If you want to use the same alias, you'll need to remove any existing certificates first. ... View more

There's more logic within the home application/My Organization page to ensure that you have a relational Data Store, which is the request from Portal to the Admin API to get the list of registered Data Stores. You're bypassing that logic by updating the federated Server manually, so it's not a bug. Did you import the certificate into Portaladmin through the Import Root or Intermediate Certificate operation? Configuring the portal to trust certificates from your certifying authority—Portal for ArcGIS (10.6) | ArcGIS Enterpri…  ... View more

Check the network requests when loading the My Organization page. If you see a request from Portal to the Admin API of Server through the Admin URL you used to federate failing with a 403 error, then the problem is that the Portal doesn't trust the certificate used for the Admin URL as Jeff Smith‌ mentioned. The Portal is attempting to determine if the Server has a registered relational Data Store and if that request fails, the option will be disabled. The Portal logs would also contain an error about a certification path not being trusted. If all requests return a 200, then you may have to look at the response of the request I mentioned above to check what's returned. ... View more

That's necessary for Python 3 to convert Unicode to strings. Python String encode() - Python Standard Library  ... View more

This isn't a general issue of being unable to import a certificate into the Portal, though. I tested this at 10.6.1 with ProcMon running as well and this is the command line arguments that are run: .\keytool  -importkeystore -noprompt -destalias wildcard -destkeystore "C:\Program Files\ArcGIS\Portal\etc\ssl\portal.ks" -deststorepass ********** -srckeystore C:\Users\********\AppData\Local\Temp\61bd17d1-bd5b-48d7-88ff-9bda9db631c7871289888969767251519029737619274\wildcard.pfx -srcstoretype PKCS12 -srcstorepass ******** -srcalias le-esriwebserversha256-59365631-8570-4756-b0f3-352b478cacbf -destkeypass ******** -deststoretype JKS -J-Duser.language=en  I suggest you contact Technical Support so they can take a look and determine why the path is constructed incorrectly. ... View more

You pointed out the two paths you have: A) Manually upgrade     1) Install Portal, Data Store, and the new web adaptors.     2) Upgrade Server     3) Federate, register the Data Store, set it as a hosting server    Using this approach you're stuck with upgrading manually, but you have more flexibility to configure paths and URLs as you need to, (paths can always be updated later). B) Use the AEB    1) Uninstall Server    2) Install/configure using the ArcGIS Enterprise Builder    2) Republish all services    The upgrade path is more straightforward, in that you can use the AEB to upgrade from then on. You'd be stuck with a single machine deployment, though. Ultimately, I think it's difficult for people to suggest which is the best way for you to upgrade. I guess I can argue that the AEB approach gives you an easier upgrade path moving forward and you can always break out of that pattern if you need to, (for example, if you want to expand to multi-machine sites). ... View more

If this was a certificate problem, then the Server could never be validated regardless if it was hosting or non-hosting. When I've seen the 502 error in Azure, it was because I hadn't mapped the internal DNS to the external URL correctly. I doubt that's the issue in your case as you can likely reach the services URL and admin URL you're using within the federation. The LB/ARR, (which is returning the 502), should be able to handle a JSON response that contains a failure. I don't see a reason why if the Data Store can't be validated, it would return a 502. If the Data Store can't be validated, (for example, when validating the hosted server in Portaladmin, when validating the relational Data Store in Manager or directly through the Admin API), an error should definitely be logged in the Server. ... View more