BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 03-22-2006, 02:18 AM   #1 (permalink)
Thumbs Must Hurt
 
bpdunsta's Avatar
 
Join Date: Aug 2004
Location: Chicago, IL
Model: 8830
Carrier: Verizon
Posts: 131
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Can't Sync Calendar to Outlook 2003

Please Login to Remove!

Trying to sync my wife's new 8700c (never had a BlackBerry before) to her Outlook 2003 calendar via USB. Her company does not use a BES. Every time I try to sync, or export, I get up to appointment #83 of 522 and the kaboom! Desktop Manager shuts down.

So far, the only way I've been able to get her calendar on her BB is by syncing Outlook with her old Dell Axim and them "Importing" in Intellisync from the Axim.

Using Desktop Manager v4.1.0.8, handheld is running platform 2.0.0.120 and app version 4.1.0.284 (Bharti).

Here's what I was able to find in the PtTrace.log file:

01:08:34.759: Starting Standard Sync
01:08:34.759: Phase=10, User=2039e743: Reading data from Handheld Calendar
01:08:36.916: Finished Reading 117 Records + 0 Deletes + 0 Unchangeds for User=2039e743 from Handheld Calendar (slow sync input for resync)
01:08:36.916: Phase=20, User=2039e743: Reading data from MS Outlook Calendar
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Wed Mar 22 01:08:45 2006: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
01:09:50.634: Begin ILX Session, Source=MS Outlook, Target=Handheld
01:09:51.087:
01:09:51.087: Starting Standard Sync
01:09:51.087: Phase=10, User=2039e743: Reading data from Handheld Calendar
Wed Mar 22 01:09:51 2006: Error 11.11 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsdk \sdk_data.cpp line 670
Wed Mar 22 01:09:51 2006: Error 0.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilxtr ans\CILTRANS.CPP line 232
Wed Mar 22 01:09:51 2006: Error 4238.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsdk \Ilx_sdk.cpp line 191
01:09:51.509: Translation Unit Status: User=2039e743, rc=4238, Phase=10, TrErr=4238, SysErr=0 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilx32 \XLATEV3.cpp line 488
Wed Mar 22 01:09:51 2006: Error 4238.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\XLATE.CPP line 3038
Wed Mar 22 01:09:51 2006: Error 4238.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\XLATE.CPP line 2751
Wed Mar 22 01:09:51 2006: Error 4238.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\XLATE.CPP line 2366
Wed Mar 22 01:09:51 2006: Error 4238.4238 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\XLATE.CPP line 3483
01:09:51.525:
01:09:51.525: End ILX Session, elapsed time = 0.891 seconds

Last edited by bpdunsta : 03-22-2006 at 02:21 AM.
Offline  
Old 03-22-2006, 10:17 AM   #2 (permalink)
Talking BlackBerry Encyclopedia
 
Join Date: Nov 2005
Location: Brossard, QC
Model: 8830
Carrier: Bell
Posts: 244
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I suggest a corrupted calendar item (or items) is the problem

I would try the following

** do a big cleanup in her calendar folder first -> archive or remove unnecessary appointements **

- Create a calendar folder in another personal folder
- transfer all calendar items to the new folder
- reboot PC (to make sure outlook is completly turned off, not running in background)
- start transfering them back to the original folder *BUT*
most should not give any problems but the corrupted ones will give an error
if you where transfering more than 1, it will not tell you which one gives the error
so here is how I do it :
sort by date/subjet/whatever
transfer by groups of 5-10, then if an error occurs, i know it's in that group
transfer them back to new calendar folder and transfer them 1 by 1 to the original calendar till you find the one (or ones) that give an error

*also* or if no errors are found

Find the intellisync folder for desktop manager and rename/remove it

how? in Desktop Manager, Options, Data Folder Settings

You should see the path (should be in the users Application Data folder)
then
-close desktop manager and redirector (remove BB from usb)
-navigate to the path
-find and rename/remove "Intellisync" folder (only)
-restart desktop manager and sync


Hope it helps
__________________
Francois B

With sufficient thrust, Blackberrys can fly
Offline  
Old 07-25-2006, 10:00 AM   #3 (permalink)
New Member
 
Join Date: Dec 2005
Location: Louisville, KY
Model: 9500
Carrier: Verizon
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I've had these "Calendar Synch" problems off and on and have had to do similar things to resolve my problem. What I'd like to know is: what good are the PTrace.log and the tif.log if they don't tell you what Calendar entry is the problem...it's a big pain to repeatedly have to troubleshoot this....

Also, the same calendar entry will synch to my PocketPC device....I'm just saying...lol
Offline  
Old 07-25-2006, 10:22 AM   #4 (permalink)
New Member
 
Join Date: Dec 2005
Location: Louisville, KY
Model: 9500
Carrier: Verizon
Posts: 8
Post Thanks: 0
Thanked 0 Times in 0 Posts
Thumbs up PTrace.log and tif.log are useful!

Well, I discovered that the log files are useful after all. After reading another thread from christinah my problem was fixed. I tried to post a link to her thread but apparently I haven't posted enough for links just yet.... The thread subject is "Intellisync Crash"

The secret is the last line in the "tif.log" file...heck, i'll just cut and paste:

Quote:
Hi

Well I'm not sure if anyone on this forum has ever had a similar problem to me as no-one responded at all to my posted problem. After a lot of work, I have discovered the resolution and thought I would post the answer here anyway just in case someone encounters something similar.

I enabled advanced logging as per
EDIT - HYPERLINK REMOVED - EDIT - *GRRR*

Reading through ptTrace.log, the last lines in the log were :

Tue Dec 13 15:42:20 2005: Error 1.0 at
D:\Mav1039513.82_17\core\xlator_libs\ilxtrans\CILF IELD.CPP line 208
Tue Dec 13 15:42:20 2005: Error Description.1.0 at
D:\Mav1039513.82_17\core\xlator_libs\ilxtrans\CILR EC.CPP line 324

This made no sense and googling this error message only found one hit which
only had a 'work around', not a fix.

I then scrolled through tif.log and found the very last entry in there
relating to a particular calendar entry in Lotus Notes. I deleted that
entry, re-synched and it worked fine! Yay. I guess that was a rogue entry
or something.

Seems crazy and very user unfriendly that I need to scroll through advanced
logs etc in order to diagnose this type of problem. Surely an error message
'Bad entry in Lotus Notes' or something to that effect would have at least
got me started on the right track

Thanks - Christinah
Offline  
Old 03-22-2007, 09:02 AM   #5 (permalink)
New Member
 
Join Date: Mar 2007
Model: 6750
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello everyone,

I am having this exact same issue with one of my users. I have tried wiping the blackberry and reinstalling the desktop software to no avail. If it is a corrupt calendar entry how am I supposed to know which one it is?

Also I cannot find this tif.log file anywhere.

Currently using 6750, 4.1.1 desktop software, 3.6.1 BB OS

Using Outlook 2003 with exchange on a BES.

The blackberry desktop software is actually crashing.

Here is the users pttrace.log file:

Thu Mar 22 09:32:44 2007 -- Pumatech Intellisync Log File --

Thu Mar 22 09:32:44 2007: Error 0x80049204.-2147184124.0 at D:\users\abaranga\SDK534\maverick\se_5x_maverick\a ction_engines\Sync_Engine\EF_Implementation\SyncCo nfigManager.cpp line 1011
Thu Mar 22 09:33:44 2007: Error 15010.0 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\xlatedll.cpp line 338
Thu Mar 22 09:33:44 2007: Error 15010.0 at D:\users\abaranga\SDK534\engine\se_5x_engine\ilsyn c\xlatedll.cpp line 338
09:33:46.668: Begin ILX Session, Source=MS Outlook, Target=Handheld
09:33:47.167:
09:33:47.167: Starting One-Way Sync
09:33:47.276: Phase=10, User=3002ffa6: Reading data from Handheld Calendar
09:33:48.588: Finished Reading 0 Records + 0 Deletes + 0 Unchangeds for User=3002ffa6 from Handheld Calendar (slow sync input for resync)
09:33:48.588: Phase=20, User=3002ffa6: Reading data from MS Outlook Calendar
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:33:51 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
09:36:31.171: Begin ILX Session, Source=MS Outlook, Target=Handheld
09:36:31.546:
09:36:31.546: Starting Standard Sync
09:36:31.546: Phase=10, User=3002ffa6: Reading data from Handheld Calendar
09:36:32.889: Finished Reading 0 Records + 0 Deletes + 0 Unchangeds for User=3002ffa6 from Handheld Calendar (slow sync input for resync)
09:36:32.889: Phase=20, User=3002ffa6: Reading data from MS Outlook Calendar
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888
Thu Mar 22 09:36:33 2007: Error Bad Field Flag in Recur Blob 0x0200.0 at D:\users\abaranga\SDK534\outlook\conn_5x_outlook\o lkapi\MS_RECUR.CPP line 1888


Any ideas?
Offline  
Old 03-22-2007, 09:33 AM   #6 (permalink)
New Member
 
Join Date: Mar 2007
Model: 6750
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I figured it out it was a calendar item that had a .gif attached to it. Just sorted the calendar view so that I could see which one had the attachment deleted and tried synced it again. This time it worked.
Offline  
Old 08-12-2007, 11:28 AM   #7 (permalink)
New Member
 
Join Date: Aug 2007
Model: 8100
PIN: N/A
Carrier: t-mobile
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

FIXED my problem... mine was crapping out while syncing record 233 of 1924 Outlook calendar records. I tried the GIF work-around above but had no luck.

I finally went into Windows and created a SAVED directory under "C:\Documents and Settings\`userid`\Application Data\Research In Motion\BlackBerry\Intellisync" and moved all of the files and directories into that directory.

Then I plugged in the BB and did another sync... it didn't know who I was so it went through the dialogs of adding a new user, ie, choose Outlook and sync calendar stuff... When I synced - it friggin worked with no errors.

What a pain to debug - but at least for my particular device... it's now working. Hope this workaround is the shiz for others having Outlook calendar sync problems.

Blackberry Desktop Manager: Version 4.2.2.14 [Apr 26, 2007]
Windows XP SP2 with all critical patches
Outlook 2003 with all patches

Phacops in Dallas

Last edited by phacops : 08-12-2007 at 11:34 AM.
Offline  
Old 08-17-2007, 10:10 PM   #8 (permalink)
New Member
 
Join Date: Aug 2007
Model: 8830
PIN: N/A
Carrier: verizon
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default internal error 4238

I had the same problem this evening – much simpler solution. On the configuration tab I clicked on the “view log” button. The last email in the list was the cause – it had a dummy embedded email in it. I simply deleted the embedded link and the sync worked fine. I’d recommend either deleting or modifying the last email in the list until a successful link occurs.

Best of luck to others that get this problem.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright © 2004-2014 BlackBerryForums.com.
The names RIM © and BlackBerry © are registered Trademarks of BlackBerry Inc.