ArcGIS Error 000601 When Running Nutrient Removal Wetland Tool

[Drake, Chad W]

Hi,

 

I receive the following error when running the nutrient removal wetland tool. I am using ArcMap 10.5 and ACPF V2.2. The tool was working fine a couple days ago. I’m not sure what lock would be preventing this step from being completed.

 

Thanks

Chad Drake

[Porter, Sarah - ARS]

Hi Chad,

 

Do you happen (or did you happen) to have Arc Catalog open at the same time as trying to run the tool from Arcmap?

 

When I encounter data locks like this, closing Arcmap and Catalog, and clearing out the workspace (in your case – C:\\Users\cdrak\Documents\ArcGIS\Default.gdb) usually fixes the problem.  I often also go into task manager and close any ArcGIS processes that are still running after closing the program.

 

Let us know if that fixes the issue.

 

Thanks,

 

Sarah Porter

USDA/ARS National Laboratory for

      Agriculture and the Environment

1015 N. University Blvd.

Ames, Iowa 50011

(515) 294-2246

--
The ACPF Forum is an online group for discussing technical issues related to using the ACPF tools. Anyone can view the discussions at https://groups.google.com/a/umn.edu/d/forum/acpf-group. Only members can participate in discussions. Join the group by sending an email to acpf-group...@umn.edu
---
You received this message because you are subscribed to the Google Groups "ACPF Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to acpf-group+...@umn.edu.
To post to this group, send email to acpf-...@umn.edu.
Visit this group at https://groups.google.com/a/umn.edu/group/acpf-group/.

This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.

[klamke...@gmail.com]

The line that has the execution error where it can't delete the reach_file it indicates you are using one of the default .gdb's as a workspace.

So anyway here are my thoughts but I might be way off base...  That type of error message is common when a schema lock is in place on something, as in another program or instance of arcmap/arccatalog or whatever is using the file, or at least windows thinks something is using the file.  It's been my experience that schema locks do not always clear as they are supposed to even when the file isn't in use or if you have had a something that was using the file crash.  Restarting will typically reset all the locks.  Using the default workspace increases the chance of having something locked up and not being able to determine what's locking it.

I think setting up a .gdb to serve as the workspace solely for the ACPF run you are working on and avoid having that .gdb open or viewable in multiple programs or multiple instances of the same program will help avoid this in the future.

That's all I got, hopefully it helps.

[Drake, Chad W]

Thank you both (once again) for the help. Yes, I did have Arc Catalog open at the same time as trying to run the tool from ArcMap. Following your instructions – closing ArcMap and Arc Catalog, and clearing out the default workspace – fixed the problem. The wetland tool worked successfully after that.

 

I know you recommend setting the current and scratch workspaces to local file locations (described in the ACPF user manual). Do you normally change the default settings (something similar to shown below) for the particular ACPF project you’re working on, or just clear the default workspace periodically? If you do change from the default location, do you normally set both the current and scratch workspaces to the HUC 12 .gdb location (e.g. acpf<HUC12number>.gdb)?

 

Thanks again for the constructive feedback.

Chad  

 

[klamke...@gmail.com]

I have to project our lidar from Albers to UTM so I just set up a working .gdb for the run at that time and dump the hydro-enforced lidar in there.  I would set the workspace to that .gdb, but not necessarily the scratch but there isn't any reason you couldn't.