<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-1178 How to disable custom error pages on IIS</title><link>https://community.appian.com/support/w/kb/395/kb-1178-how-to-disable-custom-error-pages-on-iis</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1178 How to disable custom error pages on IIS</title><link>https://community.appian.com/support/w/kb/395/kb-1178-how-to-disable-custom-error-pages-on-iis</link><pubDate>Mon, 06 Mar 2017 18:04:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:98150603-f0f2-4d72-9205-8c5f7c0037bb</guid><dc:creator>Nick Vigilante</dc:creator><comments>https://community.appian.com/support/w/kb/395/kb-1178-how-to-disable-custom-error-pages-on-iis#comments</comments><description>Current Revision posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 6:04:13 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;p&gt;A common error observed when performing activities on the Appian UI is the following:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;An error was encountered while processing your request. Please try again.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Or&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;An internal error has occurred.

The page could not be loaded. [HTTP Code = 500] (APNX-1-4279-001)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Native browser pop-ups with such generic errors are a result of Appian being unable to interpret the information it receives from the web server as a valid JSON object that it expects. A particular scenario where this error is encountered is described in &lt;a href="https://docs.appian.com/suite/help/latest/kb/kb-1112.html"&gt;KB-1112&lt;/a&gt; where a SiteMinder configuration was causing custom HTML pages to be sent to Appian instead of JSON strings.In some cases this error may also be a result of the web server (IIS for example) hiding the actual error that Appian throws due to the fact that it has been configured to display a custom error page instead. When IIS sends this custom error page, Appian is again unable to interpret this as a valid JSON and this results in the web browser displaying the generic error text described above.&lt;/p&gt;
&lt;p&gt;Appian errors are typically displayed within a pink box popup that provide basic information as to the root cause which IIS may be unable to determine. As such it is recommended to disable this configuration.&lt;/p&gt;
&lt;p&gt;There are two sets of steps, both required, to disable the custom error pages on IIS to avoid they interfere with Appian http error code interpretation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Navigate to the site on IIS&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Error Pages&lt;/strong&gt; and then &lt;strong&gt;Edit Feature Settings&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Make sure only &amp;quot;Detailed Errors&amp;quot; is enabled.&lt;/li&gt;
&lt;li&gt;Back in the site in IIS, select &lt;strong&gt;.NET Error Pages&lt;/strong&gt; and then &lt;strong&gt;Edit Feature Settings&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Set the value to &lt;strong&gt;Off&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If this does not resolve the issue(s) by itself, then there would at least a more meaningful error message. This along with the relevant log files should be helpful in determining the root cause of the issue(s).&lt;/p&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: March 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: web browser, user interface, IIS, web server, how-to&lt;/div&gt;
</description></item></channel></rss>