Troubleshooting Web Server Setup

If you have installed a web server prior to installing InterSystems IRIS, then the InterSystems IRIS installation process will configure the web server automatically. This section provides some troubleshooting steps for addressing web server setup.

Troubleshooting Windows and IIS

HTTP Redirection and WebSocket Protocol

Some InterSystems IRIS features require that the Windows HTTP Redirection and WebSocket Protocol features are turned on. HTTP Redirection is used for links to relevant documentation within the Management Portal. WebSocket Protocol is used to enable the debugging tool in the VS Code IDE. By default, these remain off even when IIS is turned on. To turn on HTTP Redirection:

Open the Windows Features manager by searching for Turn Windows features on or off or by opening the Control Panel and selecting Programs > Programs and Features > Turn Windows features on or off.
Ensure Internet Information Services > World Wide Web Service > Common HTTP Features > HTTP Redirection is selected.
Click OK.
For details on using this feature to redirect links, see Redirect Documentation Links.

To turn on WebSocket Protocol:

Open the Windows Features manager by searching for Turn Windows features on or off or by opening the Control Panel and selecting Programs > Programs and Features > Turn Windows features on or off.
Ensure Internet Information Services > World Wide Web Service > Application Development Features > WebSocket Protocol is selected.
Click OK.

Restarting IIS

You must restart the IIS web server for some changes to take effect.. It is recommended that you restart your web server after making any changes to the web server or Web Gateway configurations, including after the installation process is completed. To restart the IIS web server:

Using a Windows command line interface, run the following command to stop the web server:
```
sc stop W3SVC
```
After the web server stops, run the following command to start the web server again:
```
sc start W3SVC
```

Repairing or Modifying Your Instance

You can initiate auto-configuration of the IIS web server after installation in the event it was skipped during the installation process. To do so, run an installation using the same executable file you originally used to install the instance. Choose to Repair or Modify depending on whether the CSP for IIS component was included in your initial installation:

If the CSP for IIS component was originally installed, but IIS was either not configured or the configuration was manually deleted, you can run a Repair to initiate auto-configuration of the IIS web server.

Important:

The only way to include the CSP for IIS component without auto-configuring your instance is to specify CSPSKIPIISCONFIG=1. This flag can only be specified for an unattended installation, or when executing the installation file from the command line. If you did not include this flag during your installation, you should not run a Repair. You can instead Modify the instance to initiate auto-configuration.

If CSP for IIS was not included in your original installation, you can Modify your installation and select the CSP for IIS component. This will cause the installer to initiate auto-configuration of the IIS web server.

In either case, after the installation finishes you will need to perform additional configuration steps in order for all features to work properly:

To enable Management Portal access, set the CSPSystem account credentials for your instance within its server access profile. For details, see Step 6 of Automatic Configuration Behavior.
To enable the Launcher links, you need to configure the following InterSystems IRIS Server Manager parameters:
- Set Web Server Port to the port number your web server is using (80 by default).
- Set CSP Server Instance to the lowercase version of your instance name (for example, iris).

Changing the InterSystems IRIS Language