If it's "http:" it is going to be server side.

Adecot, your problem is entirely within the IIS configuration. Check the IIS log files for the cause of the 404 error.

The possible causes that spring quickest to mind are:
  • Missing or incorrect handler definition for ".kix" files.
  • The associated interpreter (kix32.exe) is not available on the expected path.
  • An error running the script has caused IIS to output a "helpful" error message.


You might do better asking the question of an IIS board, but before you do that ensure that you have verbose logging switched on in IIS and check the log files.