Problem
Full Error Message:
An error occurred!Control(32001): Interface UtilizationClient found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: ----Server Error in '/ReporterDataSource' Application.Configuration ErrorDescription: An error occurred during the processing of a configuration file required to service this request. Please review the specificerror details below and modify your configuration file appropriately.Parser Error Message: Unrecognized attribute 'multipleSiteBindingsEnabled'. Note that attribute names are case-sensitive.Source Error:Line 136:Line 137: Line 138: multipleSiteBindingsEnabled="true" />Line 139:Line 140:Source File: C:\CA\NFA\Reporter\NetQoS.ReporterAnalyzer.WebService\web.config Line: 138Version Information: Microsoft .NET Framework Version:2.0.50727.4984; ASP.NET Version:2.0.50727.4971 --.
- NetQoS.DataSource.Client
at NetQoS.DataSource.Client.SoapHttpClientCache.EndInvoke(IAsyncResult asyncResult) at NetQoS.DataSource.Client.ReporterAnalyzerWS.EndGetEnterpriseInterfacesPercentTimeOverUtilizationReport(IAsyncResult result,Nullable`1& recordCount, Nullable`1& error) at nqPortal.Views.DataSources.ReporterViewDataSource.EndGetData() at
- nqPortal.Views.ViewBase.RetrieveAsyncData() at NetQoS.Ajax.AjaxUserControl.OnPreRender(EventArgse)
Environment:
Windows 2008 R2
Workaround:
Attempts to set the multipleSiteBindingsEnabled parameter in the C:\CA\NFA\Reporter\NetQoS.ReporterAnalyzer.WebService\web.config
file to "false", failed. Removed the entire multipleSiteBindingsEnabled="true" parameter altogether and it worked.
The customer was able to connect and sync from Performance Center and no errors in the UI.
The current workaround is to remove the entire multipleSiteBindingsEnabled="true" parameter
Additional Information:
As per the Microsoft article below, the multipleSiteBindingsEnabled feature allows you to have multiple base addresses for the same site.
Since NFA uses only one base url this feature is not necessary. We've had several incidents reported with this msg. but have not received
any reports indicating any problems after removing the parameter so it should be ok to proceed without it.