Select to view content in your preferred language

Receiving 500 Interal Error on REST GET with Wildcards

2811
3
01-10-2013 01:36 PM
MeleKoneya
Frequent Contributor
We have ArcGIS Server 10.1 installed and are using the Web Adaptor.     Our server is on our internal network and is using reverse-proxy to serve maps to the Internet.

When a query is performed using a GET that has a Where clause such as

Addr Like '%3%'    

http://MyServer/arcgis/rest/services/MyService/MapServer/1/query?where=Addr+Like+%27%253%25%27&f=pjs...

the query returns results,  but if the Where clause is:

Addr Like '%36%'

http://MyServer/arcgis/rest/services/MyService/MapServer/1/query?where=Addr+Like+%27%2536%25%27&f=pj...

A 500 Internal Server Error is produced.     I suspect a filter setting in IIS is stopping the Query, but don't know where to look.    Has anyone encountered this same issue?  

If so,  how did you resolve it?
Tags (2)
0 Kudos
3 Replies
RichardWatson
Deactivated User
Sounds like "request filtering".

What did you find?
0 Kudos
nicogis
MVP Alum
Have you set reverse proxy on iis ARR? http://support.esri.com/en/knowledgebase/techarticles/detail/40680

Have you further details in log iis?
Have you installed sp1?
0 Kudos
MeleKoneya
Frequent Contributor
I am running SP1 on our ArcGIS 10.1 installation.     I have not looked into the IIS ARR article suggested by Domenico.    I will take a look.    I did not see anything in the logs that helped.

Since I posted this to the forum,   I contacted ESRI Support and they are suggesting it is a Firewall issue and had us try the following:

Here is the Microsoft Knowledge base article about the error that is being received from the web server. Please review the link below:

http://support.microsoft.com/kb/837865

Specifically, try to implement the following steps:

To work around this issue, configure the Web publishing rule so that it does not block high-bit characters. To do this, follow these steps:
1. Start the ISA server or Microsoft Forefront Threat Management Gateway, Medium Business Edition Management tool.
2. Expand ServerName, where ServerName is the name of your ISA server or Microsoft Forefront Threat Management Gateway, Medium Business Edition computer.
3. Click Firewall Policy, click the Web publishing rule that you created to publish the Exchange server computer for access by OWA users, and then click Edit Selected Rule.
4. Click the Traffic tab, click Filtering, and then click Configure HTTP.
5. Click to clear the Block high-bit characters check box, and then click OK two times.
6. Click Apply to update the firewall policy, and then click OK.

I do not have direct access to the ISA server,  but have been told this setting is applied to our site and we still have the same issue.    

We will have to work with our ISA administrator to see if there is any other settings that we can change.

Mele
0 Kudos