I have SP4 (hopefully the latest AVAPI) and the latest NAV for exchange 5.5. There is a MSKB article about enabling "background scanning" as a fix for these problems. Apparently it knows if a background scan was already completed so it doesn't get delayed as much. The downside to the background scan (according to the article) is that the entire store must be rescanned after each definition update at a rate of 1GB/hr (no hardware specified). My dual 200 mhz server maybe isn't that fast and my 20GB store could possibly bog down the server for a full day each time there are new definitions loaded.
Tom -----Original Message----- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 06, 2001 12:36 AM To: Exchange Discussions Subject: RE: Is there a workaround to use both MAPI and AVAPI with NAV for Ex change 5.5? I don't think there's any good reason to use MAPI if AVAPI is working. AVAPI is supposedly infallible because it's in the middle of message flow; that is, no messages are supposed to pass unless being passed through the AVAPI. I'm not familiar with NAV, but you should be absolutely sure that you have the latest versions of NAV's code and the Microsoft AVAPI code. Earlier versions were problematic. Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer "There are seldom good technological solutions to behavioral problems." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alverson, Thomas M. Sent: Wednesday, December 05, 2001 6:43 AM To: Exchange Discussions Subject: Is there a workaround to use both MAPI and AVAPI with NAV for Ex change 5.5? When we loaded the latest NAV for exchange 5.5 it had the new AVAPI option so we had it use both MAPI and AVAPI modes. This seemed to work but several strange things began to happen. First thing we noticed is that users who tried to move a lot of messages from one folder to another would get error messages (message was moved or access denied) and only some of the messages would move. They could get around this problem by moving messages one at a time, but if they were trying to move 200 messages this would be unsatisfactory. Also, if you would try to export a users mail to a PST file, you would get the same type of error and you would end up with a PST that only had some of the messages you tried to export. We turned off AVAPI and all is good again, except I'm sure it is possible to slip a virus past the scanner if it gets too busy. Does anyone know of a workaround to make the AVAPI thing really work? Tom _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
