500.19 - Internal Server Error 64-Bit Windows 2008 SBS The requested page cannot be accessed because the related configuration..

 

To summarize this issue iMIS15 was being installed on the server and while the public view was functioning the main iMIS15 Full View site was receiving the following error message.
 
 
Server Error in Application "DEFAULT WEB SITE/IMIS15"
Internet Information Services 7.0
Error Summary  
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information  
Module
DynamicCompressionModule
Notification
SendResponse
Handler
StaticFile
Error Code
0x8007007e
Requested URL
http://YOURSERVER:80/iMIS15
Physical Path
C:\Program Files (x86)\ASI\iMIS15\net
Logon Method
Anonymous
Logon User
Anonymous
 
 
 
Most likely causes:  
·             The worker process is unable to read the applicationhost.config or web.config file.
·             There is malformed XML in the applicationhost.config or web.config file.
·             The server cannot access the applicationhost.config or web.config file because of incorrect NTFS permissions.
Things you can try:  
·             Look in the event logs for information about why the configuration files are not readable.
·             Make sure the user identity specified for the application pool, or the authenticated user, has the required permissions to access the web.config file.
Links and More Information This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
 
 
After researching this issue I was able to determine that the issue was being caused by an incompatibility within theDynamicCompressionModule used by II7. This module was utilizing a global compression schema schema that was not compatible with the our 32-bit application. This schema was being set in this case by WSUS and Sharepoint. So in plain English this boiled down to a server configuration issue brought about by these applications running an incompatible dynamic compression schema which resulted in the error seen on iMIS15.
 
In order to identify this issue I did the following:
 
1. I ran the following command from an elevated command prompt.
 
%windir%\system32\inetsrv\appcmd.exe list config -section:system.webServer/httpCompression
 

It returned something along the lines off.

 
<system.webServer>
 <httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files">
    <staticTypes>
      <add mimeType="text/*" enabled="true" />
      <add mimeType="message/*" enabled="true" />
      <add mimeType="application/javascript" enabled="true" />
      <add mimeType="*/*" enabled="false" />
    </staticTypes>
    <dynamicTypes>
      <add mimeType="text/*" enabled="true" />
      <add mimeType="message/*" enabled="true" />
      <add mimeType="application/x-javascript" enabled="true" />
      <add mimeType="*/*" enabled="false" />
    </dynamicTypes>
    <scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll" />
    <scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />
 </httpCompression>
</system.webServer>
 
As you can see the dynamicCompression settings above are the cause.
 
2. So I needed to remove this compressions scheme. Now the compression schemes are globally set and so it is not possible to simply turn it off and on from II7. So I had to disabled this compression mode, this will result in a negligible performance cost while running WSUS but has no other impacts .
 
Again from an elevated command prompt I ran the following:
 
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
 
This removed the error and allowed the iMIS15 application to function.
 
Once this was completed the error dissipated and iMIS15 web views where fully functional on the server. No changes where made to the upgraded database or the installation which where working perfectly we just had to make this server configuration change which was causing the error.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Same Error message - does not seem to work

We are getting the same error message after installing iMIS 15.1.2.5901 on this server for the first time. 

~~~~~~~~~~~~~~~~~~~~~~~~~ Results of First Statement ~~~~~~~~~~~~~~~~~~~~
<system.webServer>
  <httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compresse
d Files">
    <staticTypes>
      <add mimeType="text/*" enabled="true" />
      <add mimeType="message/*" enabled="true" />
      <add mimeType="application/javascript" enabled="true" />
      <add mimeType="*/*" enabled="false" />
    </staticTypes>
    <dynamicTypes>
    </dynamicTypes>
    <scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll" />
  </httpCompression>
</system.webServer>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It does not return a scheme named "xpress" so when I run your second Statement it indicates that it can not find it.

~~~~~~~~~~~~~~~~~~~~~~~  Results of Second Statement ~~~~~~~~~~~~~~~~~~~~
ERROR ( message:Cannot find requested collection element. )

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Any other ideas as to what is wrong or how to go about fixing this?

Thanks for posting this!

I just wanted to thank you for posting this fix. I was having this same issue and your simple fix did the trick! Suffice it to say that DynamicCompressionModule was not on my radar... Should this be in the docs somewhere for Windows Small Business Server 2008 or is this a moot point now on 15.1.3? Anyway, thanks again.

Jennifer Strawn
Accounting & Association Software Group

Another Thanks!

This was a lifesaver! I am teaching class in London, UK and all the new iParts in 15.2 were throwing errors.

Killing compression cleared the issue up. Not sure it is ideal that we can't use compression,  but the slight performance hit is worth it to  get reliability.

Many thanks.