MSX2003 SP2 and IE7: ESM Help causes app crash

[pete...@gmail.com]

Hello,

System:
Windows 2003 SP1, Exchange 2003 SP2, IE 7, all Microsoft updates [as of
today, 10.11.06].

Problem:
>From Exchange System Manager, attempting to access 'Help, Help Topics'
or any context Help causes the application to crash.
One of three errors results - they all generate an App Event 1000:

app: contentfilter.dll; module hhctrl.ocx; address 0x00013368
app: maildsmx.dll; module unknown; address 0x00d2e6b1
app: exadmin.dll; module unknown; address 0x00d0fd11 (varies)

This happens on 2 servers - I think this it's due to IE7:
the reference to hhctrl.ocx; MSX 2003SP2 servers without IE7 are
unaffected.

I've seen one post re: this problem (though my server isn't SBS, like
theirs):
http://tinyurl.com/yhdefk

Has anyone else encountered this problem/got any tips, please?

Cheers,
Pete.

[eson...@gmail.com]

I've encountered this exact problem on 3 machines. The problem does not
exist on vanilla Exchange, but after installing sp2 its there. After
uninstalling internet explorer 7 though, the problem goes away. Seems
to me like there need to be a hotfix..

/Jonas

[Pete Witt]

Hi Jonas,

It seems we're not alone...

I originally posted this on Daniel Petri's site
[http://www.petri.co.il/forums/showthread.php?t=11155]. That posting has some
additional info:
'On expanding Administrative Groups, 'main site', Folders & selecting
'Public Folders', I get the following error:
Exchange System Manager:
The operation completed successfully.
Facility: Win32
ID no: c0070000
Responding 'OK' (the only option) continues and everything seems fine.'

I've just seen a similar report here: 'Exchange System Manager Error c0070000'
http://tinyurl.com/yd7otu
[http://groups.google.com/group/microsoft.public.exchange.admin/browse_thread/thread/6052af02b11ed910/298e2afb9db7585b].

Unfortunately, the only suggestion I've seen is to uninstall IE7: tried that
on a test server and it does fix both errors (ESM Help and Public Folder).
I'm not keen on repeating this on production servers, though.

Anybody (MVPs/Microsoft employees) got any other suggestions, please?

Cheers,
Pete.

[Ziv]

Thanks you, I have uninstalled IE7 from the exchange server and both help
problem and public folders problem have gone.
Now you must remember to disable auto update for installing IE7 again.
http://www.microsoft.com/downloads/details.aspx?FamilyId=4516A6F7-5D44-482B-9DBD-869B4A90159C&displaylang=en

Go to this site to download the IE7 blocker tool.
Download it and it will ask you were to extract it to. Goto CMD and run
IE70Blocker.cmd /B
If you won't use the /B it won't block.

All the best

[Pete Witt]

Thanks for the feedback, Ziv.

We had previously applied the IE7 blocker through a Domain Group Policy.
However, I later configured a number of servers to use WSUS, which ignores
the blocker.
[To be fair, this is mentioned in the blocker FAQ].

Whilst I could uninstall IE7 and either not use WSUS or re-configure it to
decline IE7, I think Microsoft should fix the problem.
I assume they'd (generally) suggest we upgrade to IE7, so they ought to
ensure it doesn't 'break' other components.

Cheers,
Pete.

[Pete Witt]

Hello,

I also posted this problem on Daniel Petri's (excellent) site/forum:
http://tinyurl.com/2qudfz

A contributor recently posted information about an upcoming article (as yet
unavailable): http://support.microsoft.com/kb/932513

I tried the workaround on a test (not production) system and can confirm ESM
no longer crashes on accessing its Help system.

Cheers,
Pete,
Royal National Institute of the Blind.