Microsoft IIS as the Web Server for the Web Interface: Difference between revisions
No edit summary |
No edit summary |
||
| Line 163: | Line 163: | ||
4. In case of '''HTTP Error 403.14 - Forbidden. The Web server is configured to not list the contents of this directory.''' : | 4. In case of '''HTTP Error 403.14 - Forbidden. The Web server is configured to not list the contents of this directory.''' : | ||
Verify the URL you are trying to access and test with the following URL: '''localhost/CommitCRM/CommitCRM.dll''' | Verify the URL you are trying to access and test with the following URL: '''http://localhost/CommitCRM/CommitCRM.dll''' | ||
Revision as of 09:48, 9 July 2015
Supported versions: CommitCRM 9 and up.
Uninstalling CommitCRM Web Interface Service
(Note: only if it was used as a service before)
‘CommitCRM Web Interface’ Windows service should be stopped on your server and then uninstalled (It is no longer needed when using IIS as the Web server).
You can learn how to uninstall CommitCRM Web interface service here.
Enabling CommitCRM for IIS
Rename file \CommitCRM\WebInterface\IISOFF.cmt to IIS.cmt to enable IIS for CommitCRM Web Interface.
Installing IIS on your Server/PC
In case you do not have IIS installed please refer to Microsoft Website here for full instructions on how to install, configure and test IIS on your server/PC.
Enabling ISAPI
After IIS is running successfully on your server you should add ISAPI support to it. Please visit this page on a Microsoft Website for all details.
Configuring CommitCRM Web Interface in IIS
Run Internet Information Services (IIS) Manager (Usually accessed from the Windows > Administrator Tools menu).
1. Creating an Application Pool for CommitCRM Web Interface.
1.1 Select Application Pools and then Add Application Pool:
1.2 Set the name to ‘CommitCRM Web Interface’ (exactly!), select No Managed Code and click on OK button:
1.3 Right click ‘CommitCRM Web Interface’ application pool in the list and choose Advanced Settings:
1.3.1 In order to support 32-bit application on 64-bit Windows you must set Enable 32-bit Applications to True (see the first circled option in the screenshot below).
1.3.2 Select the Identity and set it to a custom account (see the second circled option in the screenshot below).
NOTE: The user account you set here must be a privileged user.
2. Creating an application in IIS
2.1 Right click the Default Web Site (In case you do not use it for anything else) - or - create an entirely new Web Site and then right click it.
2.2 From the menu that opens choose Add Application:
2.3 In the window that opens (see below) configure the following:
2.3.1 Set Application Alias to CommitCRM (see the screenshot below).
2.3.2 Select the Application pool CommitCRM Web Interface by clicking the Select button (see the screenshot below).
2.3.3 Set the Physical path to the \CommitCRM\WebInterface folder on this server. For example: D:\CommitCRM\WebInterface (see the screenshot below).
2.3.4 Click on "Connect as..." button and set a specific user for the application.
NOTE: The user you set here must have full access rights and all privileges to the entire CommitCRM folder tree, among others.
Once the user is set, click on the button "Test Settings...". It must succeed. In case it does not, verify that the selected user has full NTFS permissions (aka the ‘Security’ tab) to the selected Physical path.
3. Enabling ISAPI Modules in IIS
3.1 Select your newly created CommitCRM application and then double-click on the "Handler Mappings" icon:
Note that CGI-exe and ISAPI-dll are disabled. To enable them, click on the link "Edit Feature Permissions...":
Select the "Execute" checkbox and click the OK button:
3.2 Select ISAPI-dll and click ‘Edit’:
The following window will open, set the value for “Executable” field to the point to file \CommitCRM\WebInterface\CommitCRM.dll on this server.
For example:
D:\CommitCRM\WebInterface\CommitCRM.dll
Click OK.
The following message may pop.
Click ‘Yes’ to allow CommitCRM:
Local Test
Inside IIS Manager, select CommitCRM application, switch to "Content View" (at the bottom), right-click CommitCRM.dll file and select "Browser".
Or
Open the browser on the server and go to the following URL: http://localhost/CommitCRM/CommitCRM.dll
As a result the login window for CommitCRM Web Interface should open in your Browser:
Troubleshooting
1. In case the following error is shown in the Browser you should grant full permissions and all access rights to the user the application is running under (Step 2.3.3 above) so they can access the local folder of Windows/Temp
2. In cases where you move CommitCRM to another server (or another folder on the same server) the following (single!) file must first be deleted - <server>\CommitCRM\WebInterface\web.config
Then configure the application again and select the relevant new physical paths.
3. In case of HTTP error 500.19 Internal Server Error with error code 0x8007007e:
Open Windows Command Prompt as Administrator and run the following command:
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
4. In case of HTTP Error 403.14 - Forbidden. The Web server is configured to not list the contents of this directory. :
Verify the URL you are trying to access and test with the following URL: http://localhost/CommitCRM/CommitCRM.dll














