topic Re: Tool Cost Distance - Error 010005 and 010067 in ArcGIS Spatial Analyst Questions

Tool Cost Distance - Error 010005 and 010067

MatthiasWoerner — Thu, 29 Mar 2012 18:49:15 GMT

Dear all,

I use ArcGIS 10.0 and faced this problem when executing the tool Cost Distance: I get back the Error 010005 and 010067.

Already posted comments on Error 010005 suggest that there is not enough RAM available. I don't consider this to be the problem on my computer. As well the used datasets are rather small. I tried running the tool with ArcCatalog closed and as well all other software closed except for ArcMap - but with the same error message.

Did anybody face the same problem or has a good idea how to solve this?

Many thanks in advance,
Matt

Re: Tool Cost Distance - Error 010005 and 010067

TarunJaiswal — Thu, 29 Mar 2012 18:57:00 GMT

Greetings!

Please try setting a scratch workspace and run the tool. Also, you may want to clean temp directory and to consider repathing it closer to root such as c:\temp.

Hope this helps.

Thank you.

Re: Tool Cost Distance - Error 010005 and 010067

MatthiasWoerner — Thu, 29 Mar 2012 19:34:53 GMT

Greetings!

Please try setting a scratch workspace and run the tool. Also, you may want to clean temp directory and to consider repathing it closer to root such as c:\temp.

Hope this helps.

Thank you.

Dear Tarun,

Thanks for your suggestions. I moved the geodatabase to a path close to directory c:\temp and ran the tool with an adequate scratch workspace. But with the same result. In fact my directory c:\temp is almost empty so this should not be the problem.

Still thankful for any suggestions,
Matt

Re: Tool Cost Distance - Error 010005 and 010067

DanPatterson_Retired — Thu, 29 Mar 2012 20:45:41 GMT

try running it with an ESRI grid in a folder and not a geodatabase

Re: Tool Cost Distance - Error 010005 and 010067

MatthiasWoerner — Fri, 30 Mar 2012 21:03:49 GMT

Dear Tarun and Dan,

Thanks a lot for your suggestions. I followed these and some other ideas in order to solve the problem. In the end it was a little stupid mistake I made. I didn't enter the Extent values in the Geoprocessing Environments. After catching up this the tool ran without objection.

Thanks anyway,
Matt