topic Re: Error 160326 when running ModelBuilder in ArcGIS Pro Questions

Error 160326 when running ModelBuilder

MaraDoesArcGIS — Sun, 22 Mar 2026 16:56:56 GMT

Hello everybody,

I have a problem when running my Model. It begins with "Iterate Feature Classes" which is connected to "Extract Multi Values to Points". The output is then connected to a variety of other tools etc. When running it in the Edit mode, there is no problem whatsoever.

However, in the normal Run mode (when I klick open and not edit), it always stops immediatly and tells me Error 160326 The table already exists. I have restarted ArcGIS Pro multiple times, have deleted everything that might be the problem (including everything in the Scratch GDB).

There is no other file anywhere with the same name, I even tried renaming the feature classes, made new GDBs and folders, it still happens. I really don't know what to do anymore, is this a common problem? Or is there somehing I have overlooked?

Thank you so much for any information!

Re: Error 160326 when running ModelBuilder

DanPatterson — Sun, 22 Mar 2026 17:47:49 GMT

160326: The table already exists.—ArcGIS Pro | Documentation

ensure that the conditions that exist that cause the error are not present

(eg editing the input(s) or improper filename)

Re: Error 160326 when running ModelBuilder

MaraDoesArcGIS — Tue, 24 Mar 2026 19:42:05 GMT

Yeah I did that too. Just opened a completely new project with new GDBs, new feature classes, all with new and very simple names, it still fails. Either I am overlooking something or it is not because I did something wrong...

But thank you anyways!

Re: Error 160326 when running ModelBuilder

DanPatterson — Tue, 24 Mar 2026 22:03:19 GMT

Tech support would be your best bet so they can test with your model and data. There is nothing on the publicly facing support site regarding the error and extract multivalues to points.

You do mention that the output feeds into other tools. If you truncate the post extraction portion of the model, it would help isolate where the model is actually failing. Alternately, you might try incorporting a test on the possible output file actually existing and deleting it prior to other steps

If-then-else branching and logical tools—ArcGIS Pro | Documentation (ie If Data Exists ... or similar)