Create Utility Network fails at 2.6

MarkCederholm

After upgrading Pro from 2.5.2 to 2.6, Create Utility Network fails with the following error:

ERROR 003049: The account logged into portal is not licensed with the Utility Network Service user type extension.
Failed to execute (CreateUtilityNetwork).

After reverting back to 2.5.2, it works again.  ArcGIS Enterprise is at 10.7.1.  After looking at the documentation, it appears that Pro 2.6 requires Enterprise 10.8 in order to manage utility networks.  Is that the case?  Or is there a way to get it to work with 10.7.1?

LarryYoung

Following up more on this ...

Please see the help here:  Utility network dataset administration—ArcGIS Pro | Documentation 

We try hard not to increment the version of the utility network, but the gist of this documentation is that ArcGIS Enterprise 10.8.1 is required to create new networks with Pro 2.6 due to an upgrade of the utility network.  At this stage of the development of the utility network it is sometimes necessary to increment the version of the network.  With this release we had a significant change with the addition of nonspatial object tables (edge and junction objects) to the model.  ArcGIS Enterprise versions prior to 10.8.1 have no knowledge of these changes and therefore cannot support the current version (version 4) of the network.  You can still use Pro 2.6 to work with existing networks in earlier versions of ArcGIS Enterprise, but you will need to move forward to 10.8.1 in order to create a new network with Pro 2.6.  You can still create new networks with earlier versions of ArcGIS Enterprise by using earlier versions of Pro as you did.  Once created, Pro 2.6 can be used to maintain the network.

The logic here is to maintain consistency with file geodatabase versions of the utility network.  If you use Pro 2.6 to create a new utility network in a file geodatabase it will be a version 4 network supporting nonspatial objects.  In order to support the same with multi-user geodatabases, ArcGIS Enterprise 10.8.1 is required.

What we do need to do is update the error/warning message because you should not have been told there was a licensing issue.