Mobile Sync Issue

When I go to sync a collection or multiple collections, if there is more then 100 photos LR5.4 crashes.
Report:
Process:
Adobe Photoshop Lightroom 5 [485]
Path:
/Applications/Adobe Photoshop Lightroom 5.app/Contents/MacOS/Adobe Photoshop Lightroom 5
Identifier:
com.adobe.Lightroom5
Version:
Adobe Photoshop Lightroom 5.4 [955652] (5.4)
Code Type:
X86-64 (Native)
Parent Process: launchd [153]
Responsible:
Adobe Photoshop Lightroom 5 [485]
User ID:
501
Date/Time:
2014-04-10 22:32:51.493 -0500
OS Version:
Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 686A0E9A-3C71-FFC4-ADC0-9374F6417AC9
Crashed Thread: 25 Worker Thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x0000000120aef000
VM Regions Near 0x120aef000:
MALLOC_LARGE
000000011fc20000-000000011ffef000 [ 3900K] rw-/rwx SM=PRV
--> mapped file
000000011ffef000-0000000121c3a000 [ 28.3M] r--/rwx SM=COW /Users/USER/Pictures/*/*.CR2
CG shared images
00000001c0003000-00000001c000b000 [   32K] r--/r-- SM=SHM
Thread 0:: Dispatch queue: com.apple.main-thread
0   com.adobe.ag.kernel
0x000000010fbe5b27 0x10fbce000 + 97063
1   com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
2   com.adobe.ag.kernel
0x000000010fbd7fb1 lua_resume + 112
3   com.adobe.ag.kernel
0x000000010fbd1988 0x10fbce000 + 14728
4   com.adobe.ag.kernel
0x000000010fbd1798 0x10fbce000 + 14232
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
7   com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
8   com.adobe.ag.kernel
0x000000010fbd7fb1 lua_resume + 112
9   com.adobe.ag.kernel
0x000000010fbd1988 0x10fbce000 + 14728
10 com.adobe.ag.kernel
0x000000010fbd1798 0x10fbce000 + 14232
11 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
12 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
13 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
14 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
15 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
16 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
17 com.adobe.ag.substrate
0x000000010fd42c37 0x10fd31000 + 72759
18 com.apple.Foundation
0x00007fff83fae13e __NSThreadPerformPerform + 229
19 com.apple.CoreFoundation
0x00007fff848cb731 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
20 com.apple.CoreFoundation
0x00007fff848bcea2 __CFRunLoopDoSources0 + 242
21 com.apple.CoreFoundation
0x00007fff848bc62f __CFRunLoopRun + 831
22 com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
23 com.apple.HIToolbox
0x00007fff8a43ca0d RunCurrentEventLoopInMode + 226
24 com.apple.HIToolbox
0x00007fff8a43c7b7 ReceiveNextEventCommon + 479
25 com.apple.HIToolbox
0x00007fff8a43c5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
26 com.apple.AppKit
0x00007fff876bb3de _DPSNextEvent + 1434
27 com.apple.AppKit
0x00007fff876baa2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
28 com.apple.AppKit
0x00007fff876aeb2c -[NSApplication run] + 553
29 com.apple.AppKit
0x00007fff87699913 NSApplicationMain + 940
30 com.adobe.Lightroom5
0x000000010fbb5613 main + 1107
31 com.adobe.Lightroom5
0x000000010fbb51b8 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x00007fff8fe99662 kevent64 + 10
1   libdispatch.dylib
0x00007fff90e6743d _dispatch_mgr_invoke + 239
2   libdispatch.dylib
0x00007fff90e67152 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 3:: Worker Thread Dispatcher
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
7   com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
8   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
9   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
11 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
12 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
13 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
14 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
15 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
16 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
17 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
18 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
19 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
20 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 4:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 5:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 6:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 7:: cr_scratch
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.AgImageIO
0x00000001147cb2b1 0x1146bd000 + 1106609
3   com.adobe.ag.AgImageIO
0x000000011498ab6b 0x1146bd000 + 2939755
4   com.adobe.ag.AgImageIO
0x00000001147951a1 0x1146bd000 + 885153
5   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
6   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
7   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 8:: Queue Processor - AgPhotoAvailability
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 9:: AsyncDataServer
0   libsystem_kernel.dylib
0x00007fff8fe999f2 read + 10
1   com.adobe.wichitafoundation
0x000000010fe2de57 0x10fd9b000 + 601687
2   com.adobe.wichitafoundation
0x000000010fe29900 0x10fd9b000 + 583936
3   com.adobe.wichitafoundation
0x000000010fddd0dd 0x10fd9b000 + 270557
4   com.adobe.wichitafoundation
0x000000010fdcd746 0x10fd9b000 + 206662
5   com.adobe.wichitafoundation
0x000000010fe12230 0x10fd9b000 + 487984
6   com.adobe.wichitafoundation
0x000000010fe121d9 0x10fd9b000 + 487897
7   com.adobe.wichitafoundation
0x000000010fe12063 0x10fd9b000 + 487523
8   com.adobe.wichitafoundation
0x000000010fe1281f 0x10fd9b000 + 489503
9   com.adobe.wichitafoundation
0x000000010fe18ab9 0x10fd9b000 + 514745
10 com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
11 com.adobe.wichitafoundation
0x000000010fdc7642 0x10fd9b000 + 181826
12 com.adobe.wichitafoundation
0x000000010fdc830c 0x10fd9b000 + 185100
13 com.adobe.wichitafoundation
0x000000010fdc8211 0x10fd9b000 + 184849
14 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
15 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
16 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
17 com.adobe.ag.kernel
0x000000010fbe52c8 0x10fbce000 + 94920
18 com.adobe.ag.kernel
0x000000010fbe65c2 0x10fbce000 + 99778
19 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
20 com.adobe.ag.kernel
0x000000010fbe52c8 0x10fbce000 + 94920
21 com.adobe.ag.kernel
0x000000010fbe65c2 0x10fbce000 + 99778
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
27 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
28 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
29 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
30 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
31 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
32 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
33 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
34 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
35 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
36 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
37 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
38 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
39 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
40 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
41 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
42 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
43 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
44 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
45 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
46 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
47 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
48 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
49 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
50 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
51 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
52 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
53 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
54 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
55 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
56 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
57 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
58 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
59 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
60 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
61 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
62 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
63 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 10:: Dispatch queue: AgWFCatalogIndexDefinitions.lua :: /Users/johnwatt/Library/Caches/Adobe/Lightroom/Sync Data/Sync.lrdata/6e60720763c00637a5cde2c
0   libsystem_kernel.dylib
0x00007fff8fe99f92 write + 10
1   com.adobe.wichitafoundation
0x000000010fe2b235 0x10fd9b000 + 590389
2   com.adobe.wichitafoundation
0x000000010fe299c2 0x10fd9b000 + 584130
3   com.adobe.wichitafoundation
0x000000010fddfd28 0x10fd9b000 + 281896
4   com.adobe.wichitafoundation
0x000000010fddf22f 0x10fd9b000 + 279087
5   com.adobe.wichitafoundation
0x000000010fdcdf65 0x10fd9b000 + 208741
6   com.adobe.wichitafoundation
0x000000010fdce52c 0x10fd9b000 + 210220
7   com.adobe.wichitafoundation
0x000000010fe20be9 0x10fd9b000 + 547817
8   com.adobe.wichitafoundation
0x000000010fe19945 0x10fd9b000 + 518469
9   com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
10 com.adobe.wichitafoundation
0x000000010fdc7642 0x10fd9b000 + 181826
11 com.adobe.wichitafoundation
0x000000010fdc830c 0x10fd9b000 + 185100
12 com.adobe.wichitafoundation
0x000000010fdc8211 0x10fd9b000 + 184849
13 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
14 com.adobe.ag.kernel
0x000000010fbe61a9 0x10fbce000 + 98729
15 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
16 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
17 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
18 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
19 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.wichitafoundation
0x000000010fda3e41 0x10fd9b000 + 36417
27 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
28 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
29 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
30 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
31 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
32 com.adobe.wichitafoundation
0x000000010fda3cb1 0x10fd9b000 + 36017
33 com.adobe.wichitafoundation
0x000000010fda39f2 0x10fd9b000 + 35314
34 com.adobe.wichitafoundation
0x000000010fdacf4f 0x10fd9b000 + 73551
35 libdispatch.dylib
0x00007fff90e652ad _dispatch_client_callout + 8
36 libdispatch.dylib
0x00007fff90e6d443 _dispatch_after_timer_callback + 77
37 libdispatch.dylib
0x00007fff90e652ad _dispatch_client_callout + 8
38 libdispatch.dylib
0x00007fff90e678a1 _dispatch_source_invoke + 413
39 libdispatch.dylib
0x00007fff90e67633 _dispatch_queue_drain + 359
40 libdispatch.dylib
0x00007fff90e689dd _dispatch_queue_invoke + 110
41 libdispatch.dylib
0x00007fff90e66fa3 _dispatch_root_queue_drain + 75
42 libdispatch.dylib
0x00007fff90e68193 _dispatch_worker_thread2 + 40
43 libsystem_pthread.dylib
0x00007fff83daeef8 _pthread_wqthread + 314
44 libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 11:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 12:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 13:
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.Foundation
0x00007fff83fb3adc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 253
6   com.adobe.wichitafoundation
0x000000010fe2e3ea 0x10fd9b000 + 603114
7   com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 14:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.Foundation
0x00007fff83fb1967 +[NSURLConnection(Loader) _resourceLoadLoop:] + 348
6   com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
7   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
8   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
9   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 15:
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.AppKit
0x00007fff8785b16e _NSEventThread + 144
6   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
7   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
8   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 16:: Preview Server
0   libsystem_kernel.dylib
0x00007fff8fe99f92 write + 10
1   com.adobe.wichitafoundation
0x000000010fe2b235 0x10fd9b000 + 590389
2   com.adobe.wichitafoundation
0x000000010fe299c2 0x10fd9b000 + 584130
3   com.adobe.wichitafoundation
0x000000010fddf939 0x10fd9b000 + 280889
4   com.adobe.wichitafoundation
0x000000010fdce16f 0x10fd9b000 + 209263
5   com.adobe.wichitafoundation
0x000000010fdce52c 0x10fd9b000 + 210220
6   com.adobe.wichitafoundation
0x000000010fe20be9 0x10fd9b000 + 547817
7   com.adobe.wichitafoundation
0x000000010fe19945 0x10fd9b000 + 518469
8   com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
9   com.adobe.wichitafoundation
0x000000010fdd2b98 0x10fd9b000 + 228248
10 com.adobe.wichitafoundation
0x000000010fdc690b 0x10fd9b000 + 178443
11 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
12 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
13 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
14 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
15 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
16 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
17 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
18 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
19 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
20 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
21 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
22 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
23 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
24 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
25 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
26 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
27 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
28 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
29 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
30 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
31 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
32 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
33 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 17:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x00007fff8fe989aa __select + 10
1   com.apple.CoreFoundation
0x00007fff84908b83 __CFSocketManager + 867
2   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
3   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
4   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 18:: Queue Processor - PreviewFileStore
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 19:: Queue Processor - NegativeQueue
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 20:: Queue Processor - HistogramQueue
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 21:: Queue Processor - RenderQueue_Render
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000

Scott, you mention in your message 'the next time I logged in.' Did you explicitly sign out of Lightroom Mobile sync on the desktop after syncing the first time? Or were you forced to sign in again on launch. If it's the latter this should not be happening and could be another indication that the catalog you signed in with before is not the same (i.e. a backup or a copy that is not at the same state you were when you were last signed in). Is this catalog shared between two machines in any way?
If you are seeing this and you are definitely not in a backup catalog you should be able to do the following with Lightroom shut down. This will work better if you've already done Delete All Data though it isn't required. If you haven't, after relaunching Lr we will rebuild your sync status which can take a while depending on how much you have synced. I would not recommend doing this for any other situation...
On OSX: In Finder go to /Users/<username>/Library/Caches/Adobe/Lightroom/Sync Data/Sync.lrdata and delete it.
On Windows: In Explorer go to C:\Users\<username>\AppData\Local\Adobe\Lightroom\Caches\Sync Data\Sync.lrdata and delete it

Similar Messages

Lightroom mobile sync issues

lightroom mobile says I gave one collection with 442 photos, however it shows one collection with 0 photos.. Help!

Hi,
it can take a while before they are all visible, is it still a 0?
Just to know if I interpret it correctly - you have one collection that you added 442 photos to - but the lightroom mobile app only shows 0 as the count of the images?
Thanks,
Ignacio

Disappearing Contacts, Mobile Me Sync Issues, Calendar crash-Answers??

I'll try to keep this post brief but hopefully it will help provide some possible answers for frustrated users experiencing the random complete wipe out of all contacts and calendar data when syncing with mobile me using either push or fetch. After several weeks of experiencing these random sync issues and spending several hours over several days between tech support calls with iPhone then Mobile Me support and then finally a genius bar appointment where the genius said he didn't have a clue and simply offered to replace my phone.
The next morning, SAME PROBLEMS... and through it all NO ONE could tell me why my sync was so randomly unreliable. Every other day for no apparent reason, my phone would suddenly lose all contacts and/or calendar data. (A few thousand contacts and two years of calendar data). It was both frustrating and strange—even stranger that Apple techs had no clue why and seemed to think no one else was having this issue.
I tried everything - complete restores, resets, deleting and re-adding the mobileme account, etc., etc., etc. One tech support person finally said, "good luck..." The others kept handing me off the higher levels of support... until finally they just said "we don't know why this is happening." I was waiting for someone to just say, "Look, we have issues with mobile me, so hang in there and eventually it will work." I can be patient and I still think the iphone is the greatest invention in recent years. But everybody I talked with at Apple seemed to think this should be working flawlessly.
I also started having a crash on the calendar anytime I tried to see the list view for "all calendars." This was frustrating because that's the best feature of the calendar app!
I was prepared to just return to syncing with my computer and wait for the software to improve between the phone and mobile me. Finally, last night I tried a few things that seem to be working... and for the first full day, mobile me is actually useful to me today. (my fingers are crossed!)
Here's what I did.
1. I minimized the number of calendars I was syncing - I have no idea if this affected the sync, but I was syncing eight calendars, now I'm down to four. (You can easily export a calendar and import those events back into a different calendar.)
2. I did a complete restore of the phone (not from a back up) and the VERY FIRST THING, I added mobile me and synced only the calendar (set to push.) This cleared up the random calendar crash in list view and also mobile me was pushing data rather reliably. After a few moments my entire calendar was on the phone and worked perfectly. New events were transferred quickly back and forth.
3. I then chose to sync my contacts through the computer rather than over the air. I fear that the contact sync was somehow messing up the whole communication process between the phone and the cloud. Someone suggested that the number of "groups" in contacts might have an impact on the sync issues as well. I didn't need my contacts to sync with the urgency of "push" so this works for me. Plus I have a lot of contacts and it's just faster over the cable.
4. I then GREATLY reduced the number of apps on my phone. I originally had about 27 and I only reinstalled 9 of them. I did this ONE AT A TIME - starting with the most necessary and useful... and after each install, I checked the functionality of the calendar and mobile me. No problems. Perhaps I was having an app conflict?
5. Then I reinstalled the rest of my content - music, podcasts, photos. Still no problems.
ONE of these steps actually worked, and I'm not sure which one. My guess is that one or more of my apps was conflicting in some way. OR possibly something with the contact sync... but for the last 24 hours the mobile me calendar sync using push has been consistently reliable and useful. (for the record, mobile me email has always worked perfectly for me.)
No one with tech support ever suggested to me that I could be having an application conflict or any other problems with calendars or contact groups, etc. I've spent many hours on this the past few weeks... and for the first time, my iphone seems to be working with mobile me correctly.
In reading many of these posts, it seems a lot of others are having similar problems... so hopefully these suggestions might be helpful. If you have any thoughts as to which of these solutions was the correct one, I would be interested in hearing your opinion.
Thanks!

Are your Address Book contacts and iCal calendars/calendar events on your Mac synced with your MobileMe online address book and calendar?
When you say this data is not synced with your iPhone, none of your MobileMe online data is transferred to your iPhone, or after the initial transfer of this data to your iPhone when you first turned contacts and calendars for over the air syncing with your MobileMe account on your iPhone, the data is not kept synchronized with the MobileMe "cloud"?

IPhone and Windows 7 64 Bit - syncing issues

Hi,
Just wondering if anyone is able to help. I have updated to Windows 7 and am having problems syning my iPhone. It comes up with a multitude of errors but the most common is:
'The iPhone "Michael's iPhone" can not be syned. The required file can not be found.
I have restored the iPhone and after it resets, it sits at the Setup Window in iTunes for ages, then clicks over, starts syncing (it is doind that now) but also displays the error. Will be interesting to see if it actually finishes the sync and to see if the apps work on the phone.
I have also removed iTunes, Quicktime, Mobile App Supprt, Apple Software Updater, Bonjour and reinstalled and still the sync issues coninue. I also ran the diagnostic tool in iTunes on syncing and detecting the iPhone and it reports everything is ok.
Microsoft Windows 7 x64 Business Edition (Build 7600)
Gigabyte Technology Co., Ltd. P55-UD6
iTunes 9.0.1.8
QuickTime 7.6.4
FairPlay 1.5.18
Apple Application Support 1.0
iPod Updater Library 9.0d11
CD Driver 2.2.0.1
CD Driver DLL 2.1.1.1
Apple Mobile Device 2.6.0.32
Apple Mobile Device Driver 1.45.0.0
Bonjour 1.0.6.2 (118.5)
iTunes Serial Number E400D*7E1<Edited by Host>
Current user is an administrator.
The current local date and time is 2009-10-23 19:56:37.
iTunes is not running in safe mode.
Video Display Information
ATI Technologies Inc., ATI Radeon HD 5800 Series
** External Plug-ins Information **
No external plug-ins installed.
Genius ID: cecad029456cdd284aef514988f34808
** iPod/iPhone Connectivity Tests **
iPodService 9.0.1.8 is currently running.
iTunesHelper 9.0.1.8 is currently running.
Apple Mobile Device service 2.50.39.0 is currently running.
Universal Serial Bus Controllers:
Intel(R) 5 Series/3400 Series Chipset Family USB Enhanced Host Controller - 3B34. Device is working properly.
Intel(R) 5 Series/3400 Series Chipset Family USB Enhanced Host Controller - 3B3C. Device is working properly.
FireWire (IEEE 1394) Host Controllers:
Texas Instruments 1394 OHCI Compliant Host Controller. Device is working properly.
Connected Device Information:
iPhone, iPhone 3GS running firmware version 3.1.2
Serial Number: 88924**3NS <Edited by Host>
Most Recent Device Not Currently Connected:
iPod nano (5th Generation) running firmware version 1.0.1
Serial Number: YM937**72D <Edited by Host>
** iPhone/iPod Touch Sync Tests **
Sync tests completed successfully.
I have applied all software updates and the latest chipset drivers for the motherboard. My Nano syncs without a problem. It just seems to be my iPhone.
I have iTunes installed in the defualt directory on C:\ with the mobile apps etc. Music is located on my E:\
I am not sure what to do now....

Well, the new gigabyte bios fixed the issue.

IOS 6 and iTunes 10.7 WiFi Sync issues

WiFi sync works for a day or two then from the device is just keeps saying Looking for Mario Michela's iMac... I restart iMac, reboot iPhone and or iPad. connect via usb cable, uncheck WiFi Sync (apply), recheck WiFi Sync. It will work again for 2 or 3 days. Then starts to fail again.
I've tried using Eithernet and wifi on the mac (no difference)
I've tried turning off the firewall (no difference)
I've reset all setting on the iPhone (no difference)
I've reset SyncServices Folder (/System/Library/Frameworks/SyncServices.framework/Versions/A/Resources/resetsy nc.pl full) -(No difference)
I've called Apple Care 3 times, I keep getting passed around because sync is between product departments.
iOS doesn't support desktop applications, iMac doesn't support mobile devices..
I'm hoping iTunes 11 fixes this issue.. This issue didn't occur prior to iTunes 10.7.

I am getting sync issues too (although on OSX) - seems like others are getting issues too:
https://discussions.apple.com/message/19834721#19834721
Good luck,
Chris

Lightroom Mobile Sync - Extremely High CPU Usage/Sync Process Causes LR To Lag

Since my other thread doesn't seem to be getting any responses, I'm pasting what I've found here. Please keep in mind I am not a beginner with Lightroom and consider myself very familiar with Lightroom's features excluding the new mobile sync.
1st message:
I'm on Lr 5.5 and using the 30 day trial of Adobe CC to try syncing one collection of slight more than 1000 images. Despite already having generated the Smart Previews, I can see my CPU crunching through image after image (the rolling hills pattern in the task manager) while doing the sync. I was assuming, since I already created the Smart Previews, that the sync of this collection would begin immediately and be done by simply uploading all of the existing Smart Previews. The Smart Previews folder of the catalog is 871MB and has stayed the same despite the CPU obviously doing *something*. As it is now, the sync progress is incredibly slow, almost at a pace like it's actually exporting full-res JPGs from the RAW images (as a comparison only, I know this should not be what it's actually doing).
Another side effect of this is that I'm basically unable to use my computer for other tasks due to the high CPU utilization.
Win 7 x64 / Lightroom 5.5
Intel i5 2500k OC'd 4.5GHz
16GB RAM
SSD for OS, separate SSD for working catalog and files
2nd message:
As a follow up, now Lightroom thinks all 1026 photos are synced (as shown in "All Sync Photographs" portion of the Catalog though all images after the 832nd image show the sync icon per image stuck at "Building Previews for Lightroom Mobile" and the status at the top left corner has been stuck at "Syncing 194 photos" for over 12 hours. Is there no option to force another sync via Lightroom Desktop and also force the iOS app to manually refresh (perhaps by pulling down on the collections view, like refreshing via the Mail app)?
3rd message:
One more update, I went into Preferences and deleted all mobile data, which automatically signed me out of Adobe CC and then I signed back in. Please keep in mind the Smart Previews were long generated before even starting the trial, and I also manually generated them again (it ran through quickly since it found they were already generated) many times. Now that I'm re-syncing my collection of 1026 images, I can clearly see Lightroom using the CPU to regenerate the Smart Previews which already exist. I have no idea why it's doing this except that it's making the process of uploading the Smart Previews extremely slow. I hope this time around it will at least sync all 1026 images to the cloud.
4th message:
All 1026 images synced just fine and I could run through my culling workflow on the iPad/iPhone perfectly. Now I'm on a new catalog (my current workflow unfortunately uses one catalog per event) and I see the same problem: Smart Previews already generated but when syncing, Lightroom seems to re-generate them again anyway (or take up a lot of CPU simply to upload the existing Smart Previews). Can anyone else chime in on what their CPU utilization is like during the sync process when Smart Previews are already created?
New information:
Now I'm editing a catalog of images that is synced to Lightroom Mobile and notice that my workflow has gotten even slower between photos (relative to what it was before, this is not a discussion about how fast/slow LR should perform). Obviously Lightroom is syncing the edited settings to the cloud, but I can see my CPU running intensively (all 4 cores) on every image I edit and the CPU utilization graph looks different than before I started using LR mobile sync. It still feels like every change isn't simply syncing an SQLite database change but re-generating a Smart Preview to go with it (I'm not saying this is definitely what's happening, but something is intensively using the CPU that wasn't prior to using LR Mobile).
For example: I only update the tint +5 on an image. I see the CPU spike up to around 30-40%, then falls back down, then back up to 100%, then back down to another smaller spike while Lightroom says "Syncing 1 photo". I've attached a screenshot of my CPU graph when doing this edit on just one image. During this entire time, if I try to move onto edit another image, the program is noticeably slower to respond than it was prior to using LR mobile, due to the fact that there appear to be much more CPU intensive tasks running to sync the previous edit. This is proven by un-syncing the collection and immediately the lag goes away.
I'd be happy to test/try anything you have in mind, because it's my understanding that re-syncing photos that are edited that are already in the cloud should be simply updating the database file rather than require regenerating any Smart Previews or other image data. If indeed that's what it should be doing, then some other portion of LR is causing massive CPU usage. If this continues, I will probably not choose to proceed with a subscription despite the fact that i think LR mobile adds a lot of value and boosts my workflow significantly if it wasn't causing the program to lag so badly in the process.
I know this message was incredibly long and probably tedious to read through so thanks in advance to anyone who gets through it
-Jeff

Thanks for reporting. Just passed along your info to some of our devs. One of the things that needs to be created (beside smart previews) during an initial sync are thumbnails + previews for the LrM app - Guido
Hi Guido,
Thanks for pointing this out. I realized the same thing when I tried syncing a collection for offline mode and found out the required space sounded more like Previews + Smart Previews rather than just the Smart Previews.
greule wrote:
Hi Jeff, are your images particularly large or do you make a lot of changes which you save to the original file as part of your workflow?
The CPU usage is almost certainly from us uploading JPEG previews not the Smart Previews - particularly during develop edits as these force new JPEG previews to be sent from Lightroom desktop, but would not force new Smart Previews (unless the develop edits are modifying the original file making us think the Smart Preview is out of date) to be sent.
Guido
My images are full-resolution ~22mp Canon 5D Mark III RAW files so they're fairly large. Even if I only make one basic change such as exposure changes, I saw the issue. By "save to the original file" I'm assuming metadata changes such as timestamps, otherwise edits to the images aren't actually written to the original file. I'm only doing develop module edits so I shouldn't be touching the original file at all at this point in my workflow.
I think it makes sense now that you mention that new JPEG previews need to be generated and sent to the cloud due to updated develop edits. My concern is that this seems to be done in real-time as opposed to how Lightroom Desktop works (which is to render a new Standard Preview or 1:1 Preview on demand, which means only one is being rendered at any given time while viewing it in Loupe View or possibly 2 in Compare View). If I edit, for example, 10 images quickly in a row, once the sync kicks in a few seconds later, editing the 11th image is severely hindered due to the previous 10 images' JPEG previews being rendered and sync'd to the cloud (I'm assuming the upload portion doesn't take much CPU, but the JPEG render will utilize CPU resources to the fullest if it can). Rendering Standard/1:1 Previews locally and being able to walk away while the process finishes works because it is at the start of my workflow, but having to deal with on-the-fly preview rendering while I'm editing greatly impacts my ability to edit. Perhaps there can be a way to limit max CPU utilization for background sync tasks?
It may help to know that I'm running a dual-monitor setup, with Lightroom on a 27" 2560x1440 display maximized to fit the display (2nd display not running LR's 2nd monitor). Since I'm using a retina iPad, the optimal Standard Previews resolution should be the same at 2880 pixels.
Thanks again for the help!

Apple iPad 6.1.2 10B147 - Active Sync Issues Remain

Hi,
Please correct me ASAP if I am posting this in the wrong area of the discussion forum.
I have a batch of Apple iPad devices that are now connecting to our Exchange 2003 system using Apple iPad iOS 6.1.2 10B147 devices. It would seem that these devices may have the 6.1 Active Sync issue again even though this version was meant to fix the issue.
A couple of users have reported this morning reoccuring calender cancellations, we have also had excessive log growth on Exchange 2007 platform.
Here is the reported "Device Agent" from Active Sync logs:
Apple-iPad3C6/1002.147
Apple-iPad2C7/1002.147
Apple-iPad2C7/1002.147
Apple-iPad3C6/1002.147
Apple-iPad2C7/1002.147
Apple-iPad3C6/1002.147
Here is the reported Device iOS
DeviceOS
iOS 6.1.2 10B147
Does anyone know if Apple has this as a reported bug yet on their fixed version? If not is there an official Apple bug submission process that should be followed?
Regards
Ben Paddick

Hi waddock,
I think that for the most part, iOS 6.1.2 resolved the recurring calendar bug and the significant battery drain issues. With that said, I have had a couple cases of devices still experiencing the battery drain but not the calendar bug. Quick fix is to remove the Exchange mailbox(es) from the device and re-add it. If there are any existing accounts that use Exchange ActiveSync (I think Hotmail and legacy GoogleSync), I just remove and add them back to just in case.
I suggest checking here for periodic updates on what's going on with EAS (Exchange ActiveSync) and 3rd party devices like Apple:
http://support.microsoft.com/kb/2563324
I assume you're an on-premise environment, so to mitigate short-term, you may want to think about blocking certain devices on certain operating systems using your Device Access Settings in Exchange for mobile devices.
For feedback for Apple, you can do it a couple ways. This is the internet facing site:
http://www.apple.com/feedback/
Or you can create an Apple Developer account (or Apple IT program if you have an enterprise agreement with them) and start submitting feedback during your testing (i.e. beta versions of iOS):
https://developer.apple.com/
Hopefully this helps!

Lightroom Mobile Sync Problems

Hi
My Lightroom Mobile syncing process is running very slow. I deleted the sync.lrdata file and started a new sync of approx 9500 images. Currently I have around 2100 images to sync, however the process has almost stopped. Any help or guidance would be appreciated.

Hi Trev,
Have you tried Syncing in Safe mode on the Mac? This would be to eliminate any processes that might be active in normal mode that might interfeer with the upload. Does you screen has a Retina Display? I have seen some topics where this might create a longer time for generating Smart previews to a smaller size
(iPad/iPhone screen size, compared to the Retina display)
Did you verify a Speedtest for your connection, just to make sure this is not influencing the sync behavior
This you can check for instance with Speedtest.net by Ookla - The Global Broadband Speed Test
There are some more topics on the forum where people experience problems using the Sync with a high amount of images in the Catalog.
- Re: Lightroom 5.4 to Lightroom Mobile sync is soooo slow - why no local sync?
- Lightroom Sync Issues
Hope this helps

Mobile sync not working for groups

Hello guys,
i've been playing with Mavericks Server and so far everything is working smoothly except for the mobility sync...
i successfully created a Local Network Account and was able to successfully sync it to the Server using AFP and a specific folder...
This is working awesome, but here comes the issue:
i setup another Local Network Account and assigned it to a Group and used Workgroup Manager (on the same server) to setup the mobility sync for the group...
Now, when i try to login, the mobile profile gets created on the computer but does not sync to the server, it syncs locally instead or i get the error "The sync could not complete because your network home at "(null)" does not allow writing...
if i try Profile Manager websiteit does not work either...
i know this works for a single user, but if i want to sync it using groups it fails....
I've tried finding a possible answer and so far nothing...
Im using OS X Server 3.1.2 and Workgroup Manager 10.9 (421)
Can you please help me out?
Thanks in advance...

Anyone?

Update 9.1.0.79 Mobile Sync and Yahoo Go Sync error when sync iphone 3G

Every time I synce I get the two errors - Mobile Sync and Yahoo go Sync stop working. iPhone has 3.1.3 version. Also, backup takes longer. Please advise.

notice how under diagnostics readout it shows "most recent device not currently connected"
mine does same thing and i have iphone connected when i do it.
my problems also started with this update and i show 4 errors in event viewer which is under adminastrative tools in control panel.
MY problem is super slow backups for a 16gb 3Gs with 12gbs free. a backup used to be done in like 30-45 seconds now takes about 5 minutes and looks as if it stals at a few points when looking at bar at top of itunes.
my iphone shows up in itunes and shows all pages etc. i do everything manually although i do sync apps.
everytime i connect iphone and open itunes i get 4 errors thats show up only in event viewer (but anyone who maintains computers should be aware of all tools available to them to see whats going on in the background) that show up for "BONJOUR" i have posted this here and under bonjour forum. i turned off bonjour services the proper way again thrru adminastrative tools>services double click bonjour and change for "automatic to "disabled". don't do it through msconfig as some would tell you to do if it's a bonjour issue.
but checking out event viewer can give you valuable info so you don't do the apple nonsense wasting hours to clean up their messy installation only to have it do exact same thing again. it's obvoius they have a conflict.... now we can only hope for a resolution ie UPDATE if enough complain by sending them all this.
i don't have a jailbreak phone nor am i rebuilding anything i'll live with it till they fix it as my event viewer log isn't getting filled up with bonjour errors anymore nor do i need all this bloated crap apple sends our way... i do have quicktime pro.

Common sync issues for Ovi

We tend to see lots of similar questions here, so hopefully this helps you guys out with your sync issues:
Sync SMS not arriving to device: - Commonly caused by the following reasons.
1. Operator is blocking the message from arriving.
This is the most common fault not to get the message. Please keep informing us about the problem cases via the contact us form http://www.ovi.com/support/care (if you sign in, it will prefill your personal details so you save some typing).
We will work with the operators to resolve the cases as quickly as possible but as it invilves many parties it is not always as speedy as should be. Please be patient.
2. Phone number incorrectly inserted
Very common problem we see every day. Phone number needs to be in international format. It must start with the country code +XXX followed by your number without the first digit (usually 0). e.g. your country code is +44 (UK) and phone number is 0781234567 -> the international number is +44781234567.
3. Operator alters the message.
The operator does something in between and makes the message e.g to disappear or makes the PIN code invalid, etc. Please report these cases also to us and we'll make our best to sort them out. From all the cases these are the most difficult ones to solve and will take long time.
My phone is not on the list of supported devices:
Many new models are not added to ovi as quickly as should and we're aware of this. Again patience is requested from users. We're constantly working to ensure that the new device certification is not forgetting the new devices.
As a workaround you can choose a device with same software platform and you can perform the sync with Ovi even if your new device is not yet on the list.
Synced data disappears:
Some of you have probably seen a case where all the data you have synced is not shown in Ovi. (e.g. secondary mobile numbers).The data is there in the database but not shown in your contacts. All your data is synchronized but all not showed.
We're constantly working on improving the Ovi sync experience so please bear with us and keep providing the feedback.

Hi, Erga.
You wrote:
3. Operator alters the message.
The operator does something in between and makes the message e.g to disappear or makes the PIN code invalid, etc. Please report these cases also to us and we'll make our best to sort them out. From all the cases these are the most difficult ones to solve and will take long time.
As requested by you, here goes my report. I use an E71 and everytime I receive the sync configuration SMS, the PIN Code is reported as invalid. My operator is Claro and I'm in Brasilia/DF, Brazil.
Is there any way to manually configure the phone?
Thanks for any additional information!
Br,
Carlos Lauria

Any troubleshooting tips for sync issues?

Hi,
Very new to Mobile Server. Started work on a new project that uses mobile server and we are running into a sync issue. The sync was working but we have hit an issue now.
Not sure of the cause and looking for pointers on where to look, what are some common problems, etc.
Thanks!
Bill

which version are you using.
your question is very general, perhaps some specific details would help, e.g. olite version, client type, error message etc
generally we had many issues with
connectivity especially through gprs (3g) , we used specific sim cards in handhelds that created a vpn style secure connection to the server and although the connection was established some times the packages size was greater so we had to adjust the connection settings on the device so that olite works during sync.
we had a lot of cases where olite was getting out of sync and was forcing a full refresh, thus losing the client's data. some times the data was entered in the error queue , an email was send to the admin but noone was watching anyway.
and many others.
check connection, check integrity (make sure that not 2 clients change the same table rows) make sure the server doesnt change parts of the database that the clients will change too (thus youll get conflicts).
make sure the sync remains stable, sometimes if you lose connection during a sync a full refresh might be needed (actually a patch was supposed to fix this)
we had issues with the sequences also but mainly because of bad design from our part, which we fixed later on.
etc...please provide some info on what error you are getting.
in general if you are getting an error code then you are probably going to find the solution. check the message reference in help to see what the error means, then try to see on the client what changes were made. check error queue/perhaps a log? server traces might help(might). also it depends what kind of sync are you making, your own or using the olite sync
Edited by: vasileios on May 22, 2013 10:47 PM

Intermittent syncing issue

I've just upgraded to windows 7 x64
(I'm running iphone 3gs 3.1.2/itunes 9.0.2 x64)
and now I get intermittent sync issues.
The applemobiledevicehelper.exe.00.log says: "11:24:41.059|AppleMobileDeviceHelper.exe|2268:18394096|/SourceCache/DeviceLink X/DeviceLinkX-137.1/Utility/DeviceLinkListener.c:_copyMobileDeviceValue| ERROR: Could not connect to attached device: (null) (107)
and
applemobilebackup.exe.00.log says:
"2009-11-08 11:20:44.006|AppleMobileBackup.exe|9584:43045888|/SourceCache/DeviceLinkX/Devic eLinkX-137.1/WireProtocol/DeviceLinkConnection.c:_DLHandlerThreadMessagePortCall back| ERROR: Error calling connect: SocketStreamHandlerConnect: Can't connect to host: Socket error 6 (SocketErrorConnect)"
but if I restart the Apple Mobile Device service & delete the iPodDevices.xml file the iphone shows up fine and will work for a day and then I'll have to do the process again.
Is there something I can do to permanently fix this?
Message was edited by: mrdistortion

Hope this helps out other people but I flashed my bios with the latest settings from Gigabyte and that fixed all of my issues.
http://www.gigabyte.com.tw/Support/Motherboard/BIOS_Model.aspx?ProductID=3165

Lightroom 6 mobile sync "waiting for connection"

This seems to have been a problem for a while, I've never really used the Lightroom mobile sync but decided I would give it a try. I have an iMac with the latest os version and a standard cable modem and network setup. Lightroom just always says waiting for connection in the identity plate. I'm wondering if it's a firewall issue or something, but I can't find any info on ports that need to be opened or anything like that. My router uses upnp. I've tried solutions I could find like deleting all data from online etc. in Lightroom preferences. Can you give me any help with this? Thanks.

I have updated, restarted etc etc and mine still wont actually sync - it says 'waiting for connection' but unlike others this isnt just a display bug - its not actually syncing at all with my laptop, which is very annoying.
I have disabled all antivirus FWs etc - nothing.
I am signed in - my details are shown etc as being signed in - but if I go to preferences and then 'lightroom mobile' it shows my Adobe ID as 'not signed in' - so if I click join it opens Adobe screen in Browser and brings up my account which am already signed into! cant do anything - cant even 'delete all data'

More Aperture/iPad syncing issues

Each time I create a new project or album in Aperture, I have trouble getting the images to the iPad when I sync. I sometimes need to sync several times until the images are recognized and imported to iPad. I do have the albums designated manually, rather than all, which means I have to sync and then sync again after I check the checkbox for the new album. I understand that, but sometimes I have to go back into Aperture to make sure the previews are updated. If I choose to update the previews for a project, Aperture will usually tell me that they're already up to date, but often they will not show up on the iPad, even after I check the appropriate box for the album in iTunes. Sometimes I get good results if I delete the previews and regenerate them in Aperture.
The second problem is the sort order. Even if I have "sort by filename" selected in Aperture, they do not show up in this order on the iPad--despite what the support article says about this. They appear to only show up in Date order. I've tried repeatedly resetting the sort order, but it does not change on the iPad. Sometimes I have to delete the album from the iPad, (uncheck the album in iTunes and sync again), then recheck it and sync yet another time. This does not always work, however.
It is very frustrating. The interface between Aperture and the iPad is very wonky. I often have to sync repeatedly, just to get the photos on the iPad and even then they're usually in the wrong order.
Aperture appears to have two types of previews: "previews" and "sharing previews," but "sharing previews" don't seem to appear in the documentation. I've noticed that, even when Aperture says the previews are up to date, when I exit the program, it will sometimes (but, maddeningly, not always), give the message, "updating sharing previews" before quitting. I cannot figure out how to force this, however. Sometimes opening and closing Aperture several times will cause it to do this, but I can't be sure.
iTunes seems to have its own process in which it "optimizes" images for importing to the iPad. Like Aperture's mysterious "sharing previews," "optimizing" does not show up in the iTunes documentation or help files.
This process either needs to be improved, or at least documented so users can understand how to avoid these problems.

1. Some people have reported slow syncing with anything but the iPad's own USB cable (e.g. using a US cable from an iPhone/iPod). Try different cables
2. More work - disable iTunes syncing completely, then re-enable a bit at a time, e.g. one movie at a time, one playlist at a time, one photo album at a time. There are periodic reports of syncing issues caused by a bit of media that's been corrupted, and this (tedious) approach allows you to identify where the problem might be.
3. If that fails, do a clean restore back to factory settings, then progressively re-enable syncing as above.
Hope this helps

Mobile Sync Issue

Similar Messages

Maybe you are looking for