Workflow - Query Task Fail {IP Restrictions with ReverseProxy}
Latitude or other,
I have a server with two websites and two different Geocortex instances running. We are implementing the ESRI Reverse Proxy for IIS; http://support.esri.com/en/knowledgebase/techarticles/detail/35894. Our default website is currently pointed to an ArcGIS Server instance on the same box but our second site is using an internal AGS through the Reverse Proxy. In my Geocortex site that uses the Reverse Proxy, everything works as exepcected until I apply IP Restrictions. Once the IP restrictions are applied the workflows no longer work. With the IP restrictions using the Reverse Proxy service, I can see the map, identify, query and print but the workflow fails.
The workflow fails on the QueryTask with the error message "The remote server returned an error: (403) Forbidden". The workflow also uses an "Auto Complete Box" in a form to produce a list of Parcel Numbers, that "Auto Complete Box" is using the same service that is used in the QueryTask, the list comes back without issue.
Fiddler does not report much about what is going on behind the scenes. Nothing to report from the client side, I believe that is because the communication during the execution of the QueryTask is all being done on the web server in .NET code.
From Fiddler: {"instanceId":"ffc8c4e0-d531-4b8c-8175-3f1022035e1f","status":"WaitingForExternalActivities","pendingExternalActivities":[{"id":"1.71","instanceId":"18738134-5363-4d9e-90f0-a213769ae9d1","displayName":"Alert","typeName":"Geocortex.Workflow.Activities.Alert","externalId":"","syncToken":"","isComplete":false,"inputs":[{"isRequired":false,"name":"Text","typeName":"System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","runtimeTypeName":"System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","value":"The remote server returned an error: (403) Forbidden."},{"isRequired":false..... ETC....
So the black box is the QueryTask, what is happening in there during the WorkFlow that is being blocked? The 403 error encompasses many aspects including "IP address rejected", my current suspect. http://en.wikipedia.org/wiki/HTTP_403
Anyone, have any ideas how to fix this or what is going on?
Louie Rowley
INFO SYSTEMS SPECIALIST II
lewis.rowley@countyofnapa.org
-
Hi Louie,
You are saying that the Autocomplete in the form is working but not the query task activity in the workflow? First thing that comes to mind is that the autocomplete is being run from the client application and the query task is a server activity (so the requests come from the Essentials server). I'm not too familiar with the reverse proxy stuff, but make sure the IP of the server running Essentials is authorized.
Cheers,
Christian.
0 -
Yes the Autocomplete is working. Right away I suspected the server side communication thus I added the server IP and the localhost IP but that did not work. What other IP could it possibly be?
Louie
0 -
Please confirm that you can access the query task URL when you are logged on to the server (using a web browser on the server).
Hope this helps,
Christian.
0 -
Christian,
The same url is used for the Autocomplete, that url works on the server. Anyway, it occurred to me that I could probably see the blocked IP in the IIS logs and lucky me I found the firewall IP was being restricted according to the logs. Apparently in the case of requests being made such as QueryTask, BufferTask, probably any AGS requests the client somehow becomes the Firewall. Strange but solved by adding the Firewall IP to my allow list.Louie
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare