<?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 error: request entity too large importing replica schema changes in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/error-request-entity-too-large-importing-replica/m-p/614548#M20415</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;setup: Main server: SDE 10.2 SQL Server on our own network. Parent replica and tools run from here. Destination server: Amazon web server running ArcGIS Server &amp;amp; SDE 10.2 SQL Server. Child replica lives here. Accessed through a geodata service&lt;/P&gt;&lt;P&gt;Getting an unusual error trying to sync replica changes from a replica change file to a replica using a geodata service. I generated the change file no problem using the same geodata service but when I use it in the "Import Replica Schema" geoprocessing tool the job fails with an error that says "request entity too large".&lt;/P&gt;&lt;P&gt;Google searches show a similar Apache error to do with max upload file size but this change file is very modest 52 kb. Has anybody come across something similar?&lt;/P&gt;&lt;P&gt;One thing of note the web service is an Amazon AWS server and it is a 2 way replica.&lt;/P&gt;&lt;P&gt;For the moment I'm going to try to copy the change file to the web server and run the import from there but long term I need to set up batch jobs that test for and import schema changes. Any help/ideas/suggestions greatly appreciated. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Jul 2014 04:10:04 GMT</pubDate>
    <dc:creator>DrewDowling</dc:creator>
    <dc:date>2014-07-31T04:10:04Z</dc:date>
    <item>
      <title>error: request entity too large importing replica schema changes</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/error-request-entity-too-large-importing-replica/m-p/614548#M20415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;setup: Main server: SDE 10.2 SQL Server on our own network. Parent replica and tools run from here. Destination server: Amazon web server running ArcGIS Server &amp;amp; SDE 10.2 SQL Server. Child replica lives here. Accessed through a geodata service&lt;/P&gt;&lt;P&gt;Getting an unusual error trying to sync replica changes from a replica change file to a replica using a geodata service. I generated the change file no problem using the same geodata service but when I use it in the "Import Replica Schema" geoprocessing tool the job fails with an error that says "request entity too large".&lt;/P&gt;&lt;P&gt;Google searches show a similar Apache error to do with max upload file size but this change file is very modest 52 kb. Has anybody come across something similar?&lt;/P&gt;&lt;P&gt;One thing of note the web service is an Amazon AWS server and it is a 2 way replica.&lt;/P&gt;&lt;P&gt;For the moment I'm going to try to copy the change file to the web server and run the import from there but long term I need to set up batch jobs that test for and import schema changes. Any help/ideas/suggestions greatly appreciated. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jul 2014 04:10:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/error-request-entity-too-large-importing-replica/m-p/614548#M20415</guid>
      <dc:creator>DrewDowling</dc:creator>
      <dc:date>2014-07-31T04:10:04Z</dc:date>
    </item>
  </channel>
</rss>

