On Fri, 16 Sep 2005 11:08:40 -0500, Andrew Bosch <[log in to unmask]>
wrote:

>Did you configure IIS 6 to allow it to execute binaries (.exe files)? By
>default on Windows 2003 Server, IIS will not execute CGI binaries until
>you explicitly configure it to do so.

The following is an excerpt from a more detailed paper available from L-Soft
Support on how to do this:

...
IIS 6 implements a variety of restrictions on ASP, CGI, and other executable
scripts that are significantly stronger than previous versions of IIS.
You must now configure IIS to allow it to run the wa.exe script.

Select Web Service Extensions
  (make sure the tab at the bottom says 'Extended')
  The settings for all types of scripts (ASP. ISAPI, etc.) default to 
  prohibited.  Some may already be enabled, depending what you may have
  running on your web site.  There are 2 ways to grant permissions for
  the wa.exe script to run.
  
  1.  Fast (but insecure) method  (not recommended)
  
  Select the "All Unknown CGI Extensions" and click on 'Allow'
   You will receive a warning message that this is a potential security
   risk.  Click 'Yes' to allow.
   
  2.  Slower (but more secure) method   (recommended)
  
  Select the option to 'Add a new Web service extension...'
    For Extension Name enter 'exe'  (without quotes)
    For Required files: click Add and browse to find
       x:\LISTSERV\WWW\SCRIPTS\wa.exe
       Click OK
    Check the box 'Set extension status to Allowed'
  Click OK      

Sometimes it is necessary to stop/restart the Default Web Site in the 
IIS Manager at this point.  It does not hurt to do so now.
...