Hi,

I have an asp.net webapp that uses some unmanaged code and 3rd party pre-compiled libraries that I am pretty sure are 32-bit. We developed this on a 32-bit machine with a 32-bit development windows server. Now we are moving our web site to production where the box has Windows Server 2003 64-bit. I was getting W3SCV errors about the framework at first:

http://s18.photobucket.com/albums/b116/dtdono0/DOTNET/ISAPI_002.jpg

I followed the instructions on this blog that talks about enabling the 32-bit version of ASP.NET: http://support.microsoft.com/kb/894435

Now I get a new error and I cannot find any documentation on it.

http://s18.photobucket.com/albums/b116/dtdono0/DOTNET/ISAPI_001.jpg

I looked up the error code 0x000000c1 and got the following:

C:\Err>err 000000c1
# for hex 0xc1 / decimal 193 :
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION bugcodes.h
SQL_193_severity_15 sql_err
# The object or column name starting with '%.*ls' is too
# long. The maximum length is %d characters.
ERROR_BAD_EXE_FORMAT winerror.h
# %1 is not a valid Win32 application.
# 3 matches found for "000000c1"

This really doesn't tell me much. Any ideas?

Actually a fellow colleauge found the solution to this problem.

The new error I was getting as seen in the ss above was:

ISAPI Filter 'c:\winnt\SysWOW64\SSOFilt.dll' could not be loaded due to a configuration problem.

After going into that folder and looking at that file we saw a SSOFilt.ini file right next to it. Upon opening it we saw a documentation header revealing that this was a custom HP dll (they manage some of our servers).

By going into the C:\WINNT\system32\inetsrv\Metabase.xml file, we 'commented' out the line where the SSOFilt dll was referenced and then IIS immediately started serving html and aspx pages. This file controls what ISAPI dlls get loaded when IIS is run. You will have to stop IIS before modifying this configuration file, then restart it again after you have saved the changes.

It is almost surely the last one. You are mixing 32-bit and 64-bit components. Post to forums.iis.net or forums.asp.net to get help with this.

---

Hans Passant.

Actually a fellow colleauge found the solution to this problem.

The new error I was getting as seen in the ss above was:

ISAPI Filter 'c:\winnt\SysWOW64\SSOFilt.dll' could not be loaded due to a configuration problem.

After going into that folder and looking at that file we saw a SSOFilt.ini file right next to it. Upon opening it we saw a documentation header revealing that this was a custom HP dll (they manage some of our servers).

By going into the C:\WINNT\system32\inetsrv\Metabase.xml file, we 'commented' out the line where the SSOFilt dll was referenced and then IIS immediately started serving html and aspx pages. This file controls what ISAPI dlls get loaded when IIS is run. You will have to stop IIS before modifying this configuration file, then restart it again after you have saved the changes.

I'm also wondering why I have to use 32-bit ASP.NET in the first place. Someone told me managed .NET code developed in a 32-bit environments ports directly over to a x64 architecture directly. I think I had a dll that utilized some unmanaged calls and that is the reason it would not run in 64-bit. Are there any more caveats I should be aware of?