Receiving the following error when trying to launch Batch Manager on a workstation
 Kdolib: Error opening database. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
DNS Bad configuration
1. This issue can be caused by a DNS issue where a workstation cannot properly resolve the IP address of the Kofax Capture server.
Until the DNS issue is fixed, you can add an entry mapping the hostname of the Kofax Capture server to the IP address in the
hosts file as a workaround.
The hosts file is normally located in the
Use a text editor, such as Notepad, to edit the
hosts file and save the changes.
2. It has been seen in at least one case the customer opened up all the ports we require through the firewall but not the security group that was controlling the access. Once the customer opened up the proper ports within the Security Group everything worked like it should.
Here are the ports involved (Both inbound and outbound need to be set up):
1433, 1434, 2424, and the Dynamic SQL Port
3. If the SQL Server service is not started the error will occur when launching any modules.
4. Check the SQL error log, it may contain errors like the one below:
FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(failed to retrieve text for this error. Reason: 1815).
This error was found to be caused by a group policy restriction on the domain preventing a local user within the local admin group from actually having full local admin rights. Make sure the installation user account actually has full local admin rights in order to install Kofax Capture.
Level of Complexity
Article # 3031320