Changes in IIS6

I have an ASP application that works in IIS5 but not IIS6
worker process model (it works ok in IIS6 when it is
running in IIS5 Isolation mode). The application is
failing when at a point where a COM object implementing
my business logic is using the catalyst socket controls
to talk to a TCP/IP socket on a remote machine, there is
no data being sent or received. However the same COM
object does talk to a SQL database on the same remote
machine using TCP/IP.

I have tried running the web site under a new Application
Pool and configuring that application pool to runs as the
LocalSystem account and a few other accounts in case it
is access to resources that is causing the problem but
this also did not work.

I don't think my application requires inetinfo.exe, read
raw data filters or dllhost.exe which all need IIS5
Isolation mode as documented in the online help.

Does anybody know what other changes have been made to
IIS6 that could be causing this problem as I don't want
to insist our customers configure their 2003 server to
run in IIS5 isolation mode and lose all the new enhanced
features of IIS6 ?

Cheers

Scott Robinson

v-wdxu
Tue Oct 21 23:36:25 CDT 2003

Hi Scott,

Very good question!

IIS6 has provided a very new architecture from the one in IIS5/5.1. In IIS5/5.1, the IIS take advantage of TCPIP.sys to provide web service which
lives in kernel mode. But in IIS6, Client requests and responses to them are now handled by an HTTP listener(HTTP.SYS). As it is, HTTP.SYS doesn't
replace the TCPIP.SYS driver, but rather receives data through it. Like the TCP/IP subsystem, this listener lives in kernel-mode, but implements many
new features to improve the performance of IIS. For example, This listener can manage the IIS connections, validate HTTP requests, route HTTP
requests to the correct application pool if you use worker processs isolation mode(WPIM) and cache of responses in kernel mode etc. All these new
features are designed for better performance, stable and quick response to the web requests.

From your description, the com component uses a Catalyst socket control. Since it is a 3rd party product, I am not sure how the control builds the
communication for you which may cause the component failed in WPIM mode of IIS6. Based on my experience, you can check the event viewer to
find any related error message about this issue which may tell us something about the failure. You may also need to request support of Catalyst for
more information about their control used in WPIM of IIS6.

Please feel free to let me know if you have any questions.

Does this answer your question? Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.