Brian Lloyd wrote:
Note that on winNT Zope also supports an alternate publishing mechanism that was developed in-house by Digital Creations. This mechanism is similar to (but not exactly like) pcgi. It runs your Zope process as a win32 service, and provides a lightweight cgi exe which knows how to communicate requests to the Zope service (the moral equivalent of pcgi-wrapper).
You should be able to install b3 on an NT machine and choose the "Install as an NT service and run with my existing web server" option.
This will install the Zope instance as a service, and prompt you for a CGI directory into which it will place the cgi exe. Pick a directory set up for cgi with IIS when prompted.
I have done this part, and the cgi-bin/WebSite.exe starts up and runs fine, giving the "! sorry not available" message when the service is not started, and the error mentioned in my original post ("no attribute argv") when the server is started The error is: Sorry, an error occurred.<p> <!-- Traceback (innermost last): File C:\Program Files\WebSite\lib\python\ZPublisher\Publish.py, line 872, in publish_module File C:\Program Files\WebSite\lib\python\ZPublisher\Publish.py, line 163, in __init__ File C:\Program Files\WebSite\lib\python1.5\cgi.py, line 795, in __init__ AttributeError: argv -->
Note that you probably have to tweak your IIS configuration to get IIS to pass authentication headers to Zope. You need to make sure that BOTH "Windows NT Challenge/Response" AND "Basic Authentication" are DESELECTED for the cgi directory where you placed the cgi exe. Otherwise, IIS will intervene on every request and try to do the authentication itself (which will fail, of course).
I have done that already, but as said above, it does not get that far. --------------- Hannu Krosing