I have a reproducible scenario that is causing duplicate Portal items to be created for services published to a Federated ArcGIS server. All software is running version 10.5 and the ArcGIS Server site is a multi-machine site with two machines. The ArcGIS Server config-store and directories are on a network drive references by a UNC path. The ArcGIS Server processes both run under the same domain account and I have verified that the file system permissions on the network storage are appropriate.
Here are the steps taken along with a description of the intermediate errors and effects:
The biggest issue I have at the moment is that there is a lot of content that needs to be repairs because the original service items no longer map to the portal Items that ArcGIS Server believes represent the services, so users get errors trying to add these old items to their Web Maps.
This issue just started happening in the past week, so I am assuming some sort of corruption or misconfiguration was introduced. Restarting the ArcGIS Server services and the Portal service has had no effect. Absent any advice from this forum, my next attempt to resolve the issue is to remove each ArcGIS Server from the Site and then re-add it, hoping that will reinitialize whatever if causing the issue.
I have seen other reports of CONT_0005 error, but they all seemed to be related to republishing service via ArcPy without setting the sddraft to Replacement mode.
Any and all advice is appreciated.
It appears that this issue I've run into is documented as a series of BUGs in 10.5 that were fixed in 10.5.1. Other than keeping Portal Service Items out of Portal folders in the short-term, upgrading appears to be the correct fix.
Yes, we worked around the issue by moving all of the Service Items into the root of the Named User that owned the service, instead of placing them in Portal folders.
We could still publish the services into ArcGIS Server Folders, but the corresponding Portal Item needed to be in the root of the Named User's My Content page.
For what its worth I think some form of these bugs still exist in 10.5.1. In our case services appeared to be shared to Everyone but in reality were not. We use IWA which may play a role, not sure. Next time it surfaces I'll try some of these suggestions.