Latest Contributions by EdwardBlair

Its a json file downloaded from my.esri.  I've been working with ESRI tech support on this for about two weeks.   They're stumped, too. I'm about to install the license server on another machine... which seems to work. Thanks again, Ed ... View more

Hi Richard (or anyone) - I followed you suggestion and made IPv4 preferred over IPv6 - as indicated in the screenshot below (I think).  The darn license manager still returns a MAC address of "ffffffff".   And when I try to authorize my license file I still get an error that the MAC address in the license does not match the address of the machine. Any other thoughts would be greatly appreciated. Ed       ... View more

Hey Richard - Just saw your post.   Thanks much for responding.  I'll take a look at your link. Ed ... View more

Hi Joker - I assume you're using a geometric network here, true?   If so, that's the way the software works.   A junction is the endpoint of all lines connected to the junction.  If you move the junction the endpoints of the line move. Depending on exactly what you wan to do, you may be able to insert a vertex (or vertices) on either side of the junction, so when you move the junction only that, and the small segments between your new vertex and the junction will move. Adding a screen shot may help other better understand exactly what you are trying to do. Ed ... View more

Thank you, Heather!   We tried and failed when connecting as SDE.   Worked fine when we connected as the data owner Ed ... View more

Great.  Thanks for the info! ... View more

Doh!   I had made a number of changes and neglected to re-enable network topology.    Re-enabling allowed me to trace. In my (meager) defense, sometimes just by writing out a description of the problem helps lead to a solution. Sorry! Ed ... View more

Hi gis_KIWI4! This is just what I was looking for.  Thanks! Ed ... View more

So... suspecting that the issue was rooted in SQL*Server permissions, I granted additional permissions to all users involved and systematically checked in ArcGIS Pro after each change to see if this allowed the process to complete.   None of the permissions changes made a difference. Then, at the suggestion of Jeff Buturff, master of all Geodatabase knowledge, I started SQL*Profiler before opening ArcGIS Pro with the hope of capturing the offending call.    For whatever reason, after starting SQL*Profiler and then starting ArcGIS Pro I was able to create a new version without error.  I suspect that starting the profiler somehow put the previous permissions changes into effect -- but that's just a guess.  At any rate, I can now create versions. Ed   ... View more

Walked through the steps with ESRI Tech Support.  Still stumped.   Here's what we observed/tried: We have a Branch versioned service published to ArcGIS Enterprise 11.2 from Utility network data in an enterprise geodatabase. We encounter the mentioned error when we create new versions on the service. Confirmed from the ArcGIS enterprise portal that the user with which we are connected to the portal in ArcGIS Pro has administrators privileges, has Advanced editing user type extension. From the server manager we confirmed that the service has version management capabilities enabled. We published a new service from the same data and observed that we encounter the same error message. We created a new polygon feature class in the enterprise geodatabase and registered it as branch versioned. We published yet another branch versioned service from the new feature class created with the version management capabilities enabled however when creating the versions encountered the same error message. From the server manager we observed that in the server logs we do not get any additional error rather the same error is mentioned there as well. Tech support is going to research further.   Will post a resolution when we get to one. Ed ... View more