Slow Sychronization

[BartPouteau]

I'm running ArcGIS for Windows Mobile version 10.2 (10.2.5000.3581) on a Juno 3B device connected to a wireless network.  I have a feature class with approximately 13000 points in it and after editing one attribute on one point the synchronization process takes 12 minutes which seems quite excessive considering only the changes (or at least that's my understanding) get sent back and forth.

The same process on a full Windows version of Mobile takes 10 seconds.

There are a few bugs related to this issue (NIM 064309 & NIM 087498) but both pertain to an earlier version of the software.
There's also a posting (http://forums.arcgis.com/threads/17562-Excessive-time-to-post-single-update-windows-mobile-app?highl...) from 2010 that indicates there's a hotfix out there that resolves this issue, but I haven't been able to locate it and it also pertains to an earlier version of the software.

Any suggestions?

Thanks.

Bart

[ChristopherOlsen]

Bart-
NIM087498 is still active and valid in the system.  It was logged at 10.1 sp1, and in terms of mobile, there have not been that many changes to the MPC or caching tools since then.  So, it could be that you are still hitting this bug.  Have you logged a ticket with Support yet?  If not, I would encourage you to do so and that way we can troubleshoot the issue. Thanks!

[BartPouteau]

A ticket has been logged.

[AkhilParujanwala]

I agree synchronization can be slow in general.
I instead set my code to upload only. My field teams only upload data to the server as opposed to using a bidirectional sync where it would take a long time.
I am still using 10.0 just an FYI.

[BartPouteau]

Just as an update.  Tech Support determined that this was a new bug (NIM098612 - Slow synchronization with ArcGIS Mobile when using mobile services) and are currently reviewing whether or not they will create a Hot Fix.

Bart

[JeffJohnson]

We are experiencing slow synchronize as well using ArcGIS for Windows Mobile (10.2.5000.3581). Just tapping the synchronize button on the mobile device (Trimble GeoXH 6000, Windows Mobile 6.5) results in a 10-20 minute wait for the task to launch. I have attached the mobile project description as a text file to this post. We have just upgraded from 10.0 to 10.2.1 and this is a terrible bug that will kill production.

[AkhilParujanwala]

Are you guys registering your featureclasses/featuredatasets as versioned?
Or are you not registering as versioned?

There are 3 options:
Not registering as version = fast sync from my experience
Registering as versioned without moving edits to base = fast sync but to the delta tables - meaning the actual feature classes doesn't contain the updated features until you reconcile
Registering as versioned with moving edits to base = slow sync, writes to the delta tables and then moves the data to the actual featureclass.

I personally don't register as versioned, it write straight to the featureclasses and all you have to do in ArcMap is press the little refresh button.
If I registered as version and move edits to base then I wouldn't have to press the refresh button in ArcMap, but my mobile app would take forever to sync.

I hope this helps.

[JeffJohnson]

We are using versioning and may consider sourcing to DEFAULT. We were using versioned data for ArcGIS Mobile at version 10 and the work flow was great. We could collect hundreds of features then post to SDE in a matter of seconds via desktop connection. The guys could rec and post, connect dots, edit attributes, etc. then post to DEFAULT and everything worked great. Tried to synch two point features this morning and after 26 MINUTES that process was done.

I have reported a bug/incident to ESRI and they have replied and mentioned the bug described previously in this thread. ESRI has also suggested publishing some of the data as a tiled mobile cache.

Thanks for the reply and I will try and update.

[TerryOD]

Hi Bart, Sorry for digging this up but I'd be interested to know if you found a solution? We're testing migration from 10.0 to 10.3 and have hit the same slow sync issue. Thinking that we may have to look at other options to enable us to move forward.

Cheers

Terry