How to confirm if SQL Server 2005/2008 does have the TCP/IP protocol enabled.
A common issue when trying to configure Kofax RPA to work with a new installation of SQL Server 2005/2008 is that by default the TCP/IP protocol is NOT enabled for a new SQL Server installation.
How to confirm if the TCP/IP protocol has been enabled for a SQL Server 2005/2008 server.
- Start your SQL Server 2005/2008 service so it is running.
- Open a command prompt window and type the following command: netstat -aon | find "LISTEN"
What I want to know is whether Port 1433 is listed as a LISTENING port on your computer in the same way it is shown here:
c:\>netstat -aon | find "LISTEN"
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 416
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:554 0.0.0.0:0 LISTENING 3668
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 5444
TCP 0.0.0.0:2002 0.0.0.0:0 LISTENING 1864
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5701 0.0.0.0:0 LISTENING 9924
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:10067 0.0.0.0:0 LISTENING 2132
NOTE: The rest of the list was truncated as the entry I'm after is the one for "0.0.0.0:1433".
Unless you changed the default TCP/IP port for your SQL Server 2008 instance, the Listening Port for incoming connections is 1433. Do you see this port listed?
You've selected a different TCP Port to be used for this SQL Server 2008 instance. You will need to use the SQL Server Management Studio (which may require working with your local Database Administrator) to confirm the current configuration.
It is even possible that the [TEST CONNECTION] button under SETTINGS will work, but it won't be possible for Design Studio or RoboServer to actually connect and talk to the SQL Server database because the test that that performs is different than actually making a full login with credentials.
Keywords: Kapow, Robotic Process Automation, Kapow 8.3.x, Kapow 9.0.x, Kapow 9.1.x, SQL, database, connection
Level of Complexity
Add any references to other internal or external articles
Article # 3035196