Completing the initial installation and configuration of KAFC, which includes the first launching of the ..\Insight\Admin view, an error message is received:
System.ServiceModel.ProtocolException: The content type text/html of the response message does not match the content type of the binding (text/xml; charset=utf-8).
Why is this issue encountered, and what steps are needed to resolve it and access the Insight\Admin view of KAFC?
Check for a related error message in the logs.
Error occurred while checking Insight service.
System.ServiceModel.CommunicationException: An error occurred while making the
HTTP request to https://localhost/WcfDataService/DataServiceExt.svc. This could
be due to the fact that the server certificate is not configured properly with
HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the
security binding between the client and the server. ---> System.Net.WebException:
The underlying connection was closed: An unexpected error occurred on a send. ---
> System.IO.IOException: Unable to read data from the transport connection: An
existing connection was forcibly closed by the remote host. --->
System.Net.Sockets.SocketException: An existing connection was forcibly closed by
the remote host
at System.Net.Sockets.NetworkStream.Read(Byte buffer, Int32 offset, Int32 size)
Launch the IIS Manager (
inetmgr) and browse the 'Insight' Web site — an error message may be received:
HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid
Config Error: "Cannot read configuration file due to insufficient permissions."
Review the KAFC Web.Config files for permissions.
Note: If you created an IIS website and used Custom Site Delegation to change the default delegation states, errors may occur during installation. To prevent errors, set the delegation state for modules to
IMPORTANT: When you configure Insight on IIS, the application pool (default or custom) must be .NET v4.5 (Windows Server 2012) or .NET v4.0 (Windows Server 2008).
If Windows authentication is used for any database, the application pool identity must have database access. You must have a dedicated application pool configured with the LocalSystem identity that is used by the DataFileProcessorService. If you use an Active Directory account for an application pool, it must have the same level of permissions as the NetworkService and LocalSystem identities. Also, the application pools should have the Idle Timeout set to zero, so that they always remain active.
Level of Complexity
|Kofax Analytics for Capture||2.0|