Skip to main content

After new Install no KC modules will open

Article # 3032341 - Page views: 1533


After new Install no KC modules will open.

When this issue occurs, an error message similar to the ones below will pop up after about 10 or 15 minutes:

(A) [3566] KdoLib: Network I/O error.: A network-related or instance-specific error occurred while establishing a connection to SQL Server.

(B) [4001] KdoLib:Error opening Database. SQL Server does not exist or access is denied (17).


The workstation or server is not able to connect to the same dynamic TCP port as the SQL Server is listening.

Kofax Capture relies upon UDP port 1434 to discover which dynamic TCP port SQL Server is listening.



The following step will help resolve the issue:

  1. Determine the dynamic TCP port SQL Server is listening on. There are a couple of options that can be used to quickly determine the dynamic TCP port being used:

Option 1: The dynamically-assigned TCP port can be found and even edited in the System Registry under the following Registry Key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\AscentCapture\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort

Option 2: On the SQL Server Configuration Manager:

- Launch SQL Server Configuration Manager.

- Under the SQL Server Network Configuration, select Protocols for <Instance Name>.

- Right-click on TCP/IP protocol and select Properties.

- Under the IP Addresses tab, scroll down to the IPAll section where it shows the “TCP Dynamic Ports” value.

  1. Once the dynamic TCP port has been determine, verify if the dynamic TCP port is open on the KC machine.

  2. Check if the workstation is able to connect to SQL Server Express / Full SQL server on the server by doing the following steps:

1. Go to Start ¦ Programs ¦ Administrative Tools.

2. Open Data Sources (ODBC 32-bit).

3. Create a new DSN. Choose SQL Server as the driver. Click the Finish button.

4. On the 'Create a new data source to SQL Server' dialog box, fill out the following:

Name: your test name

Description: optional

Server: '[ServerName]\AscentCapture' (This is your standard named instance.)

5. Click the Next button, then click on the 'Client Configuration' button. Uncheck 'Dynamically Determine Port'. Set the port to check for the dynamic port on which the server is listening.

6. Click the Next button. 

  • If you receive an error that says 'SQL Server does not exist' then that means that you can not establish the connection to your SQL Server.

  • If you receive an error that says 'Invalid user name or password' then that means that you have resolved the port issue successfully and that you have established a connection to the Server.

Ensure that a value named "[ServerName]\AscentCapture" exists under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo branch in the Registry.


If no client computers can connect to the server that is running SQL Server, there may be a server-side problem such as:

  • SQL Server is not installed on the computer that you specify in the connection string. Verify that SQL Server is actually installed on the computer that you specify in your connection string.

  • SQL Server is not started. SQL Server must be running to accept connections.

  • SQL Server is not listening on the protocol or port that you are using to connect. The Server Network Utility on the server determines which protocols SQL Server will use and on which TCP/IP ports SQL Server will listen. The Client Network Utility, an MDAC data source name (DSN), or your connection string determines which protocol and port your client uses when it connects.


Level of Complexity 



Applies to  

Product Version Build Environment Hardware








Add any references to other internal or external articles


Article # 3032341
  • Was this article helpful?