|
POST
|
Thank you, Heather! We tried and failed when connecting as SDE. Worked fine when we connected as the data owner Ed
... View more
02-21-2025
07:34 AM
|
0
|
0
|
1069
|
|
POST
|
Hi - Is there any value in performing a compress on a non-versioned, archive-enabled geodatabase? I can't think of why there would be -- there are no extraneous delta table rows that would have been moved to the base table. But I might be missing something. Thx, Ed
... View more
02-19-2025
07:22 AM
|
0
|
2
|
1043
|
|
POST
|
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
02-04-2025
02:06 PM
|
2
|
0
|
932
|
|
POST
|
So, I'm trying to use the Subnetwork Trace tool (though the same thing happens with a Connected trace) and I consistently get the error "A networking error has occurred" (below). Following instructions from the links below, I increased the "javaHeapSize" parameter on the published feature service to, first, 128 and second, 256. The first site says that a heap size of 256 should be able to handle 800,000 edges and 800,000 junctions. My entire electric network is smaller than this. Any other suggestions would be greatly appreciated. Thx, Ed https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-errors-and-warnings-03626-03650-003642.htm https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/share-analysis/geoprocessing-service-settings-advanced.htm
... View more
02-04-2025
01:11 PM
|
0
|
1
|
945
|
|
POST
|
Hi gis_KIWI4! This is just what I was looking for. Thanks! Ed
... View more
02-03-2025
06:04 AM
|
0
|
0
|
942
|
|
POST
|
All - I'm sure there is a way to do this and I'm just missing it, but is there a way to export the assigned terminal configurations from a utility network? Thx, Ed
... View more
01-31-2025
09:23 AM
|
0
|
2
|
1003
|
|
POST
|
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
01-30-2025
09:23 AM
|
0
|
0
|
1937
|
|
POST
|
Hi - I was looking for a way to get the classes joined to a feature layer in ArcMap. A Google search returned a description of an IJoinInfoCollection interface that is exposed on a feature layer. This looked perfect! But when I go look for the thing in VS, or really anywhere else, I don't see any evidence of this interface. Is Google AI just making up stuff? Any guidance would be much appreciated. Thx, Ed
... View more
01-29-2025
10:43 AM
|
0
|
0
|
444
|
|
POST
|
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
01-24-2025
12:57 PM
|
0
|
0
|
1968
|
|
POST
|
Michael - Thanks for your suggestion to use "Save A Copy". I tried this and it worked for one of my MXDs (though not all). So... many thanks! But (and I don't mean to look a gift horse in the mouth) is there a way know what "wasn't being used"? These MXDs are complex animals. With joins, relates, definition queries, excluded features, etc. etc. Is there a way for me to know what got left behind? BTW - I found that an MXD *not* resolved by your suggestion was one that had a definition query based on a join - and the join was not updated. And now I at least know to account for that case. Thanks again for you suggestion. Much appreciated. Ed
... View more
01-21-2025
04:12 PM
|
0
|
0
|
1947
|
|
POST
|
Rhett - Thanks for the insights. Out of curiosity I tried both MXD Doctor and the Defragmenter and, as you suspected, neither of these identified or fixed the problem. Ed
... View more
01-21-2025
10:57 AM
|
0
|
0
|
1963
|
|
POST
|
Hi Chris - Just wanted to let you know that I tried the python script you suggested. It didn't find anything broken, but we still get prompted for a database connection when opening the MXD. Ed
... View more
01-21-2025
10:53 AM
|
0
|
0
|
1965
|
|
POST
|
Hi Chris - Thanks for the reply. The thing is, there are no broken data sources in the MXD. All layers are hooked up correctly to sources. But we still get prompted for a database connection. Ed
... View more
01-21-2025
08:11 AM
|
0
|
4
|
1980
|
|
POST
|
We've got numerous detailed maps with feature layers that we want to "swizzle" to point to a new Geodatabase. This works is most cases, however there are a few cases where, even after all feature layer data sources have been changed, when opening the map we are prompted to enter a database connection. In some cases, simply saving and closing the map document resolves the issue. But in some cases not. Its as if the MXD has a broken database reference that is *not* among the map's feature layers. Any suggestions would be much appreciated. Thx, Ed
... View more
01-20-2025
04:22 PM
|
0
|
7
|
2036
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-14-2026 07:31 AM | |
| 1 | 05-11-2026 02:55 PM | |
| 1 | 01-07-2026 12:34 PM | |
| 1 | 01-04-2026 05:14 PM | |
| 1 | 12-17-2025 07:45 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|