Hello all,
I have a strange issue with Enterprise Portal 11.5 due to a failed overwrite of a referenced service from a SQL Enterprise Database with traditional versioning and feature access enabled.
I removed an attribute rule from a layer within the SDE because it was causing users to not be able to save edits in a web Experience. Deleting the attribute rule went as expected; however, when I attempted to overwrite the service in our portal, it failed. Unfortunately, I did not save the failure log. It appears the failure was at the reconciliation phase, and the original service no longer existed in the Enterprise Server Manager. A new service named the same except with a time stamp at the end has been created (myService_2020606051321).
The portal item associated with the original service still existed in the portal contents; however, it no longer points to a mapServer or featureServer because the named service no longer exists, only the one with the timestamp. The original portal items are essentially broken at this point, along with all the maps and apps that draw data from them.
In an attempt to sort out what was happening, I tried overwriting the original service again, only to be given a warning of "Unable to retrieve information for existing item: Service not found". Instead, I published a "new" service with the exact same name as the now broken one. This has successfully created a new portal item, as well as restored the REST connection to the "old" portal item and restored the data connection in all of the associated maps and apps.
The real issue is that I now have two portal items with the same name, but different ID numbers in the portal details section, and they both point back to the exact same REST endpoint. All in all, it's not a huge issue to have both these portal items and maybe change the name of the one I don't intend to use.
I am wondering if there is something I can do to delete the newly created portal item without destroying the other one?
