[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

EXCDO 8208 Exchange Server 2003

I am currently receiving many EXCDO 8208 errors on my Exchange 2003 server.  Users are experiencing the inability to open up their mailboxes due to the error.  This is not apparent with all users, just some random ones and newly created accounts.  After waiting about 20 minutes or so the mailbox opens, but is still delayed if the user closes and tries to reopen Outlook.  Every time a user experiencing this issue attempts to connect to the exchange server there is a EXCDO 8208 error for that user.

Error EXCDO 8208 - Calendaring agent failed with error code 0x8000ffff while expanding recurring appointments.
I have been scouring the web looking for a possible solution to no avail.  I have tried the below references and have ensured that the databases are not included in AV scans.

http://blogs.technet.com/b/exchange/archive/2011/09/22/released-update-rollup-5-for-exchange-server-2007-sp3.aspx.

http://social.technet.microsoft.com/Forums/en-US/exchangesvrgenerallegacy/thread/c275b561-7b88-4d7a-ba16-2956a88d43a1/ 

I am not able to find anything to help.  I also noticed a 9542 error which was seen prior to this occurring.

Error 9542 - Initialization of external interface OLEDB failed; Error ecServerOOM.
I thought that MDAC might be the cause of the 9542 error and was looking into that when I left off.  I found out using the MDAC version checker that we are using MDAC 2.8 SP2 for Windows Server 2003.  I was unable to locate a download for it though.  Any help would be greatly appreciated, as this is a real headache for us.
0
necromiser
Asked:
necromiser
  • 4
  • 2
1 Solution
 
Md. MojahidCommented:
Ensure you have applied the latest Exchange 2003 Service pack. Service packs might include fixes for the EXCDO component (or other related components) and may fix the problem.

Re-register the following DLL files using the REGSVR32.EXE program: oledb32.dll, Oledb32r.dll, Msdaipp.dll, Msdaurl.dll and Msado15.dll.

Check to see if any kind of File Level Antivirus Scanner is scanning the M Drive. If so, configure the Antivirus software to exclude the M Drive (and also the Exchange Database and log directories) from a file level scan. You may have to reboot the server after making this change. Contact the Antivirus vendor for details.

If the errors persist after the above changes, then you may have to run some maintenance utilities on the Exchange 2003 databases. Please contact Microsoft Product Support Services before performing this action.

And also see the Microsoft articles

http://support.microsoft.com/kb/823159
0
 
necromiserInformation System Security ManagerAuthor Commented:
Attempted to re-register the DLL files but was presented with an error of one file not being found.

C:\Program Files\Common Files\System\Ole DB\Msdaipp.dll

What is the M drive?  We do not have an M drive, but the AV software is configured to exclude the Exchange Database and log directories from a file level scan.
0
 
Md. MojahidCommented:
Exchange Installable File System (IFS) Drive also called M Drive
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
necromiserInformation System Security ManagerAuthor Commented:
Still seeing the errors.  Executed everything stated in KB 823159.
0
 
necromiserInformation System Security ManagerAuthor Commented:
Ended up rebuilding from scratch.  Don't know what caused it either.
0
 
necromiserInformation System Security ManagerAuthor Commented:
No solutions were provided that worked.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now