NIM044046 for ArcGIS for Desktop

Bug ID Number	NIM044046
Submitted	April 7, 2009
Last Modified	June 5, 2024
Applies to	ArcGIS for Desktop
Version found	9.3
Operating System	Windows OS
Operating System Version	2003
Status	Will Not Be Addressed

Additional Information

We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.

Workaround

For models, do not manually delete the output (especially intermediate data). Allow the application to handle the operation. Set a scratch workspace (it is best if the scratch workspace is a file geodatabase). It can be a folder (so that the intermediate feature classes are shapefiles); however, it is recommended to use file geodatabase (FDGB) scratch workspaces. If the model is run as a model tool, the application deletes the intermediate data. If the model is run from the model editor, run "delete intermediate data" before subsequent runs (only for shapefile intermediate data. This is not necessary if the intermediate data or scratch workspace is FDGB.) Another option is to not manually delete intermediate data at the end, but instead use the in_memory workspace for intermediate data output. See the help for more info. The syntax for specifying the output is: in_memory\my_output_feature_class. By doing this, "delete intermediate data" does not need to be specified from the model editor. For script tools, again do not manually delete the intermediate data. Shapefile scratch workspaces still generate the file locking errors. So for intermediate data, use a FGDB, FGDB scratch workspace, or in_memory workspace. If intermediate data or other output created from the script or model must be manually deleted, use FGDB. The input can still be a shapefile, but what is being deleted must be FGDB.