Outlook Synch problems

N

npm22

New member
Hi,

Could anybody give me any ideas as to why I get the following error codes when trying to synch with Outlook 2003 on a pc with Win XP Pro, I have installed all of the software as administrator, installed both the Palmone support pages latest Outlook 101 conduit update plus the latest desktop software,
incidently, using the conduit switcher to allow me to synch with Palms desktop software results in the hotsynch operation starting but never ending, even after a an hour or more,
I know this has been covered many times before, I have read up what I can and tried most of the suggestions, I am at a loss as what to do next, below is a copy of my latest attempts log:

thanks in advance

Trev

HotSync operation started 09/03/04 12:45:54
Outlook Notes
- Fast Sync
OK Outlook Notes
Outlook Calendar
OLERR:05-0013
OLERR:05-000F
OLERR:0D-000E
OLERR:05-001D
OLERR:0D-0004
OLERR:0D-0001
- Recovery Sync
Outlook Calendar synchronization failed
OLERR:15-0002
OLERR:06-0001
Outlook Contacts
- Fast Sync
OK Outlook Contacts
Outlook Tasks
OLERR:10-0019
OLERR:10-0017
OLERR:10-000F
OLERR:0D-000E
OLERR:10-0023
OLERR:0D-0004
OLERR:0D-0001
- Recovery Sync
Outlook Tasks synchronization failed
OLERR:15-0002
OLERR:0F-0001
OK Expense
OK Note Pad
OK Voice Memo
OK Quick Install
OK Documents To Go
OK Ultrasoft Money
OK Photos
 
The sync tasks are corrupted. Depending on where you have the most current, information, set the conduits for "X" overwrites "Y". e.g., if the most current data is in Outlook, set the calendar and tasks Outlook conduits to overwrite the handheld. This shoud reset the sync tasks and fix the problem.
 
Hi Jim,

I set the pc to overwrite the handheld and it worked a treat,

What can I say, thanks does not seem enough, I have been stuck with this problem for a quite a while now, trawling through forums for cures, and you were the only one to suggest a solution that worked,


regards


Trev
 
Trev,

You're quite welcome. What happens is that the fast sync depends on recognizing record headers that have changed. For some reason, a record header will get corrupted and the fast sync will fail. Hotsync then attempts a recovery sync but that fails also because it still tries to figure out where the corrupted record should go. By doing an overwrite sync, you tell hotsync to ignore all the previous sync tasks and write new sync tasks. This will usually exclude the record with the bad header. In many cases, this record is bous anyway so it is just "walled-off", so to speak and future hotsyncs can proceed normally.

The Palm Outlook conduits are quite buggy, especially the calendar and tasks conduits, compared to Pocket Mirror, which is a far better program but won't sync all the new PIM fields. You should download DBScan from www.pimlicosoftware.com and run it against your calendar database regularly. It seems that many of the errors come from deleted records that get stuck in the database. DBScan will fix these errors and avoid the hotsync problems you had. The tasks conduit seems to get balled up if you have too many completed tasks. A good fix is to create a completed tasks folder in Outlook and move your completed tasks to this folder. The less completed tasks you have in your Outlook tasks folder, the better.
 
Hi Jim,


It is great to be able to synch again,

but it is even better having an understanding of what went wrong in the first place,
thanks again for taking the time and trouble to help me out, you obviously know your stuff.


regards


Trev
 
I learned something too . . . what in essence to do if dbScan shows errors, or what someone can do if they DON'T have dbScan.

EXCELLENT!! I'm wondering if it isn't worth doing that once a month for the hell of it . . . kind of a "system purge" of any errant records or databases.

Cool beans, Sir Jim!
 
I've found that the only time stuff gets corrupted is when trying different programs or upon restoring from some sort of crash.

This has usually occurred when using Agendus and Datebk5 at the same time because both programs use different encodings for icon's etc. Since the last time this happened in July, I've not "purged" records or forced the sync in one direction or another.

However, if I decide to try something else (such as Life@hand) when it comes along, I will uninstall Agendus and then load the new trial program etc. Even still, corruption has occurred in the past when I've done this because of the residual encoding left in the notes field by Agendus in the Outlook field.

What I've discovered is a way to "purge" the notes:

I export the entire contents of the 3 main fields, Contacts, Calendar, and Tasks via CSV. Then I delete the notes section from the CSV file by opening Excel and delete the contents. Then resave the file in CSV format to hold the data in the same structure. Then I delete the contents of the Outlook folders. Import back in the 3 files or databases and all is clean.

The contact history of Agendus is maintained since I've backed up the corresponding "history" database of Agendus on the handheld.


Next time - I'm going to actually "trial" a program I'll use the above procedure with one little twist: I will save an "original" copy of the exports with the encoding for Agendus plus create a duplicate without the Agendus encoding. This I beleive will enable me to maintain the icon assignments etc since I can probably do a double restore....restore first to trial the new program and then uninstall it and restore back to Agendus - assuming I'm going to do so. :D
 
Pocket Mirror is advertising there Pocket Mirror Pro XT here that is supposed to sync all fields available on the T3, Zire 72 and Zire 31.....the new PIM apps.


I just love catching the Mods.......;)
 
Moose,

Dang it , I knew about PM Pro XT and just forgot all about it when writing the reply. Got me again.:) The XT version of PM Pro has proven to be a very stable conduit and bypasses all the Data Manager bugs in the Palm Outlook conduits.

Trev, happy to help. I know how frustrating it can be to not be able to sync your data. I just wish Palm tech support people would keep a database of these issues and not make people go through the install/unistall route when there's a relatively easy fix.

Paul, thank you for the kind words. I still have my trusty T665 and run DBscan once a month, It always catches at least one record with a bad header. I think anyone runing OS 5.2.8 would be well advised to run DBScan on a regular basis.

Moose, I think your plan when trying new apps is a good one, especially if you also are using programs like DateBk5 and Agendus, which can have some serious conflicts with one another. You're process gives you the the equivalent of System Restore in Windows, which is a nice thing to have when things go pear shaped. :)
 
Wouldn't it be easier to just DELETE the CalendarDB on your handheld, burn the PC version to disk, and then "replace to folder" and have PC overwrite?

I imagine the glitch might be that you're ADDING date information as you try the new app, and wouldn't know where you were at such time as you "scrapped" the new one and went back to Agendus.

I'm offering this only because dbScan caught some errant records on me, but it was my "try anything but Agendus" fling of a couple of weeks ago that left "stuff" in my NOTES section (as you point out) and corrupted something somewhere. I wonder if dbScan actually catches "notations in notes" as corruptions - or if their language goes unnoticed until "sync-time" and THEN causes problems.

I found just DELETING my to-do and calendar database and re-entering was the "final and best solution" -- until reading this thread!! That's why I thought Jim's idea was a saving grace - and yours is a good method -- a template, if you will -- to avoid problems in the first place. Kinda like keeping a file in .doc form of your Saved prefs - you always know what the "odd ones" are from then on.

All I know is that BECAUSE OF THIS, it will be along time before I "brave" something other than Agendus - and you know I'm a "throw anything on there and see" type of guy most of the time - I just can't believe anything is better than Agendus, bugs and overpricing aside.
 
Paul,

Well, I could do that and instead of burning to disk - just hotsync and then move the db file to a Temp folder and delete from handheld.....but then I'd still have the info in Outlook. That's the problem is getting the encoding stuff out of Outlook and I'm not going to delete my entire Outlook.pst file and lose "other" stuff. What you describe will work perfectly with the Palm Desktop but the structure of Outlook requires maintaining the PST file.

Also, I've found that dbscan will catch the obivious stuff but remember the @@@@@@ that Datebk5 creates as part of it's icon encoding.......dbscan won't catch those. It may not be an issue in Palm Desktop but in Outlook the quickest way I've found to clean them up is to export to CSV - open in Excel, use Excel's find and replace search engine to clean the critters out - delete the Outlook data and then reimport. Then force the desktop to overwrite the desktop as Jim outlined in his "fix". I don't think you use Outlook as I recall. Your suggestion is perfect for the Palm Desktop though.

Jim,

I just have fun with you moderators. I always get into a fun "heated" discussion with Reinbeau over in the iQue forum and "catch" her every once in awhile. She's a die hard Datebk5 fan and I'm always baiting her on Agendus vs Datebk5. I also helped her out on some automotive issues so we've become good ebuddies.

I've been a devoted Pocket Mirror fan since day one and have always used the Pro version to occassionaly back up to the Palm desktop just for checking stuff - love that feature.

I haven't used the XT version yet. The T3 has returned and may come out of moth balls depending upon what direction the company takes with regards to using Goldmine and purchasing all of us sales guys PDA's. Since Goldmine doesn't have any on board software and will sync to either PPC or Palm - I think I'll get to keep my beloved Palm OS devices. About the time the next Generation of Treo hits the streets, I may purchase it and it may use the new PIM fields based upon the rumors and then I'll need the XT.

Thanks for the thoughts on the System Restore - the only negative I see there is loss of "other" stuff between the restore points. I think that the export/import will allow new stuff to be merged with the "cleansed" old stuff when it's reimported. I think I could actually use the "other" program for - a week - and then restore the old data and it would merge to the new and I wouldn't have lost anything, except some contact history in Agendus.

I'll try this method during my next test of software, whenever that is.

BTW - I'll be in your fair city most of tomorrow setting up a customer with some of my wares.
 
Back
Top