KB-1093 "HTTP Error 403.14 - Forbidden" error thrown when accessing Appian with IIS as a web server

Nicholas Van Dyke — Wed, 10 Feb 2021 21:44:04 GMT

Current Revision posted to Appian Knowledge Base by Nicholas Van Dyke on 2/10/2021 9:44:04 PM

Symptoms

After starting the application server and IIS, accessing any Appian URL that contains "/suite" will result in the following 403.14-Forbidden error screen:

Accessing the the root domain will successfully load the IIS screen, however.

Cause

The probable causes for this error are the following:

The ISAPI module (isapi_redirect.dll) is failing to properly load. This happens when IIS was set up with a specific version of the module, either 32-bit or 64-bit, and was later modified.
Windows Process Activation Service is not enabled.

Note: The error page may suggest to enable directory browsing, this can safely be disregarded.

Action

It is possible that the incorrect ISAPI Redirector DLL is being referenced and the ISAPI module may need to be reconfigured. To reconfigure the ISAPI module, perform the following:
1. Delete the ISAPI module set up in step 8 of the Set Up IIS documentation.
2. Once deleted, change the setting ‘Enable 32-Bit Applications’ configured in step 9 of Set Up IIS documentation to ‘False’.
3. Recreate the ISAPI module from step 12 of the Set Up IIS documentation. If you no longer get an error, this means you were using the 64-bit ISAPI Redirector DLL.
If the error still exists, enable Windows Process Activation Service and all its sub processes in "Turn Windows features on or off".

Affected Versions

This article applies to all versions of Appian using IIS as the web server.

Last Reviewed: January 2021

Tags: IIS, web server, infrastructure

KB-1093 "HTTP Error 403.14 - Forbidden" error thrown when accessing Appian with IIS as a web server

Parmida Borhani — Mon, 17 Sep 2018 20:53:41 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2018 8:53:41 PM

Symptoms

After starting the application server and IIS, accessing any Appian URL that contains "/suite" will result in the following 403.14-Forbidden error screen:

Accessing the the root domain will successfully load the IIS screen, however.

Cause

The probable causes for this error are the following:

The ISAPI module (isapi_redirect.dll) is failing to properly load. This happens when IIS was set up with a specific version of the module, either 32-bit or 64-bit, and was later modified.
Windows Process Activation Service is not enabled.

Note: The error page may suggest to enable directory browsing, this can safely be disregarded.

Action

It is possible that the incorrect ISAPI Redirector DLL is being referenced and the ISAPI module may need to be reconfigured. To reconfigure the ISAPI module, perform the following:
1. Delete the ISAPI module set up in step 8 of the Set Up IIS documentation.
2. Once deleted, change the setting ‘Enable 32-Bit Applications’ configured in step 9 of Set Up IIS documentation to ‘False’.
3. Recreate the ISAPI module from step 12 of the Set Up IIS documentation. If you no longer get an error, this means you were using the 64-bit ISAPI Redirector DLL.
If the error still exists, enable Windows Process Activation Service and all its sub processes in "Turn Windows features on or off".

Affected Versions

This article applies to all versions of Appian using IIS as the web server.

Last Reviewed: February 2017

Tags: IIS, web server, infrastructure

KB-1093 "HTTP Error 403.14 - Forbidden" error thrown when accessing Appian with IIS as a web server

Parmida Borhani — Mon, 30 Jul 2018 03:58:03 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:58:03 AM

Symptoms

After starting the application server and IIS, accessing any Appian URL that contains "/suite" will result in the following 403.14-Forbidden error screen:

Accessing the the root domain will successfully load the IIS screen, however.

Cause

The probable causes for this error are the following:

The ISAPI module (isapi_redirect.dll) is failing to properly load. This happens when IIS was set up with a specific version of the module, either 32-bit or 64-bit, and was later modified.
Windows Process Activation Service is not enabled.

Note: The error page may suggest to enable directory browsing, this can safely be disregarded.

Action

It is possible that the incorrect ISAPI Redirector DLL is being referenced and the ISAPI module may need to be reconfigured. To reconfigure the ISAPI module, perform the following:
1. Delete the ISAPI module set up in step 8 of the Set Up IIS documentation.
2. Once deleted, change the setting ‘Enable 32-Bit Applications’ configured in step 9 of Set Up IIS documentation to ‘False’.
3. Recreate the ISAPI module from step 12 of the Set Up IIS documentation. If you no longer get an error, this means you were using the 64-bit ISAPI Redirector DLL.
If the error still exists, enable Windows Process Activation Service and all its sub processes in "Turn Windows features on or off".

Affected Versions

This article applies to all versions of Appian using IIS as the web server.

Last Reviewed: February 2017

Tags: IIS, web server, infrastructure

KB-1093 "HTTP Error 403.14 - Forbidden" error thrown when accessing Appian with IIS as a web server.

Nick Vigilante — Wed, 22 Feb 2017 21:57:02 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 9:57:02 PM

Symptoms

After starting the application server and IIS, accessing any Appian URL that contains "/suite" will result in the following 403.14-Forbidden error screen:

Accessing the the root domain will successfully load the IIS screen, however.

Cause

The probable causes for this error are the following:

The ISAPI module (isapi_redirect.dll) is failing to properly load. This happens when IIS was set up with a specific version of the module, either 32-bit or 64-bit, and was later modified.
Windows Process Activation Service is not enabled.

Note: The error page may suggest to enable directory browsing, this can safely be disregarded.

Action

It is possible that the incorrect ISAPI Redirector DLL is being referenced and the ISAPI module may need to be reconfigured. To reconfigure the ISAPI module, perform the following:
1. Delete the ISAPI module set up in step 8 of the Set Up IIS documentation.
2. Once deleted, change the setting ‘Enable 32-Bit Applications’ configured in step 9 of Set Up IIS documentation to ‘False’.
3. Recreate the ISAPI module from step 12 of the Set Up IIS documentation. If you no longer get an error, this means you were using the 64-bit ISAPI Redirector DLL.
If the error still exists, enable Windows Process Activation Service and all its sub processes in "Turn Windows features on or off".

Affected Versions

This article applies to all versions of Appian using IIS as the web server.

Last Reviewed: February 2017

Tags: IIS, web server

KB-1093 "HTTP Error 403.14 - Forbidden" error thrown when accessing Appian with IIS as a web server

Nick Vigilante — Wed, 22 Feb 2017 16:57:16 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 4:57:16 PM

Symptoms

After starting the application server and IIS, accessing any Appian URL that contains "/suite" will result in the following 403.14-Forbidden error screen:

Accessing the the root domain will successfully load the IIS screen, however.

Cause

The probable causes for this error are the following:

The ISAPI module (isapi_redirect.dll) is failing to properly load. This happens when IIS was set up with a specific version of the module, either 32-bit or 64-bit, and was later modified.
Windows Process Activation Service is not enabled.

Note: The error page may suggest to enable directory browsing, this can safely be disregarded.

Action

It is possible that the incorrect ISAPI Redirector DLL is being referenced and the ISAPI module may need to be reconfigured. To reconfigure the ISAPI module, perform the following:
1. Delete the ISAPI module set up in step 8 of the Set Up IIS documentation.
2. Once deleted, change the setting ‘Enable 32-Bit Applications’ configured in step 9 of Set Up IIS documentation to ‘False’.
3. Recreate the ISAPI module from step 12 of the Set Up IIS documentation. If you no longer get an error, this means you were using the 64-bit ISAPI Redirector DLL.
If the error still exists, enable Windows Process Activation Service and all its sub processes in "Turn Windows features on or off".

Affected Versions

This article applies to all versions of Appian using IIS as the web server.

Last Reviewed: February 2017

Tags: IIS, web server