topic Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1 in ArcGIS Utility Network Questions

Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Thu, 12 Jun 2025 18:14:17 GMT

We have created a UN v6 using Pro 3.3.5 and then extending the latest Esri foundational data model. We are now attempting to publish that to an Enterprise 11.1 environment. However, we get a "Domain code is invalid error" regarding the BIGINTEGER domain value defined within the AP_Attribute_Types domain, which is applied to the "attribute_type" field of the B_NetworkAttribute table. However, we've confirmed the value is not actually being used by any records. Attempting to remove the value renders all feature classes unreadable. We've confirmed our asset package is UN v6 and all objectIDs are 32-bit.

I'm interested to hear your thoughts.

Thanks,
Mike

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

RobertKrisher — Thu, 12 Jun 2025 18:29:53 GMT

Which utility network foundation are you using?

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Thu, 12 Jun 2025 18:36:53 GMT

Hey Robert,
We started with the Sewer Expanded which we downloaded in January.

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

RobertKrisher — Thu, 12 Jun 2025 18:49:06 GMT

After reading your question more closely, please post a screenshot of exactly where you are seeing this error. If you are publishing a deployed utility network to ArcGIS Enterprise it should not contain that table, domain, or coded value.

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Thu, 12 Jun 2025 19:12:23 GMT

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

RobertKrisher — Thu, 12 Jun 2025 19:59:44 GMT

The image says it's still virus scanning (50 minutes later). Maybe try embedding it directly in your post?

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Thu, 12 Jun 2025 20:12:51 GMT

let's try this...

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MikeMillerGIS — Thu, 12 Jun 2025 21:10:48 GMT

That is not publishing, that is trying to create a new UN File/Mobile Geodatabase with 3.1 ArcGIS Pro. The asset package scheme is a 3.3 schema. Our foundation solutions only support 3.3 and 3.5.

You need to create the UN gdb with 3.3 or greater, then use copy and paste to your enterprise GDB.

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Thu, 12 Jun 2025 21:23:45 GMT

That screen shot was from a subsequent troubleshooting step.

We have a hard requirement for Enterprise 11.1. Is there an alternative approach for applying the solution schema to a UN v6 without rebuilding the desired asset groups/types from scratch? I seem to recall you mentioning in the past that the solution schemas could be applied/downgraded to earlier versions, but I don't recall the steps. Or I mistaken?

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MikeMillerGIS — Fri, 13 Jun 2025 09:47:37 GMT

Have you tried using ArcGIS Pro 3.3 to publish to 11.1 enterprise? That domain with the big int is only an asset package domain, once you have a UN, it might be compatible with 11.1(lots of other variables, attribute rules, etc).

You can use 3.3 to create the UN and then use 3.1 after that too.

Re: Error with BIGINTEGER domain value at UN v6 and Enterprise 11.1

MichaelParma — Fri, 13 Jun 2025 12:04:11 GMT

Ok, that's good to know. Perhaps the BIGINTEGER error is a red herring for something else happening. Yes, we initially tried to deploy to Enterprise 11.1 with Pro 3.3. We were able to stage a UN and then attempted to Apply Asset Package. At that time we received the message: Error 160250: Objects in this class cannot be updated outside an edit session. Failed to execute (Append).

Various troubleshooting steps led us first a "Dataset version is later than is supported by your server" message, that main.SewerJunction shows a minimum client version 13.2, and eventually the BIGINTEGER error message.

Unless there's a different path we missed, our tentative plan is to start with a fresh UN created from 3.1 and apply/recreate our modified schema from 3.3.