topic Re: "Specified method is not supported" error message in ArcGIS Explorer Online Questions

"Specified method is not supported" error message

Anonymous User — Mon, 25 Jul 2011 15:46:27 GMT

Original User: jhong14

When I tried to import a shapefile, I got the attached error message.
I thought the size of the file was too big, so I selected a few features, and exported to another shapefile.
The new shapefile was successfully imported.
However, when I checked the size, the new one was bigger.

What does the error message mean?
What do I have to do if I want to import the original shapefile?

Just in case, I also attached the original shapefile.

Thanks.

Jessie

Re: "Specified method is not supported" error message

Anonymous User — Tue, 26 Jul 2011 09:56:17 GMT

Original User: sgill

Hi - I'm afraid I'm not sure what's causing this failure, we'll let you know by posting back here when we know exactly what the issue is here.

When I tried to import a shapefile, I got the attached error message.
I thought the size of the file was too big

If your file size is too large, you will get a different error message, saying that files above 10MB are not supported, so it's definately not the overall file size.

Re: "Specified method is not supported" error message

mrmark — Tue, 23 Aug 2011 20:01:35 GMT

Exact same problem here. I exported various pieces of my shapefile out and some of them worked, some didn't. I've attached one that didn't. It is a single multipart polygon of Russia. It is from the Countries shapefile from ESRI with an added field to it. I've made no changes otherwise. Exporting the US and Canada works fine, I got up to North and South America and Africa before it started giving me the "Specified method is not supported" error.

Re: "Specified method is not supported" error message

Anonymous User — Wed, 24 Aug 2011 07:43:26 GMT

Original User: sgill

It is a single multipart polygon of Russia. It is from the Countries shapefile from ESRI with an added field to it.

Hi Mark - I've had exactly the same (same dataset, same feature) issue previously reported by a colleague, although I dont know what precisely about this feature causes the issue yet. I've referred this one to the appropriate people for fixing, and it's on the list to be addressed.