Previous Next

• 04-28-2008, 9:43 PM

  tyronewillingham Joined on 04-29-2008, 1:38 AM Posts 5

  Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact I am trying to instantiate the log parser COM object from within an (old-style) ASP page. When I do this on IIS on 32-bit machine, it works fine. However, running my ASP page with Log Parser 2.2 installed on a 64-bit IIS machine, I get an error. Is there a 64-bit version of Log Parser? I have tried configuring my IIS to allow running 32 bit apps using: C:\Inetpub\AdminScripts>cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAp pOnWin64 1 When I do this and run my ASP page, I get a "Service Unavailable" error, the special App Pool I created stops, and I get an error in my Windows Event Viewer about IIS not being able to load all the ISAPI filters. Has anyone ever tried to use Log Parser within 64-bit IIS?

• 04-29-2008, 11:43 AM

  In reply to

  thomad Joined on 08-20-2002, 11:28 AM Redmond Posts 387

  Re: Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact You seem to have an ISAPI filter that can't load in a 32-Bit Application Pool. Here is what I would do: 1) Change the global setting Enable32BitAppOnWin64 back to false 2) Create a new Application Pool called ClassicASP32Bit 3) Run this AppPool as 32-Bit AppPool: cscript.exe adsutil.vbs set W3SVC/AppPools/ClassicASP32Bit Enable32BitAppOnWin64 true or appcmd set appPool ClassicASP32Bit -enable32BitAppOnWin64:true 4) configure your application to run in this AppPool: appcmd set app "Default Web Site/<your app>" -applicationPool:ClassicASP32Bit 5) Chances are that you still have the 64-Bit ISAPI filter that blocks the app from working. You can find out what filters are installed by running this command. Send the output of the command if you can't figure out which one can't be loaded. c:\windows\system32\inetsrv\appcmd list config "Default Web Site" -section:isapiFilters Hope this helps Thomas Deml Senior Program Manager Internet Information Services Microsoft Corp.

• 04-29-2008, 3:47 PM

  In reply to

  tyronewillingham Joined on 04-29-2008, 1:38 AM Posts 5

  Re: Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact Thank you for the reply Thomas. That's right, I did a bit more investigation. When I enable 32bit apps and run my application with its own app pool, I still receive an error (and my app pool stops running). I discovered that the ISAPI filter that it's conflicting with is the 64bit .Net 2.0 aspnet_isapi.dll. One problem here is I'm running on Win2003 IIS6. So I don't think I'm able to turn on/off the 32bit support on a per app-pool level. In any event, I'm not sure if there's a way around this conflict. Do you have any suggestions? Is there a way to run the asp.net 2.0 framework in 32bit mode for this IIS server? Thanks, --Dan

• 04-29-2008, 3:59 PM

  In reply to

  thomad Joined on 08-20-2002, 11:28 AM Redmond Posts 387	Re: Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact I'm sorry. For some reason I was assuming you run on Win2K8. You have to do the following on IIS6: http://support.microsoft.com/default.aspx/kb/894435   Thomas Deml Senior Program Manager Internet Information Services Microsoft Corp.

• 04-29-2008, 5:22 PM

  In reply to

  tyronewillingham Joined on 04-29-2008, 1:38 AM Posts 5

  Re: Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact Thanks Thomas. Those steps did the trick. Unfortunately in my case I am trying to do this on an Exchange 2007 server. In setting everything up to run 32bit, there is one ISAPI filter that still can't operate in 32bit mode: "Exchange OWA Cookie Authentication ISAPI Filter" (owaauth.dll). Once I remove that filter from the Default Web Site, my script works correctly. However, it seems I must sacrifice interactive OWA login as a result.

• 04-29-2008, 6:12 PM

  In reply to

  thomad Joined on 08-20-2002, 11:28 AM Redmond Posts 387

  Re: Invoking Log Parser as COM object in ASP page on 64bit IIS Reply Contact Looks like it. In IIS7 you can configure the bitness per AppPool. This works in IIS6 (adsutil command I posted in the previous post), too. It's not supported however because it is pretty challenging to configure sites in two AppPools with ISAPI filters that have the right bitness. Give it a try if you want but make a backup before you do it.   Thomas Deml Senior Program Manager Internet Information Services Microsoft Corp.