ESM Crashing in GAL preview

Home ›

ASP.NET Forums » Windows Hosting » Microsoft Solution for Hosted Exchange » ESM Crashing in GAL preview

Shortcuts

Previous Next

ESM Crashing in GAL preview

Last post 06-28-2006 12:50 PM by DmitriG. 6 replies.

Sort Posts:

ESM Crashing in GAL preview

04-03-2006, 11:35 PM

Contact

60 point Member
ekw540
Member since 03-30-2006, 8:06 AM
Posts 12

When I do a preview on the on the GAL or AL in ESM, the entire ESM crashes.

AppName: maildsmx.dll

AppVer: 6.5.7638.1

Anyone experiencing this problem?

Re: ESM Crashing in GAL preview

04-10-2006, 5:37 PM

Contact

2,535 point Contributor
jjstreic
Member since 04-28-2004, 2:09 AM
Madison Wisconsin
Posts 507

I have not seen this issue before. Does ESM crash from other servers?

Thanks

Technical Account Manager
Microsoft Communication Sector North America
This posting is provided "AS IS" with no warranties, and confers no rights. Script samples are subject to the terms at http://www.microsoft.com/info/cpyright.htm"

Re: ESM Crashing in GAL preview

06-22-2006, 2:45 AM

Contact

60 point Member
ekw540
Member since 03-30-2006, 8:06 AM
Posts 12

Yes, it does crash on both the Front-End and Back-End servers. Nothing on the Event Log.

Where else can I check the cause?

Re: ESM Crashing in GAL preview

06-28-2006, 7:37 AM

Contact

170 point Member
Marsax
Member since 06-10-2005, 9:53 AM
Posts 49

I've the same problem, we have HMC 3.5 FP1 Win2003 SP1 Exchange 2003 SP2,
when I want to preview the GAL in ESM it crashes with the stupid Win error Message:
... Exchange extension has encountred a problem and needs to close. Sorry for blabla ...

In the Application Event Log I see:
Error:
Faulting application maildsmx.dll, version 6.5.7638.1, stamp 430e738e, faulting module lcdsuiex.dll, version 2.0.5470.0, stamp 426c886c, debug? 0, fault address 0x00002bb2.

Information:
Bucket 232417753, bucket table 1, faulting application maildsmx.dll, version 6.5.7638.1, stamp 430e738e, faulting module lcdsuiex.dll, version 2.0.5470.0, stamp 426c886c, debug? 0, fault address 0x00002bb2.

Any idea?

Martin