Problem post KB937143 install Windows Server with .Net dll exposed via COM

[Tony J]

Dear Group,

We've recently applied KB937143 to a server and a bespoke dll we have
(for encryption) has suddenly stopped working. This is a VS 2005
(framework 2) dll that simply wraps some of the MD5 functions within
the .Net Framework. The dll has been exposed to COM via the usual
means. This has all been working without issue in a production
environment for well over 12 months with the dll being shared between
a .Net application and a server side classic ASP site.

The problem appears to be that KB937143 has done something to the way
dll's are exposed. The dll is shown to be still registered but all
the methods for it have just disappeared! Have tried un-registering
the dll and re-registering to no avail. Un-install KB937143 and the
COM methods will reappear!

Note that this issue only happens on servers that have IE 7 installed
- IE 6 based machines appear to be unaffected.

Any helps thoughts, or comments very much appreciated.

 

[Guest]

Hi Tony,

Note that this issue only happens on servers that have IE 7 installed
- IE 6 based machines appear to be unaffected.

Any helps thoughts, or comments very much appreciated.

Having the exact same problem with our own application - as soon as the
patch is installed on the web server (and it's running IE7) the web
application breaks horribly.

We're having to tell all our clients to un-install the patch.

Still investigating!

Graeme

 

[Guest]

hi Tony,

After 8 hours of playing and reproducing the errors, I have found two other
workarounds that resolve this issue without having to un-install the patch.

1. Change the asp.net pool security settings for your application - if you
have a dedicated pool, then make the settings there, otherwise change the
account for the default asp.net app pool to something other than the network
service

(IIS, App Pools, Properties, Identity, Pre-defined -> Change to local system

Seems to be some permissions error with the network service account (haven't
pinpointed why, but with hundreds of other users having network problems,
that doesn't surprise me)

2. Load another .aspx page before the main page ... seems to be something
funny about the asp.net framework. I can leave the app pool running as the
network service, try launch a non-existent page (e.g.
localhost/nosuchpage.aspx) and then load the application, it works fine.

Still investigating further, but at least found a workaround.

Graeme