IIS and FastCGI/Registering interpreter

This page is largely a wiki-mirror of the official Microsoft docs.

Configuring FCGI.ini
To register an extension globally:

To register a site-specific extension simply add the  flag. (No angle brackets)

On success you should see:

Finishing fcgiext.ini
Documented is located by default in: C:\WINDOWS\system32\inetsrv\fcgiext.ini

The FastCGI document is formatted with a Types section that maps the FastCGI application onto the IIS site (vhost) using the specific IIS ids. And, a section that describes the application:

Registering FCGI with IIS
To add the FastCGI to a site follow these steps: Start &rarr; Administrative Tools &rarr; Internet Information Services (IIS) Manager &rarr; Right Mouse click on Web Sites folder Properties &rarr; Home Directory &rarr; Configuration &rarr; Select extension you installed &rarr; Edit &rarr; you should see C:\WINDOWS\system32\inetsrv\fcgiext.dll or the like in the executable field. Uncheck verify file exists.

Troubleshooting
ScriptMap already exists
 * Example:
 * Cause: Often old Active State CGI garbage
 * Solution: Start &rarr; Administrative Tools &rarr; Internet Information Services (IIS) Manager &rarr; Right Mouse click on Web Sites folder Properties &rarr; Home Directory &rarr; Configuration &rarr; Delete all conflicting extensions i.e. .pl, .plex, .plx, .php, .rb etc. &rarr; OK / Confirm