Skip to Content

Refresh of data error: "MS SQL 2014: Unable to connect. Check your data access driver

I have connected Lumira 1.31 (desktop) to a SQL server and imported a data set

Now I close down Lumira and reopen – and try to refresh the data source

Get this error

I have taken a look at the below possible solutions – and implemented it

but I does not work

All the files SAPVI and sqlsrv.sbo points the the location where the jar file is placed

I use this jar = sqljdbc41 but have also tried with sqljdbc4 and sqljdbc. All with no luck

the sbo file looks like this" xsi:noNamespaceSchemaLocation="../sbo.xsd"> $ROOT$/drivers/java/dbd_jdbcwrapper.jar Microsoft sqlsrv sqlsrv jdbc sqlsrv Query,Procedures sqlsrv,jdbc Yes No True 10 False Yes Yes False True MS SQL Server 2005 MS SQL Server 2000 MS SQL Server 7.x MS SQL Server 6.5 jdbc:sqlserver://$DATASOURCE$;DatabaseName=$DATABASE{replace44}lt;/Parameter> sqlsrv2008,sqlsrv,jdbc Always True jdbc:sqlserver://$DATASOURCE$;DatabaseName=$DATABASE{replace60}lt;/Parameter> sqlsrv2012,sqlsrv,jdbc Always Query,Procedures,Can picture-lumira-error.pngcel</Parameter> <Parameter Name="SSO Available" Platform="MSWindows">True</Parameter> </DataBase> <DataBase Active="Yes" Name="MS SQL Server 2014"> <JDBCDriver> <!-- Uncomment and edit the following lines to define java classes required by JDBC driver <ClassPath> <Path>your jar or class files directory</Path> </ClassPath> --> <ClassPath> <Path>C:\JDBC\qljdbc41.jar</Path> </ClassPath> <!-- Configuration is done for SQL Server 2012 JDBC Driver (2.0) --> <Parameter Name="JDBC Class"></Parameter> <Parameter Name="URL Format">jdbc:sqlserver://$DATASOURCE$;DatabaseName=$DATABASE{replace80}lt;/Parameter> </JDBCDriver> <Parameter Name="Extensions">sqlsrv2014,sqlsrv,jdbc</Parameter> <Parameter Name="Force Execute">Always</Parameter> <Parameter Name="Driver Capabilities">Query,Procedures,Cancel</Parameter> </DataBase> </DataBases> </DriverConfiguration>

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    May 04, 2017 at 11:36 AM

    Hi - we found the solution. The underlying MS SQL server had a faulty user. We solved it by cloning the old user. then it works

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Rene,

      I have the same issue, was this Faulty user a generic user, was the user working okay for other reporting from other sources?

      This is because my user is generic user and works ok for all our reporting from our DW, and also used for SSMS and universe connections.We have no issues with any other reporting using this user.


  • avatar image
    Former Member
    May 01, 2017 at 09:58 AM

    Hello Rene,

    Please check the TCP port number for the SQL database connection. Please go through this post: and read the answer Priyal, brand representative of Stellar data recovery.

    Good Luck!

    Add comment
    10|10000 characters needed characters exceeded