This content has been marked as final. Show 4 replies
I've seen something similar once previously but with an async GP service instead of a query task. I don't currently have a fix or a good work around.
Is there a public URL for your service?
No it's not a public service... maybe I'll try and get it through the firewall and repost the question.
This looks like it's NIM086349 which was introduced with service pack 1 for ArcGIS Server 10.1. Can you open a call with support and request to be added to this bug?
I hit the same issue and I found this thread,
the request is like:
I am using this work around:
because queryTask.execute() accept the third parameter as err handling function, I insert the function to call queryTask.execute() again in it and it works almost all the time.
Any other ideas?