idea Error 160090 too confusing; needs better explanation in ArcGIS Pro Ideas

Error 160090 too confusing; needs better explanation

Craig_Eissler_Iceman — Fri, 14 Jul 2023 19:04:15 GMT

The current Error 160090 Description reads: "A persisted domain record with the specified name does not exist".

But what does that mean? I ask all kinds of people, including Esri Support, and no one really seems to know. ...And, besides, what does a domain have to do with an invalid join issue which is described here.

Cause: The Error is caused by adding a join to an existing join, where the Input Table was the Join Table in the existing join.

Solution: Use the same Input Table as the existing Input Table or start a new Add Join with a different Input Table.

I suggest the Error/Help page be re-written OR create anew Error code for this particular Invalid Join issue, perhaps with the wording similar to above.

Thanks!

Re: Error 160090 too confusing; needs better explanation

JonathanNeal — Fri, 14 Jul 2023 19:02:52 GMT

@Craig_Eissler_Iceman Yeah super confusing. Looking into it now.

Detials if needed:
Reviewed the error message and it is only used in 1 location in the code (Could be multiple ways to get to that code, but will assess it in detail shortly). The best way for doc feedback is to use the link on the bottom of our doc topic link because it routes it more effectively to me. But, either way still glad for the feedback so it can be improved. Messages without actionable ways to get users working again are bugs.

160090: A persisted domain record with the specified name does not exist.—ArcGIS Pro | Documentation

Re: Error 160090 too confusing; needs better explanation

SamanthaEarnest1 — Fri, 12 Apr 2024 15:51:47 GMT

Thank you for posting this. I had a student send me a screenshot of this error, and I came here to figure out what was going on. I agree that the text should be more clear about what the problem was.

Re: Error 160090 too confusing; needs better explanation

nadja — Wed, 14 Jan 2026 15:00:45 GMT

it seems linked to this post: https://community.esri.com/t5/arcgis-pro-questions/don-t-fully-understand-error-160090-quot-a/m-p/1305094

the solutions proposed in the link provided by @JonathanNeal are no option for my case... I'm still looking for a working workaround.

Re: Error 160090 too confusing; needs better explanation

JonathanNeal — Wed, 14 Jan 2026 16:57:47 GMT

@nadja Just for status:
The 16XXXX errors are usually confusing because they come from the database. We typically intercept them when running a tool and transform them into something actionable. I have it in the queue for us to address remapping it for the Join tools.

Do you know what your case is?
Tool used, Data types used.

I can look into it and get back with details. The 16XXXX errors to us are similar to Error 999999, we don't like them and want to re-route them to a more informative, actionable message.