<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Nightly batch reconcile corrupts geometric network features in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/nightly-batch-reconcile-corrupts-geometric-network/m-p/1663645#M45792</link>
    <description>&lt;P&gt;We have had for years, no decades, an ArcObjects-based .NET process that reconciles outstanding versions.&amp;nbsp; &amp;nbsp;When reconciles are complete, a compress is initiated.&amp;nbsp; &amp;nbsp;This (at least until now) has run like clockwork.&lt;/P&gt;&lt;P&gt;A few weeks ago users discovered that versions&amp;nbsp; not reconciled and posted during the day, which most are, were found to have corrupt network features when the version was re-opened the following day.&amp;nbsp; &amp;nbsp;And when I say "corrupt" I mean either not connected to other features or un-editable -- and requiring the "Geometric Network Editing" tools to repair.&lt;/P&gt;&lt;P&gt;After investigation we found that if we turn off the nightly reconcile (basically disable the scheduled task under which it runs) features are not corrupted.&lt;/P&gt;&lt;P&gt;Clearly something has changed and we're in the process of trying to determine what.&amp;nbsp; &amp;nbsp;In the mean time we've found that an ArcPython scripted reconcile does not seem to cause corruption.&amp;nbsp; &amp;nbsp;However, the fact that something so fundamental to our solution is failing is a cause for concern.&amp;nbsp; &amp;nbsp;Any chance anyone else has seen this?&amp;nbsp; &amp;nbsp;If so, any feedback would be much appreciated.&lt;/P&gt;&lt;P&gt;Thx,&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;</description>
    <pubDate>Wed, 05 Nov 2025 18:13:08 GMT</pubDate>
    <dc:creator>EdwardBlair</dc:creator>
    <dc:date>2025-11-05T18:13:08Z</dc:date>
    <item>
      <title>Nightly batch reconcile corrupts geometric network features</title>
      <link>https://community.esri.com/t5/data-management-questions/nightly-batch-reconcile-corrupts-geometric-network/m-p/1663645#M45792</link>
      <description>&lt;P&gt;We have had for years, no decades, an ArcObjects-based .NET process that reconciles outstanding versions.&amp;nbsp; &amp;nbsp;When reconciles are complete, a compress is initiated.&amp;nbsp; &amp;nbsp;This (at least until now) has run like clockwork.&lt;/P&gt;&lt;P&gt;A few weeks ago users discovered that versions&amp;nbsp; not reconciled and posted during the day, which most are, were found to have corrupt network features when the version was re-opened the following day.&amp;nbsp; &amp;nbsp;And when I say "corrupt" I mean either not connected to other features or un-editable -- and requiring the "Geometric Network Editing" tools to repair.&lt;/P&gt;&lt;P&gt;After investigation we found that if we turn off the nightly reconcile (basically disable the scheduled task under which it runs) features are not corrupted.&lt;/P&gt;&lt;P&gt;Clearly something has changed and we're in the process of trying to determine what.&amp;nbsp; &amp;nbsp;In the mean time we've found that an ArcPython scripted reconcile does not seem to cause corruption.&amp;nbsp; &amp;nbsp;However, the fact that something so fundamental to our solution is failing is a cause for concern.&amp;nbsp; &amp;nbsp;Any chance anyone else has seen this?&amp;nbsp; &amp;nbsp;If so, any feedback would be much appreciated.&lt;/P&gt;&lt;P&gt;Thx,&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 18:13:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/nightly-batch-reconcile-corrupts-geometric-network/m-p/1663645#M45792</guid>
      <dc:creator>EdwardBlair</dc:creator>
      <dc:date>2025-11-05T18:13:08Z</dc:date>
    </item>
  </channel>
</rss>

