Error: "A configuration error has occurred" when launching the Web Console in Control Compliance Suite (CCS) 11.0
Event code: 3008
Event message: A configuration error has occurred.
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application Virtual Path: /CCS_Web
Application Path: d:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\WebPortal\
Process ID: 5088
Process name: w3wp.exe
Exception type: ConfigurationErrorsException
Exception message: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
You may run into this issue if the managed pipeline mode is incorrect. You can change this under the basic settings of the application pool. In IIS 7.0, there are two request-processing modes for application pools: Integrated mode and Classic mode. When you configure an application pool with integrated mode, IIS processes requests for managed content with the new integrated IIS and ASP.NET request processing pipeline. When you configure an application pool with classic mode, IIS continues to process requests for managed content using the separate IIS and ASP.NET request-processing pipelines. Follow the instructions below to change the managed pipeline mode in IIS 7:
Note :- This solution should be used as a workaround as CCS recommendations are to use Integrated mode and not Classic mode.
- Open Internet Information Services on the windows 2008 server. This is found under Start Menu > Control Panel > Administrative Tools > and then Internet Information Services (IIS) Manager.
- Click on the + next to your server name and then click on Application Pools.
- Locate the CCSWebApp pool and Right click on the application pool
- Click on Basic Settings.
- From the drop down menu under Managed pipeline mode: choose Classic then click on OK. (Integrated is the default mode.)
About Integrated and Classic Mode :-
Classic mode is where IIS only works with ISAPI extensions and ISAPI filters directly. This is how IIS 6 and below behaved. Using classic mode, ASP.NET is simply an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). When using classic mode the server uses two piplines to handle requests, one for native code and the other for managed code. In this mode the application doesn't take full advantage of everything IIS 7.X has to offer. Integrated mode handles all requests through a unified pipeline for IIS and is tightly integrated with ASP.NET through that same pipeline. ASP.NET sees every relevant request and manipulates things along the way rather than acting as an external plugin. With integrated mode ASP.NET runs much more efficiently in IIS and will yield greater performance for your site.
Rate this Article