After much swearing I figured this out. The issue was that the ASP pool was set to enable 32-bit apps which allowed the Access ODBC to work, but didn't like the 64-bit module. I solved this by placing the 64-bit version in %windir%/system32/inetsrv, and the 32-bit version in %windir%/sysWOW64/inetsrv/. Now the 32-bit and 64-bit apps call the correct modules.
As an admin that rarely touches IIS and is ashamed to admit that I'm running a server with Access as a backend, I hope this saves someone else a day's worth of aggravation. M On 07/21/2010 03:06 PM, Matt Soccio wrote: > I have a Win2k8 server with IIS7, and I'm trying to port some old ASP > code to it from a Win2k/IIS5 server. In order for the code to run, I > have created an App pool set for No Managed Code, and Classic > pipelining. Without the Cosign module, these pages work and the ASP > code executes. I have installed Cosign, and for the static pages > under my Default App pool, the Cosign module loads and pages work. > However, when I try to hit the pages under the old ASP app, the App > pool dies and I get a system message that the module failed to load. > If I set the App pool to v2.0 for the .Net framwork, the Cosign module > loads, but the code does not execute. > > Is anyone aware of a way to run really old ASP code behind Cosign on a > 2k8 server? > > Thanks > > Matt > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
