Latest Contributions by BenO_Connor

Great! I've run those steps and they are all showing the validation was successful for both the components. I'll run some publishing tasks to ensure that is all working correctly also. Thanks Thomas! ... View more

Hi Michael, Yeah, as Jonathan Quinn‌ suggested I had configured the certificate in IIS myself. I'm not sure if the below is the best way, but this is the process I followed to make a Windows Server 2016 machine ready for Enterprise Builder: 1) Enabling IIS and required components: https://enterprise.arcgis.com/en/web-adaptor/latest/install/iis/enable-iis-2016-components-server.htm 2) Asking our IT department to issue a certificate signed by our internal domain CA, for the target machine ArcGIS Enterprise was to be installed to. (they supplied a password protected .pfx format certificate) 3) Adding that certificate to the target machine's certificate store. (There was an "Import" option in IIS Manager > [MachineName] > Server Certificates, but I could have just double clicked the .pfx and followed the wizard) 4) Identified the "Default Web Site" in IIS Manager (this was the only website listed in my IIS so I assumed Enterprise Builder would automatically choose it). 5) Added a binding so that "Default Web Site" listens for HTTPS traffic on port 443 and uses the certificate I had just imported. I effectively followed ESRI's instructions in the Bind the certificate to the website from here: https://enterprise.arcgis.com/en/web-adaptor/latest/install/iis/enable-https-on-your-web-server-server-.htm I had completed those steps before doing the Enterprise Builder installation. But I would guess it could be done at a later stage. Maybe someone else could comment on that. ... View more

Hi Jonathan, Super! That clears it up for me. We'll most likely replace the self-signed certificates with the domain CA ones. Kind regards, Ben ... View more

Hi Thomas, Thank you for your reply. It looks like the log files in that folder stop being used at an earlier point in the installation process. However, when I logged into the machine to look at the log files, the configuration process had actually finished. But it appears to have taken nearly 24 hours for the "Register Data Stores with GIS Server" step to complete. As it completed just after midnight, I was thinking that maybe the cycling of an internal ArcGIS Server component had jump started the configuration? As this installation time sounds out of the ordinary, I was wondering if there are any options to perform a health check on the installation? Kind regards, Ben ... View more

Hi all, I have had similar issues to what I see described in the previous posts and I believe it may be a bug which is triggered the first time you output to UTM using the "Convert file(s)..." feature. When subsequent batch conversions are performed the Grid InQuest software appears to remember the previous output coordinate setting being UTM and uses this over the output coordinate system manually chosen. I've found that deleting a few registry keys can fix this issue. In Registry Editor (Start > Run > regedit.exe) navigate to HKEY_CURRENT_USER\Software\Quest\. When I have had this issue I have deleted the entire contents under the Quest key, however it is likely that deleting the values "Destination Format", "Destination Zone", "Format", "Source Format" and "Source Zone" under HKEY_CURRENT_USER\Software\Quest\GridInQuest\Preferences\ will be sufficient. Hope this helps! Ben ... View more