Skip to main content

SQL Server 2012 not connecting when using sqljdbc42 as the driver.



We have seen cases where when the backend database a customer uses is SQL Server 2012 and they have uploaded the sqljdbc42 driver jar file that there can be connection problems when creating logging or harvest table connections in the Management Console.

Try using the sqljdbc41 or sqljdbc4 dirvers instead.

Keywords: Kapow SQL Server 2012, connection failure, sqljdbc42, Kapow, Robotic Process Automation

  • Was this article helpful?