Troubleshooting

Unable to Load a Viewer Hosted Behind a Firewall

Problem:

Attempting to load a viewer hosted behind a firewall via an external URL results in an error similar to:

There was an error with your request. The viewer could not be opened/downloaded. Not online (cannot reach host 'ServerName').

Actions to Take:

If you can connect to your internal network via a Virtual Private Network (VPN), do so before loading the viewer.
If you cannot connect to your internal network via VPN, but have configured external URLs for Essentials and the HTML5 Viewer, do the following:
1. On the Essentials server, run a text editor as an administrator.
2. Open the Templates.xml file. By default, this file is located at:
  
  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\Templates\Templates.xml
3. Find the <ViewerFramework> element, and edit its Url attribute:
```
<ViewerFramework ProductID="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" TemplateID="Html5Viewer_2_X" Url="http://MyServer.com/Html5Viewer" PhysicalLocation="C:\inetpub\wwwroot\Html5Viewer" RequiresUpgrade="false" />
```
  Set the value of the Url attribute to the external URL of your HTML5 Viewer. For example, http://MyServer.com/Html5Viewer.
4. Save the file.
5. Open the RestManagerSettings.xml file. By default, this file is located at:
  
  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Manager\App_Data\RestManagerSettings.xml
6. Find the <ViewerFramework> element, and edit its Url attribute:
```
<ViewerFramework ProductID="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" TemplateID="Html5Viewer_2_X" Url="http://MyServer.com/Html5Viewer" />
```
  Set the value of the Url attribute to the external URL of your HTML5 Viewer. For example, http://MyServer.com/Html5Viewer.
7. Save the file.
8. Open the Web.config file. By default, this file is located at:
  
  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Manager\Web.config
9. Find the following element, and edit its value attribute:
```
<add key="EssentialsUrl" value="http://MyServer.com/Geocortex/Essentials/REST/sites" />
```
  Set the value of the value attribute to the external URL of your Essentials Sites folder. For example, http://MyServer.com/Geocortex/Essentials/REST/sites.
10. Save the file.

Unable to Run Workflows on a Windows-Authenticated Essentials Server

Problem:

Attempting to run an Essentials Workflow workflow on an Essentials server secured by Windows Authentication results in an HTTP 403 error similar to the following:

The current user cannot access the desired resource.

This error occurs due to the proxy page not being properly configured to forward the necessary authentication information to the Essentials server.

Actions to Take:

Follow all of the instructions in Adapt the ASP.NET Proxy Page to Access Windows-Secured Servers. In particular, ensure you enable Windows Authentication in IIS, and add the Essentials server to the proxy.config file and set its useAppPoolIdentity attribute to true.

Unable to Use Geolocation in Windows 10

Problem:

Attempting to use the geolocation feature in Windows 10 results in an error similar to:

Geolocation command returned no results.

This error usually occurs because the Windows 10 computer has a group policy enabled that turns off location.

Actions to Take:

Sign into the Windows device with an Administrator account.
Click Start, type gpedit.msc and press Enter.

The Local Group Policy Editor appears.
Navigate to Computer Configuration > Administrative Templates > Windows Components > Location and Sensors.
Double-click Turn off location.

The Turn off location window appears.
Ensure the Enabled radio button is not selected, and click OK.
Navigate to User Configuration > Administrative Templates > Windows Components > Location and Sensors.
Double-click Turn off location.

The Turn off location window appears.
Ensure the Enabled radio button is not selected, and click OK.