Select to view content in your preferred language

[RPC Fault faultString="Servlet execution threw an exception" faultCode="500"...

7528
18
03-15-2011 05:25 AM
AshleyOwens
Emerging Contributor
I added a 2nd combobox to my search widget. When the 1st combobox has a selection, the code should populate the 2nd combobox. I am getting the following error in function onFault:

[RPC Fault faultString="Servlet execution threw an exception" faultCode="500" faultDetail=""]

Attached is the xml and mxml. In the mxml, making a selection in the 1st combobox (???Search Layer???) calls function searchLayerChangedText(). That calls function querySearchFeatures(), which is the function where the error is being thrown.
Tags (2)
0 Kudos
18 Replies
RobertScheitlin__GISP
MVP Emeritus
Ashley,

   To be able to query a layer in a map service it will allways have to have the Shape and ObjectID fields visible as REST needs these to perform the query. You do not have to return these fields in your query though.

The rule of thumb is always use the name of the service or just copy the url path from the address bar in the services directory.
0 Kudos
AshleyOwens
Emerging Contributor
As far as SHAPE & OBJECTID, we are currently showing details about this layer so these fields must already be visible.

How can I change the "land" service in Dev to be "Land" so it matches Production? I would like to keep the config XML file as it is now.

Do you have any recommendations to resolve error "Unable to perform query. Please check your parameters" (I see this when I change the URL to "Land").

Thank you so much for all your responses today! I appreciate the help!
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Ashley,

As far as SHAPE & OBJECTID, we are currently showing details about this layer so these fields must already be visible.
So does this mean that you physically opened the MXD that this map service is pointing to and opened the attribute table for that particular layer (land) and verified that the shape and objectid field are visible in the table?

As far as making sure that the development server and the production server are using the same name for the land layer look at the mxd that each server is pointing to and ensure that land is spelled using the same case in each of those mxds.

Is your production server publicly visible?
0 Kudos
AshleyOwens
Emerging Contributor
Yes, I viewed the attribute table for that mxd and could see OBJECTID & SHAPE listed.

I tested again and am getting COUNTY information back! 

Thank you so much!
0 Kudos
AshleyOwens
Emerging Contributor
When I go to the URL you provided, I get COUNTY information back like I said. But when I run through my app, I still get "Servlet execution threw an exception". Can I get the URL the app is creating for this query to compare? Otherwise, the error is vague and it's hard to troubleshoot...
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Ashley,

   If you install free HTTP utilities like Fiddler or Charles you can see the HTTP traffic that is going back and forth from the server and the client.
0 Kudos
AshleyOwens
Emerging Contributor
Thanks Robert. I can see the URL now and compared it to the one that works. When I changed query.returnGeometry = false; it worked through the app!

Thanks again for your help Robert!  I appreciate your patience with a beginner!
0 Kudos
AshleyOwens
Emerging Contributor
I am having this problem again. In our test environment that we just upgraded to ArcGIS Server 10, we see error [RPC Fault faultString="Unable to perform query. Please check your parameters" faultCode="500" faultDetail=""] when attempting to access certain layers using Identify or Search widgets.
When I change the xml files to point to our production environment (v9.3), it works.
I went to the REST service in a browser and was able to query on the layers that give an error in the widgets.
How can I further troubleshoot this issue? Could it have to do with the ArcGIS Server upgrade?
0 Kudos
AshleyOwens
Emerging Contributor
I think I figured this out. If there are fields listed in the widget XML that are not in the corresponding database table, this error will be returned. This was not an issue before, so I'm assuming it's a change with ArcGIS Server version 10.
0 Kudos