Skip to main content
Kofax

Could not open connection to SQL Server error when launching Administration Module

13136

QAID # 13136 Published

Question / Problem:

I receive the following error message when opening the Administration module:

"[3566] KdoLib: Network I/O error. A network-related or instance-specific error occured while establishing a connection to SQL Server. (provider: Named Pipes Provider, error: 40 - Could not open connection to SQL Server)".

How can I resolve this issue?

Answer / Solution:

This is a generic error message which indicates that the Kofax Capture database service could not be started.

On one occasion, starting the Kofax Capture database service generated the following error in the SQL Server ERRORLOG file:

========================================================================
2009-11-20 11:29:19.82 Server Virtual Interface Architecture protocol is not supported 
for this particular edition of SQL Server.
2009-11-20 11:29:19.82 spid5s Server name is 'XXXX\XXXXXXXXXXXX'. This is an 
informational message only. No user action is required.
2009-11-20 11:29:19.84 spid5s Starting up database 'msdb'.
2009-11-20 11:29:19.84 Server Error: 17190, Severity: 16, State: 1.
2009-11-20 11:29:19.84 Server FallBack certificate initialization failed with error 
code: 1.
2009-11-20 11:29:19.84 Server Unable to initialize SSL encryption because a valid 
certificate could not be found, and it is not possible to create a self-signed certificate.
2009-11-20 11:29:19.84 Server Error: 17182, Severity: 16, State: 1.
2009-11-20 11:29:19.84 Server TDSSNIClient initialization failed with error 
0x80092004, status code 0x80.
2009-11-20 11:29:19.84 Server Error: 17182, Severity: 16, State: 1.
2009-11-20 11:29:19.84 Server TDSSNIClient initialization failed with error 
0x80092004, status code 0x1.
2009-11-20 11:29:19.84 Server Error: 17826, Severity: 18, State: 3.
2009-11-20 11:29:19.84 Server Could not start the network library because of an 
internal error in the network library. To determine the cause, review the errors 
immediately preceding this one in the error log.
2009-11-20 11:29:19.84 Server Error: 17120, Severity: 16, State: 1.
2009-11-20 11:29:19.84 Server SQL Server could not spawn FRunCM thread. Check the SQL 
Server error log and the Windows event logs for information about possible related 
problems.
========================================================================

The source of the problem was insufficient access rights for the "NT AUTHORITY\NetworkService" Log on as account, caused by Domain Policy security settings. Switching the Log on as account to "Local System" resolved the issue in that case.

Applies to:

Product Version Category
CAPTURE 7.0 Database
CAPTURE 7.5 Database
CAPTURE 8.0 Database
CAPTURE 9.0 Database