In certain scenarios, file locking errors are incorrectly generated when shapefiles are created and deleted within the same model or script.
上次发布: December 18, 2015ArcGIS for Desktop
漏洞 ID 编号
NIM044046
已提交
April 7, 2009
上次修改时间
June 5, 2024
适用范围
ArcGIS for Desktop
找到的版本
9.3
操作系统
Windows OS
操作系统版本
2003
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
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.
解决办法
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.