Automation problem under IIS5

[GrantW]

I am using a com object to automate an application from asp called Cumulus (the com api it exposes directly is not compatible with asp ) To over come this i have wrote a com object in vb 6 to act as a buffer/interface/wrapper thing. This worked fine under IIS4, however when i moved it to IIS5 the application i am automating keeps returning the error "cannot connect to server", which is the same error i get if i try to automate the application directly from asp.

Does anyone know how IIS5 handles the com object differently than IIS4 does ?

thanks
Grant

[mlewis]

As far as I'm concerned IIS is screwy. I can't make it accept my activeX server either...