RE: Exch 5.5 ost synch

2002-10-24 Thread Craig A. Mills
Adams Sent: Wednesday, October 23, 2002 7:37 AM To: Exchange Discussions Subject: RE: Exch 5.5 ost synch I've seen this happen in the following situation: Users had large messages, or lots of messages with attachments AV running on the Exchange server (Trend Scanmail 3.5 in the case I've s

RE: Exch 5.5 ost synch

2002-10-23 Thread Craig A. Mills
Sent: Wednesday, October 23, 2002 7:37 AM To: Exchange Discussions Subject: RE: Exch 5.5 ost synch I've seen this happen in the following situation: Users had large messages, or lots of messages with attachments AV running on the Exchange server (Trend Scanmail 3.5 in the case I've seen) Mo

RE: Exch 5.5 ost synch

2002-10-23 Thread Craig A. Mills
-365265@;ls.swynk.com]On Behalf Of David N. Precht Sent: Tuesday, October 22, 2002 6:26 PM To: Exchange Discussions Subject: RE: Exch 5.5 ost synch Post the errors. -Original Message- From: [EMAIL PROTECTED] [mailto:bounce-exchange-224131@;ls.swynk.com] On Behalf Of Craig A. Mills Sent: M

RE: Exch 5.5 ost synch

2002-10-23 Thread Darcy Adams
I've seen this happen in the following situation: Users had large messages, or lots of messages with attachments AV running on the Exchange server (Trend Scanmail 3.5 in the case I've seen) Move users to new server - synching would fail because the AV check of the large messages would cause suffi

RE: Exch 5.5 ost synch

2002-10-22 Thread David N. Precht
Post the errors. -Original Message- From: [EMAIL PROTECTED] [mailto:bounce-exchange-224131@;ls.swynk.com] On Behalf Of Craig A. Mills Sent: Monday, October 21, 2002 12:19 To: Exchange Discussions Subject: Exch 5.5 ost synch I have two Exch 5.5 sites where every user receives synch errors

RE: Exch 5.5 ost synch

2002-10-22 Thread Dupler, Craig
I only know one thing that will induce a synch error at will. There are probably others. I'll share my recipe and maybe that will help. Recipe for indcing synch errors: 1. Set mailbox size limit low. 2. Have users fill mailboxes, including some meeting requests. 3. Have users attempt to pro