Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
 
  1 links from elsewhere to this Post. Click to view. #1 (permalink)  
Old 10-11-2009, 10:44 AM
BES Activated
 
Join Date: Oct 2009
Location: Mexico
Posts: 8
Post Event id 1639

Hi everyone, I have a recurrent warning on my BES Server, it keeps showing the 1639 Event ID warning for several users:

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:
X:/O=DOMAIN/OU=OU/CN=RECIPIENTS/CN=USER.

It seems that i need the exact same version of cdo.dll in both the Exchange and the BES Server but im not really sure, is there a problem if
i have a higher version on my Exchange Server?

I'm running BES 5.0 over a Windows Server 2003 and Exchange Server 2003 SP2.
I have cdo.dll 6.5.7638.2 on my BES and cdo.dll 6.5.7654.12 on my exchange.

For me, this major versions are the same and in fact i installed the exchange admin tools SP2 on my BES and all my Exchange servers have the SP2, i suppose that the minor version changed for a microsoft update or something.

Well, any ideas about this?

Best regards
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 10-11-2009, 04:45 PM
Otto's Avatar
Proprietor
 
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,033
Blog Entries: 14
Default

Here's the update that should be applied:
MS09-003: Vulnerability in Microsoft Exchange could allow remote code execution

BES should always be the same or greater than Exchange (CDO is 'backwards compatible').

Also, I would take a look to see if you may have more than one version of CDO.dll on your system (for example, one in C:\Program Files\Exchsrvr\bin and one in C:\Windows\system32). If so, delete the one in the system32 folder and re-register the one in the bin folder.

You may also want to cross-reference the timestamp of the error in the event log entry to the associated MAGT log file for that user to see a more specific error notification in the BES logs. That may help you figure out the real issue.
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
Reply With Quote
  #3 (permalink)  
Old 10-13-2009, 10:48 AM
BES Activated
 
Join Date: Oct 2009
Location: Mexico
Posts: 8
Default

Hi Otto, thanks for the tip, i got the Microsoft update patch. Indeed, i have 2 versions of cdo, one in Program files\exchsrvr\bin and other in windows\system32 but i remember that the one in system32 is in fact the dll in use by my server.

The official tech support for Telcel in Mexico took the cdo.dll in exchsrvr\bin when i installed the MSE Admin Tools and re-register in system32, i dont know why. I asked them to make the change you told me and they say that i shouldnt move the cdo.dll in system32 cause that is the one running for my bes server.

Is there a problem if i leave that cdo.dll and just update my server with the microsoft patch? Im little bit confuse on what to do.

so, what do u think?

Thanks in advance.
Reply With Quote
  #4 (permalink)  
Old 10-18-2009, 05:26 PM
Otto's Avatar
Proprietor
 
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,033
Blog Entries: 14
Default

You'll need to update it (which updates the one in \bin) and either a) copy the cdo.dll from \bin to \system32, or b) unregister the one in \system32 and re-register the one in \bin. The reason for the \system32 location was a holdover from BES 3.x and earlier (maybe earlier versions of 4.0, but I can't recall) when it was required by the application to be in that location (it looked for a specific location rather than a registry registration location). The Telcel people probably just had their way of doing things that were leftover from the earlier days of BES. I just think that removing it from \system32 and re-registering it in \bin will allow you to do future updates without the 'one additional step' in the process. Simplifying the environment is always a good thing
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
Reply With Quote
Reply

Tags
1639, msexchangecdo

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://www.port3101.org/port-3101-bes-admin-bar-grill/2022-event-id-1639-a.html
Posted By For Type Date
Error 1639 / Page 6 This thread Refback 05-03-2011 08:35 AM

Similar Threads
Thread Thread Starter Forum Replies Last Post
Event: CHECK_EMS_MESSAGES spab Port 3101: The BES Admin Bar & Grill 1 06-02-2012 09:43 PM
Event ID 41206 Source DevMgmtConnector Pelvir Port 3101: The BES Admin Bar & Grill 9 04-29-2010 01:31 PM
KB04433 - Event log levels hdawg Featured BlackBerry KB Articles 0 06-16-2009 11:22 AM
Event ID 566 on DC from BESADMIN knottyrope Port 3101: The BES Admin Bar & Grill 5 02-06-2009 05:04 PM


All times are GMT -4. The time now is 04:58 PM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


 

SEO by vBSEO 3.3.2 PL2