Skip to main content

"Can't send publish data to Analytics"

Article # 3040467 - Page views: 59


When attempting to publish a Batch Class with a Kofax Analytics for Capture (KAFC) workflow agent included, then an error is received and the Batch Class is not published successfully.
The Kofax Capture ERR Log is not shown with any related errors but, the KAFC Listener Logs are shown with a similar error.
Test Connections from the KAFC Workflow Agent and Listener are successful and the Insight Dashboard View is accessible.

Checking for errors...
Can't send publish data to Analytics

How can this issue be resolved?



IIS DefaultAppPool Identity.



The issue encountered during the Batch Class publishing can be due to the configured IIS DefaultAppPool Identity.

An example of the error in the Listener Log is below:

2017-11-14T13:19:09.0180907-05:00, Can't send publish data to Analytics:
System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Can`t open connection to database.
Login failed for user 'US\CWD1-001256$'. (Fault Detail is equal to An ExceptionDetail, likely created by
IncludeExceptionDetailInFaults=true, whose value is: AltoSoft.Insight.DBCore.AltoSoftDBException: Can`t open connection
to database. Login failed for user 'US\CWD1-001256$'. ----> System.Data.SqlClient.SqlException: Login failed for user
'US\CWD1- 001256$'.
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity,
SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword,
SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions,
SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey,
Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePoole...).

At least one case using two KAFC Listeners and a Load Balancer had a specific Application Pool Identity for the DefaultAppPool. Once that Identity was updated to match the explicit Domain User and an IIS Reset was completed, then the error was no longer received during Batch Class publishing.

Steps to Resolve:

  1. Access the Application Pools for each of the KAFC Listeners such as with INETMGR
  2. Right-Click on the KAFC Listener and select: Set Application Pool Defaults...
  3. Scroll To & Expand: Process Model
  4. Set the 'Identity' to the Domain/User or 'Network Service' & click OK to save changes
  5. Complete an IISRESET on each of the affected Listeners


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
KAFC 2.x   IIS  



Article # 3040467