Getting ERROR 003320 when staging the UN

[PhilDunn]

We just updated to UN v5 and have hit a brick wall.  Here is what we did:

Update Pro to v2.7.2

Upgrade Enterprise to 10.9

Upgraded the EGDB

Undated untools in Pro to v2.7

When trying to stage the UN, we get this error.  Doesn't make sense, since we did all of the upgrades.  And we had v10.8 in the first place, so anything below v10.7 wasn't even a factor.

ERROR 003320: The connected portal's federated servers do not meet the minimum supported release for the Utility Network - 10.7

[ColinWerle1]

Hi @PhilDunn ,

It could be helpful to run Fiddler trace while the Stage Utility Network tool is being executed. You may be able to see how the portal account is being referenced and perhaps what kind of requests to the enterprise deployment are failing. 
https://community.esri.com/t5/esri-technical-support-blog/monitoring-web-service-requests-using-fidd...

Also, using the DEBUG log level for untools is helpful in these situations as well.
https://support.esri.com/en/technical-article/000024444

Thanks,
Colin

[PhilDunn · Accepted solution]

Thanks Colin.  We did figure out the problem this morning.  After the upgrade, for some reason the web adapter was set to the server Url versus the web adapter Url.  Once we re-did the web adapter, problem fixed.  This was for sure a defect in the upgrade process.

[Anonymous User]

Hey @Phil I'm not exactly tracking your solution.  When you said the WA was set to the server url did it have the complete services url address:  https://mydomain.com/server ?  and what exactly is the web adapter url and how is that different?  I'm working with a fresh install of Enerprise at 10.9.1 and federation validates--the site is working as it should.  I'd hate to update these url's and not have to.  Thanks!

[PhilDunn]

Hi Randall.  When the Portal federates to AGS, you can use the WA Url as the AGS location.  Which is what we did originally.  After the upgrade, somehow the AGS registered on the Portal showed the server name (https://servername/server) instead of our WA name, which was https://myalias.mydomain.com/server.  Not sure how or why it changed it.  So the fix was that we just uninstalled the WA, then installed it again.  Seemed to fix it.  It's been a while so I don't remember if we had to re-federate or not.

[Anonymous User]

@ColinWerle1 @PhilDunn bonehead move on my part.  I wasn't signed into Portal.  I remember in older versions of Pro the error would let you know you needed to sign into an active portal.  Maybe I'm just not remembering that correctly?

[ColinWerle1]

Glad to hear it was resolved. Thanks for sharing your fix!

[Tech_MahindraGIS]

Hi Colin,

We also having this issue but could not resolved using your suggestions. we recently upgraded to ArcGIS Enterprise 10.9, Pro 2.8.1and UN tools 2.8.1.

Please suggest

[GeethanjaliM]

@Tech_MahindraGIS I faced the same Error. Issue was with federation in my case. Did you check whether your server is federated properly with your Portal?