IIS7 error when calling inactive X dll from COM + activeX dll called by classic asp

I have a classic ASP application that works fine on older versions of IIS, but not on IIS7.

The ASP code calls the COM + ActiveX DLL (written in VB6) and I was able to work fine except for one program where the ActiveX DLL calls another third party DLL without ActiveX.

At this point, I get "error 800706be" .

I'm not sure what to do here. Here's what I've tried:

  • I thought it might have something to do with permissions, so to check, I provided Full Control for IIS_IUSR for non-ActiveX DLLs. This didn't fix the problem.

  • I know that a COM + component that calls a non-ActiveX DLL is not a problem because I can call other methods on that component without any problem. Then I see a component running in component services.

Can anyone help me?

Edit : 8000706BE translates to "Failed to execute remote procedure call". Not very useful, right?

Edit Hi - thanks for the comments. I got third party DLL providers to recompile as an ActiveX DLL and now it works fine on IIS7.

The third party DLL was written in Delphi - at first they tried to recompile it with the latest version of Delphi, but that also didn't work.

0


source to share


1 answer


looks weird, try this tool to help.

ADPlus is a Microsoft Product Support Services (PSS) tool that can troubleshoot any process or application that stops responding (hangs) or doesn't work (crashes). You can often use ADPlus (ADPlus.vbs) as a replacement tool for Microsoft Internet Information Server (IIS) Exception Monitor (6.1 / 7.1) and user mode process dump. These are two separate tools that PSS often uses to isolate what causes a process to stop responding (hang) or terminate unexpectedly (crash) in a Microsoft Windows DNA environment.



http://support.microsoft.com/kb/286350/

0


source







All Articles