Sync Issue with Outlook 2003

J

Jackson

I'm having a sync issue with Outlook 2003. Currently we have an exchange
2000 server and we are trying to use Outlook 2003 to filter junk mail. But
when we use "Cached Exchange mode" it keeps giving me a sync issue.



In the message it states



14:42:46 Synchronizer Version 11.0.6352

14:42:46 Synchronizing Mailbox 'Jackson'

14:42:46 Synchronizing Hierarchy

14:42:46 Done

14:42:46 Microsoft Exchange offline address book

14:42:46 0X8004010F

I tried unchecking the "download address book offline" from
tools->options->mail setup-> send and receive, but I'm still getting the
same error message. Is there anyway to fix this issue?

TIA,

Jackson
 
G

Guest

Jackson said:
I'm having a sync issue with Outlook 2003. Currently we have an exchange
2000 server and we are trying to use Outlook 2003 to filter junk mail. But
when we use "Cached Exchange mode" it keeps giving me a sync issue.



In the message it states



14:42:46 Synchronizer Version 11.0.6352

14:42:46 Synchronizing Mailbox 'Jackson'

14:42:46 Synchronizing Hierarchy

14:42:46 Done

14:42:46 Microsoft Exchange offline address book

14:42:46 0X8004010F

I tried unchecking the "download address book offline" from
tools->options->mail setup-> send and receive, but I'm still getting the
same error message. Is there anyway to fix this issue?

TIA,

Jackson
I have had this same problem and had to stop using the Junk Mail Filter. We
are running an Exchange 2000 server and I am running the Outlook 2003 client.
In order to use the Junk Mail Filter, it requires Cached Exchange Mode --
which we usually use only for laptop users.

The filter was working great, but then I would stop getting emails. It took
me a while to realize that whenever Outlook encountered a virus email, it
simply stopped synchronizing. It wouldn't skip the offending email, it would
just stop. Because I use the "mail" view, I don't see the Sync Issues
folder. By the time I discovered the issue, I had literally thousands of
synch error messages. I cannot compare them to the previous post, because I
deleted mine.

It would NOT let me delete the offending emails by logging in via OWA, so to
rectify the issue I had to alter my mailbox to stop using Cached Exchange
Mode, quit Outlook, re-launch Outlook, delete the email, change my mailbox
again, quit Outlook again, and re-launch Outlook again. I usually deleted
all of the spam during that process because although I could see the one
offending email that caused the issue, I couldn't be sure that more virus
emails were not lurking in the enormous backlog that built up. Of course,
these emails would have (and did) caused me to have to repeat the process.

I am surprised that this isn't a bigger issue. Perhaps if we were running
Exchange 2003, it wouldn't be, but I can't say. I own it, but we didn't buy
the software assurance for Server 2003, it never occured to me that the
upgrade wouldn't be able to run on the old platform.

This is the first time I have seen this issue raised anywhere -- I stopped
using the filter a while ago and I delete my spam by hand, it's easier. I
would have thought that Microsoft would have a note about it somewhere or
that more users would have experienced this very annoying issue, which ruins
what weemed to be a good spam solution. And, P.S., why can't it run in
Exchange mode? Client-side rules can.
 
D

David Elders

Had the same issue a couple of times.

At first thought that it was the Inbox Rules that had become corrupted that
was causing the problem but think now that's a red herring. I far more
suspect that its a corrupted/strange email that Outlook [or the Cached copy]
has trouble with. If you have any emails that you can't delete, that seemed
to be the cause of it for us. Simply delete these with SHIFT-DELETE and the
problem went away for us.

Spent a LOT of time researching this [to very little avail] and LOTS of
trial-and-error attempted solutions before we came to this conclusion. This
has now happened to us [since we sussed it] twice recently and on both
occasions finding and shift-deleting the offending email fixed the problem
without recourse to more 'drastic' measures...

Best of luck,


David
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top