topic Re: FATAL ERROR (ICLOSE) in Python Questions

FATAL ERROR (ICLOSE)

AndrewHardy — Wed, 30 Mar 2011 08:26:03 GMT

Has anyone ever come across a python error looking like this...

FATAL ERROR (ICLOSE)
Attempting to close channel 2, which isn't open

I am extracting zonal stats as a table for multiple sets of two raster datasets. These tables are joined and the joined table is outputted as a csv. Numpy is then used to calculate the correlation coefficent which is then written to a text file.

It works fine for the first two set of files then comes up with the above error message. I found a link to a known error with ArcWorkstation (http://resources.arcgis.com/content/kbase?fa=articleShow&d=11798) but not sure whether it is relevant here

I am running ArcGIS 9.3 - code attached if interested.

Any thoughts?

Re: FATAL ERROR (ICLOSE)

DarrylKlassen — Fri, 18 Jan 2013 20:21:03 GMT

Has anyone resolved this issue? I am getting the same error message!

Thanks

Darryl Klassen
GIS Technician

Re: FATAL ERROR (ICLOSE)

DavidRheinheimer — Fri, 25 Jan 2013 03:35:16 GMT

For other GIS Googlers out there:
I just encountered and resolved this issue, so thought I'd post a reply. This issue also arose when I was using ZonalStatisticsAsTable() in python. Furthermore, I was also creating a SearchCursor from the new zonal stats table and working with the cursor. I was able to resolve the problem by properly deleting the cursor after each use (and there are several "proper" ways to delete a cursor--e.g., a simple "del cursor" works to resolve the problem).

I hope this helps!

David

Re: FATAL ERROR (ICLOSE)

RyanHill1 — Thu, 26 Sep 2013 18:19:09 GMT

I encountered this when working with Search and Insert cursors. I had a script which was working fine, all tables being accessed and written to within a File Geodatabase. I made some script changes, in which tables were now being written into a simple directory folder. Absent mindedly, I initially did not change table names explicitly with ".dbf" in the script, so within the folder they were written as default INFO tables, and the problem surfaced. I created a new FGDB in which to write the tables as default dBASE and the problem disappeared. As per the above response, properly deleting cursor resources is also probably important.

-Ryan