WebViewer 403 Error

Andrew Adamson

March 26, 2020 18:52

On our on premises install of Geocortex Web 5.3.0 we are getting a 403 - Forbidden: Access is denied. error when we load out the WebViewer link to preview our apps. Designer runs fine but anything related to the /WebViewer url throws 403 errors.

 

Can't seem to find any information on this error from other posts.

0

• 

  Pairin Mason

  March 26, 2020 19:08

  Hi Andrew,

   

  How do your IIS settings for WebViewer look like? Is it just default setting?

   

  

   

  Cheers,

  Pairin

  0
• 

  Andrew Adamson

  March 26, 2020 19:20

  Web was initially installed with /Geocortex/WebViewer as the default virtual directory. When I found that /Geocortex/WebViewer was throwing 403 errors I looked into the docs more and found that we should not be using this virtual directory if essentials is installed - Essentials is installed on this machine.

   

  After that I changed the virtual directory to /gcx/WebViewer in post install but 403 error still persists.

   

  0
• 

  Pairin Mason

  March 26, 2020 21:32

  Did you install GXW in non default directory by any chance?

  (Default directory would be C:\Program Files\Latitude Geographics\Geocortex Web Viewer)

   

  Cheers,

  Pairin

   

   

  0
• 

  Andrew Adamson

  March 26, 2020 21:36

  We installed GXW in a non default directory - D:\Program Files\Latitude Geographics\Geocortex Web Viewer

  0
• 

  Pairin Mason

  March 26, 2020 21:46

  Our guess would be that your non default folder doesn't have a proper permission set.

  Would you mind to try giving permissions to the IIS_IUSRS account to the folder where GXW is installed to see if that helps?

  0
• 

  Andrew Adamson

  March 27, 2020 12:04

  I gave IIS_IUSRS full control on the D:\Program Files\Latitude Geographics\Geocortex Web Viewer folder but the 403 error still comes up when I try to navigate to a launch URL

  0
• 

  Pairin Mason

  March 31, 2020 01:00

  That's very odd.

  It likely uses Identity (AppPoolIdentity in IIS). In some cases, some might change it to a user who is not a member of IIS_IUSRS, which would mean the permissions would need to be added for that user either by name, or based on group they belong to.

   

  If you have a custom authentication in place that might try to perform additional validation of the request, and cause it to fail as well.

   

  Please don't hesitate to file a support ticket, so we can take a closer look at the issue.

   

  Kind Regards,

  Pairin

   

   

  0

Please sign in to leave a comment.