I get this about every third time I try view the information of any user in the organization. below is the description of the error.Faulting application maildsmx.dll, version 6.5.7638.1, stamp 430e738e, faulting module cdoexm.dll, version 6.5.7638.1, stamp 430e72ec, debug? 0, fault address 0x00008209If anyone can help please let me know its getting really annoying.

While Posting it would be better if you could give us more info version of Exchange? what are you trying to view? have applied lates hotfix/patches? Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

HI, please let us know below information 1) Domain Controller OS version?2) OS version of server of exchange?3) Exchange Server version?4) This error popup on EMC or ADUC?5) This error pop-up on all servers or specific server?RegardsChinthaka

1) Domain Controller OS version? I have 7 2003 domain controllers and 2 2008 domain controllers 2) OS version of server of exchange? Server 2003 SP2 all updates applied. Not sure about the hotfixes. 3) Exchange Server version? 2003 SP2 4) This error pop up on EMC or ADUC? the error pops up saying it had to close unexpectedly and I got the info from the even viewer 5) This error pop-up on all servers or specific server? It appears to only happen on the exchange server. I have a single exchange server environment.

Issue description: ADUC crashes when attempting to open a user object on the exchange 2003 server Error Event 1000: Faulting application maildsmx.dll, version 6.5.7638.1, stamp 430e738e, faulting module cdoexm.dll, version 6.5.7638.1, stamp 430e72ec, debug? 0, fault address 0x00008209 Notes: Please follow KB 946459, which described the same symptom as yours Check info: 1. Exchange has been installed on windows server 2003, right? 2. Have any other applications been installed on the exchange server? 3. Could you disable the AV software temporarily on the exchange server, and see if the issue still occurs? Notes: Maildsmx.dll is used to open the Microsoft Exchange System Management Tools Console, if AV software try to scan exchange during that time, the same symptom will occur

How's the issue currently

Had the same issue, was caused by Symantec AV , exclude "c:\program files\Exchsrvr" Directory and it should sort your problem