Testing KCNS Connection Issues

ISSUE

There may be times when various issues are preventing a Kofax Capture Remote Site from connecting to the Central Site.

SOLUTION

In the case of connection issues, there is a URL with a set of parameters that can be used for troubleshooting purposes. The following URL is intended to be run on the remote site that is having the issue:


http://<host>/acis/config.acis?config=


where <host> = the Web server name or IP Address.


The parameters are represented by the following:




  • =debug (Returns information that indicates whether ASP.NET is properly registered with MS IIS.)
  • =service (This returns the KCN service(s) that are installed. If multiple services are installed, they will be cycled through as the page is refreshed. The KCNS Web Server component reads the flag files written by the KCN Services in the file cache folders, finds the next available and valid service, and returns its location. This test performs a read in the KCNS\Services folder to find the servers that are configured with the KCN service.)
  • =cache (This command reads the web.config file to determine the number of the filecache folders configured in IIS. Then it validates the path and returns the next available file cache internal identification number. The expected value is ‘0’. If there are multiple cache folders, they will be cycled through as the page is refreshed. For example, if there are three folders, ‘0’ will be displayed in the browser, then ‘1’, and then ‘2’ as the page is refreshed.)
  • =version (Returns the version of the Web server to determine compatibility)
  • =write (Uses the IIS worker thread credentials to write a file to the Upload folders)

When these URL’s fail, ASP.NET “Web server” issues could be indicated. All config.acis? commands are handled by the KCNS Web Server component, running on the Web Server machine, and NOT by the KCN Service.


URL Example:


http://<host>/acis/config.acis?config=service