How to troubleshoot SQL error [3566] & open applications in Kofax 10

I recently worked with a customer who was receiving the error below on a Client/Server installation with a standalone SQL instance (not built-in):

[3566] KdoLib: Network I/O error: 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. (Provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (-1)

After performing a clean install of Kofax 10 on a new workstation, they were unable to open Batch Manager, Administration, etc. The process could be seen in Task Manager, but the window would not open, and after about 20 minutes would show the error above.

To resolve this we first tested the connection to the SQL server using a .udl file. This can be done by creating a blank text file, then renaming the extension to .udl.

Open this new Data Link and fill in the fields for your SQL server and test the connection. If you do not get a success, verify that your server name, login, firewall, etc. are configured properly to access the server. Continue reading

An Explanation of SQL Joins

Recently I had to analyze several Stored Procedures and Views in SQL 2008 to find out why a process had stopped working. Many of you have had to do the same thing and this stuff gets complicated. So along with my several pages of notes I found this article particularly useful. This is the best representation and explanation of SQL Joins I have found and wanted to share.

http://blog.codinghorror.com/a-visual-explanation-of-sql-joins/

Andrew Skovran
Support Engineer
ImageSource, Inc.

How to fix an error when configuring Active Directory Federation Services

While recently working to deploy an Active Directory Federation Services (ADFS) instance on a Server 2012 system, I ran into an issue. When I tried to do the initial configuration of the ADFS service from the ADFS console, there was an error that said the Windows Internal Database (WID) could not be started. This WID service is required for the ADFS service to function. I have included the text from the error below, which is very simple to fix once you know the root cause. Continue reading