Latest Contributions by VishApte

You probably have checked, but  1. Is your EGDB connection set as branched version? 2. Is UN dataset registered as versioned? 3. Do all datasets have globalids? ... View more

I have same observation, it takes ages to Enable Topology if there are too many errors. Iterative approach will be better. In my case, most of the errors were due to the missing rules, missing terminals, missing junctions and some snapping issues. "snap" tool and some simple model builder tools for setting terminals as well as adding junctions etc. fixed lot of errors. Enable Topology ran lot quicker. Here are some statistics (from memory) Take 1: more than 100,000 (max set) errors and hence failed after 15 hours. Take 2: ~25,000 errors in 7 hours Take 3:  3,000 errors in 1 hour Take 4: <1,000 errors in 25 min. The dataset was HV/MV network with ~18,000 km lines, ~30,000 transformers and ~300,000 poles. HTH. ... View more

Hi Kevin, If you move the junctions added using the Asset Package, does it have a rubber-band effect on the lines they connect to? If not, it means the junctions are not connected. It could be because the junctions are not snapped to the end/vertex/edge or the rule does not allow the connection. Check "assetgroup", "assettype" and "lifecyclestatus" and any other "network" attribute that governs if connection can be made. Enable Network Topology adds system junctions to connect the lines together if the junctions/devices do not conform to UN rules.  I had a similar issue where I had bring the data from the third party system and re-project it into Asset Package. Re-project created junctions with a floating point misalignment and caused the junctions to not snap to line and thus disconnect. I had to run "snap" tool on points before apply asset package. Hope it helps to diagnose the issue further. Cheers, Vish ... View more

Hi Jon, We got it worked out. It seems that the privatePortalURL must be set first and then WebContextURL should be added. If we set both in one go, somehow, privatePortalURL doesn't get registered completely. We could repeat this in 3 environments. So the steps are; 1. Install SSL certificate on port 7443 that matches DNS name for the portal. 2. Change the default self signed certificate to above. 3. Set privatePortalURL to DNS based URL using portaladmin. 4. Test privatePortalURL based URL for Portal Home in a browser and confirm it does not redirect to a server name based URL. 5. Configure Web Adaptor for Portal. 7. Add WebContextURL that matches Web Adaptor using portaladmin 8. Test Portal home via WebContextURL and via privatePortalURL and confirm it works without redirection. 9. Perform federation. Not sure if this is as designed or a bug. Cheers, Vish ... View more

Thanks for your reply Jonathan. But couldn't get it going. I first federated without privatePortalURL property set. Federation between server and portal worked fine. I could see SampleWorldCities and other GP services in Portal under My Contents. Server admin showed ArcGIS_Portal as a authentication provider with portal properties showing portal machine's FQDN name and not DNS name. Everything looked as it should be. I then unfederated the server using portaladmin. Unfederate was successful. Manually removed SampleWorldCities and other GP services in Portal under My Contents as these will be orphaned. Confirmed ArcGIS server has gone back to "GIS Server" as a security provider. Everything looked as it should be. I then went to portal admin and added privatePortalURL property set to portal's https://dnsname.domain:7443/arcgis. Manually restarted Portal service after this, though I believe update of the portal property does it. Confirmed privatePortalURL is still set to DNS.  I then federated the server again with Portal. No error but the "status" glyph beside server admin url remained as "?" even after validate. Went to My Contents in Portal and found nothing there. Was expecting SampleWorldCities and other GP services in there. Went to ArcGIS Server Manager and found that Sharing icon was not available for the SampleWorldCities and other GP services. Went to server admin and found that server has ArcGIS_Portal as a authentication provider with portal properties showing DNS name for the portal and not FQDN name. Server and Portal log had nothing meaningful.  Restarted Portal and Server services. Still no sign of federation of services. ArcGIS Server still had ArcGIS Portal as authentication provider. Browsed to https://dnsname.domain:7443/arcgis/home Got redirected to https://servername.domain:7443/arcgis/home Browsed to https://dnsname.domain:7443/arcgis/portaladmin/ and this time no redirect. So somewhere Portal has not registered privatePortalURL.   Am I missing a step here? Support ticked is logged. ArcGIS Enterprise 10.7.1 and all Windows 2016 Datacenter servers.  Cheers, Vish ... View more

Hi Jonathan, Can you please elaborate on <privatePortalURL>/sharing/rest == https://lb.domain.com:7443/arcgis/sharing/rest I have setup ArcGIS Enterprise 10.7.1 with privatePortalURL as https://dnsforportal.company.com:7443/arcgis and WebContextURL as https://portaldmz.company.com/gisportal and have restarted Portal service after. Portal machine has ssl certificate including root and intermediate matching dnsforportal.company.com and browsers seems to happy when accessing https://dnsforportal.company.com:7443/arcgis/portaladmin and does not give any SSL warning. However, if I browse to https://dnsforportal.company.com:7443/arcgis/sharing/rest, it redirects to https://portalsvr.domain.com:7443/arcgis/sharing/rest where portalsvr.domain.com is the FQDN of the portal server. Same for https://dnsforportal.company.com:7443/arcgis/home, redirects to https://portalsvr.domain.com:7443/arcgis/home . I would expect that because of the privatePortalURL property, portal's web server will stay on https://dnsforportal.company.com:7443/*  I am not sure X-Forwarded-Host setting is required in DNS as the documentation says not to set-it. Besides I am not sure how this can be set in DNS. Is anything else required to use DNS based url as privatePortalURL? May be because of this redirect to FQDN, when I attempt a federation with a ArcGIS Server, server cannot register items with portal.  https://dnsforportal.company.com:7443/arcgis/sharing/rest seem to be inaccessible to the ArcGIS Server. Thanks, Vish ... View more

Possibly, there are records in C_Associations table where from/to globalid does not exist in the specified from/to feature class. ... View more

Hi, Your "Service Territory Feature Class" parameter should typically be from a separate File or Enterprise Geodatabase and not from the same SDE where you are staging UN in. The workflow I follow is; 1. Use Esri supplied Water Distribution Asset Package and export it to another asset package using Change Asset Package Spatial Reference—Tool Reference | ArcGIS Solutions  This creates another asset package with empty feature classes in the coordinate system I want. 2. Using Pro, manually add a service territory polygon in FGDB created in step 1. 3. Stage Utility Network with Service Territory from step 2. Hope this helps.  Cheers, Vish ... View more

Thanks Damien, I am still on Pro 2.3.3 and "Portal Utility Network Owner" attribute in General pane is read-only. Had checked What's new in ArcGIS Pro 2.4—ArcGIS Pro | ArcGIS Desktop   but only mentions about  Transfer ownership of network diagrams—ArcGIS Pro | ArcGIS Desktop  Is there a tool in Pro 2.4 now or a right context option or editable property on UN dataset?  Cheers, Vish ... View more

Hi Vanessa, Not sure why republishing the survey hangs in Connect. Did it validate your form before it hung? If you are adding new fields to a S123 form and if these fields do not exist in the feature service, you can add new fields directly to the feature service using AGOL/Portal UI. Simply go to the feature layer and go to "Data" tab instead of Overview, select the layer you wish to add fields to and click add field. Then try to republish the survey. ... View more