nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

eSearch:

MichaelMiller2

I have two file geodatabases(FGDB): one a copy of the other with an additional year of feature classes. I've been using the original one for services used in eSearch widget with great success. I copied the original FGDB and added an additional years of feature classes. Any eSearch services hitting the new FGDB return "[RPC Fault faultString="Failed to execute query." faultCode="400" faultDetail=""]". Any ideas on why a service using the same year from two different FGDB's works in one and not the other?

Find more posts tagged with

Accepted answers

AntGiles

A 400 error normally occurs if your query is trying to return a field that does not exist, check the fields in your config match those in your rest endpoint (check field name spellings). Remember REST is also case sensitive.

All comments

JenniferWhiteis

This solved my problem. Thanks!

MichaelMiller2

Thanks Anthony!

Yes, I just discovered that a field name had changed and was being referenced by the old name in the eSearch config xml file. Once I updated the config file, all was well.

Thanks again.

AntGiles

RhettZufelt

Not sure, but a good place to start would be to open the mxd's that the services are based on and make sure they open and bring in the data correctly. Might give you an idea of where it is broken.

If not, might try to re-publish the service after re-sourcing to the copy of the data.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.