I'm wondering if someone can tell me if they have had a similar Portal experience?
Michael: I have noticed that I get this error whenever I republish a map service; the map service that is already in Portal's web map will lock up and becomes unusable. This seems to occur whenever I update a field in the geodatabase layer and then republish (without republishing I don't see any database changes in the Portal map service). This is sort of frustrating because I was hoping that I could republish a map service and retain the popup configurations that I had already completed (that task can sometimes take me hours to do), rather than adding the map service to the web map each time, and then having to redo all of those popup configurations for all of the layers in that one map service (am I ever glad now that I decided to create several smaller map services rather than one large one 
).
Unless of course I'm doing something wrong. I find that I have to stop the map service before I can edit the geodatabase, and then restart it before I publish (with overwrite); however, if I just publish it will turn on the map service anyway. I just thought that if one republishes a map service then the map service layers already in the web map will automatically adopt the changes that one made in the MXD before republishing; mine just seems turn off the ability to configure the popup. The only solution I have found, so far, is to reload the map service from the web map Portal, reload a new one, and then reconfigure all of the popups. If it is still locked up at that point then the only other solution I have found is to create a brand new MXD (from scratch) and publish it again; hence, the problem seems to find it's way back into the geodatabase and may corrupt the MXD.
Mark,
A few things come to mind:
1. You do not have to republish if there are schema changes. Just restart the service. Reason is, the ArcSoc in memory process is what holds that information on your service instance. So don't republish. Also, by default (I don't know why it is enabled by ESRI as default) there is a setting I always change to false.
In Catalog:
Alternately in ArcGIS Server Manager:
2. Unlikely an MapDoc issue. From the knowledge presented this far, I am doubting it is a corrupt mxd.
3. If it is 'still locked up' my bet is just browser caching. Depending on brower, make sure to do Hard Reloads
e.g. Chrome:
F12 - Then you can right click on the reload button and select HARD
Just like layers, the Field values for the popup uses indexing. When you re-arrange these indexes, you risk the change of breaking widgets. In this case, the popup configuration.
E.g. a summary widget points to a specific layer in a featureclass service. in that mxd that was used, lets say you add 3 new layers (2 before and 1 after the original layer in the map) and overwrite the publish... your index numbers will change. The Summary widget would no longer be looking at /0 as the proper layer.
You have to be aware that scoping out content should be carefully planned from the get go.
Are you appending fields to the end only? or are you rearranging fields as well?
Hi Paul,
Yes, forgot about disabling the Automatic Account creation. You are referring to this :
Automatic registration of enterprise accounts—Portal for ArcGIS (10.4.1) | ArcGIS for Server
When you have tied A.D. do you not have to follow the below to add named users to Portal? Manually, batch or automate... guess it is not much work, but its a workflow process none the less.
