Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Microsoft's Internet Information Server, Version 6.0 (IIS6) contains numerous security features that were not present in previous versions of IIS.

By default, CGI programs are not permitted to run on IIS6. You must configure IIS6 to permit the SAS/IntrNet CGI Tools to execute. The following list contains some tips to help you configure IIS. You must use the IIS Manager to make these modifications.

1. If your IIS6 Web server does not already have a scripts directory or a cgi-bin directory, then you need to create one. When you create this directory, be sure to check the Execute (such as ISAPI applications or CGI) box.

2. Using the IIS Manager, select your Web server name. Then, under Web Service Extensions, select Add a New Web Service Extension. For the extension, specify exe and specify the path for the broker.exe, htmSQL.exe, or shrcgi.exe file.

   Next, click on the newly added exe extension and click the Allow button (to permit the broker.exe, htmSQL.exe, or shrcgi.exe file to be executed).

3. If you want to permit all CGI programs to execute, then you can skip item 2 and do the following. Under Web Service Extensions, select All Unknown CGI Extensions and click the Allow button.

If the security is not configured correctly, then you will receive the following error message when you attempt to execute the CGI Tools:

   The page cannot be found

This error message can mean either of the following:

1. The broker.exe, htmSQL.exe, or shrcgi.exe file is not present at the URL that you specified in your Web browser.

   OR

2. The broker.exe, htmSQL.exe, or shrcgi.exe file is present at the URL that you specified, but the IIS6 security is not configured to permit the CGI Tools to be executed. As a result, access is denied.

If you have difficulty determining the cause of the The page cannot be found error message, then it might be helpful to check the IIS log file. This file is usually located at a path that is similar to the following:

   C:\WINDOWS\system32\Logfiles\W3SVC1\*.log

Check the lines in the log file that reference the broker.exe, htmSQL.exe, or shrcgi.exe file. If the lines end with 404 2 1260, then the file was present, but IIS denied access for security reasons. If the lines end with 404 0 2, then the file was not found (not a security issue).

Operating System and Release Information