<?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>idea Improve Error Logging and Reporting of Replication/Synchronization Process in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idi-p/944898</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;During a failed Synchronization run, we have received errors like the ones below:&lt;BR /&gt;&lt;BR /&gt;&lt;DIV style="margin-left: 40px;"&gt;ERROR 000582: Error occurred during execution.&lt;BR /&gt;The field is not nullable.&lt;BR /&gt;The field is not nullable.&lt;BR /&gt;&lt;BR /&gt;General function failure&lt;BR /&gt;General function failure&lt;BR /&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;We have may have 20-30 feature classes plus 10 + relationship classes in each of our replicas.&amp;nbsp; It would save us (and ESRI&amp;nbsp;Tech Support) many, many hours to know what feature class or table experienced the error and what column (field) and even objectid is in question.&amp;nbsp; The replicalog.dat file does not provide enough trouble shooting information to be of assistance.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;!-- content transformation source ID: 087300000008M2z --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Mar 2011 18:56:45 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2011-03-30T18:56:45Z</dc:date>
    <item>
      <title>Improve Error Logging and Reporting of Replication/Synchronization Process</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idi-p/944898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;During a failed Synchronization run, we have received errors like the ones below:&lt;BR /&gt;&lt;BR /&gt;&lt;DIV style="margin-left: 40px;"&gt;ERROR 000582: Error occurred during execution.&lt;BR /&gt;The field is not nullable.&lt;BR /&gt;The field is not nullable.&lt;BR /&gt;&lt;BR /&gt;General function failure&lt;BR /&gt;General function failure&lt;BR /&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;We have may have 20-30 feature classes plus 10 + relationship classes in each of our replicas.&amp;nbsp; It would save us (and ESRI&amp;nbsp;Tech Support) many, many hours to know what feature class or table experienced the error and what column (field) and even objectid is in question.&amp;nbsp; The replicalog.dat file does not provide enough trouble shooting information to be of assistance.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;/DIV&gt;

&lt;!-- content transformation source ID: 087300000008M2z --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 18:56:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idi-p/944898</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2011-03-30T18:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Error Logging and Reporting of Replication/Synchronization Process</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944899#M6174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;In version 10, they have included the column name but still no feature class name or table name. It would be hard to troubleshooting with a large amount of feature classes in the database.

&lt;!-- content transformation source ID: 00aE0000002A1e0 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 10:58:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944899#M6174</guid>
      <dc:creator>JoanneLoh</dc:creator>
      <dc:date>2013-04-26T10:58:14Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Error Logging and Reporting of Replication/Synchronization Process</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944900#M6175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Currently encountering this issue in production and it would be wonderful to be able to identify and rectify the problem without the need of a support call..... Not that I dislike support but I would much prefer to be able to resolve the problem myself

&lt;!-- content transformation source ID: 00aE0000005Vjn1 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2014 11:52:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944900#M6175</guid>
      <dc:creator>AlanHope</dc:creator>
      <dc:date>2014-02-26T11:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Error Logging and Reporting of Replication/Synchronization Process</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944901#M6176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We recently received one of these generic errors when attempting to create a 2-way replication.&amp;nbsp; The error stated that we had an 'Invalid GlobalID'.&amp;nbsp; We were unable to isolate the offending feature and therefore had to reset all of the GlobalIDs.&amp;nbsp; With more robust error reporting that provided the objectid of the offending feature we could have more efficiently resolved the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jun 2016 23:29:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/944901#M6176</guid>
      <dc:creator>JakeMatthys</dc:creator>
      <dc:date>2016-06-30T23:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Error Logging and Reporting of Replication/Synchronization Process - Status changed to: Closed</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/1576669#M33522</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Thank you for sharing your Idea with the ESRI Community. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This idea has been closed due to inactivity.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Users looking for similar functionality may open a new idea related to the current implementation of replication in ArcGIS Pro.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2025 23:52:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-error-logging-and-reporting-of-replication/idc-p/1576669#M33522</guid>
      <dc:creator>SSWoodward</dc:creator>
      <dc:date>2025-01-16T23:52:13Z</dc:date>
    </item>
  </channel>
</rss>

