Source: MSExchangeCDO Event:1639....

The description for Event ID ( 1639 ) in Source ( MSExchangeCDO ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: EX:/O=GENOVESE LICHTMAN JOBLOVE & BATTISTA/OU=MIAMI.

I receive this warning from every minute, to every five minutes, to every hour, at any time really...anybody have any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

From the little information you have provided it looks like a MAPI error. Something cannot talk to the Exchange server. I presume that this is appearing on an Exchange server?
You haven't got Outlook installed on this machine as well have you?

Otherwise need full details of the system:
Exchange server version including SP and roll ups (if applicable)
Host OS - including SP
Is the server a member server or a DC?
Anything else installed on the machine?

wdigitechAuthor Commented:
This is actually a warning I got on the file server, the Exchange server is on a different server.  I found some info on a different site, and it does look like a MAPI error.  The data  of the warning is 80004005 which is CdoE_CALL_FAILED.  The Exchange server is 2003 w/ SP1.  Outlook is not installed on either server.  The file server is a DC with 2003 server.  The file server has BlackBerry Enterprise Server on it.  This uses a different MAPI profile which I had to get from the Microsoft website.  Perhaps this is causing a problem?  I have teh BES installed on other servers and I do not get this warning.

Just to mention, not sure if this has anything to do with this.  On the Exchaneg server, there is an error I get which seems to have the same error code of 80004005.  The error is..MSExchangeFBPublish, ID 8207, "Error updating public folder with free-busy information on virtual machine MAILSERVER. The error number is 0x80004005."

Thanks in advance you for any info you can provide...
BES is where I would be looking now. If Exchange isn't installed on the machine, but the error is MAPI (And I am pretty sure it is) then you need to look at what is using MAPI on the server. If it was Outlook then I would usually suggest ripping it out totally so that the MAPI is also removed, rebooting and reinstalling.

That other error I don't think is related. Check that there is replica information for the Free/Busy system public folder in ESM.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I've also just started getting this Event 1639 on a Win2k server running Exchange 5.5.  I agree that BES appears to be involved, as we have BES pointing at mailboxes on this server also.  I've just joined a new exchange 5.5 server into the site, which is what appears to have started the events.

I recall from the original BES installation that there was a requirement to apply a CDO hotfix to the Exchange server, which is detailed in KB article Q312273.  I'm going to look into reapplying this hotfix to see if it makes any difference.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.