Post reply

Error : Connection failure. SQL Native Client is not installed correctly. To correct this, run SQL Server Setup.

  • July 11, 2017 at 4:12 am

    #338207

    Hi
    I am running Sql scripts through jenkins job. The jenkins job contains sql scripts like
    1.Sql1
    2.Sql2
    3.Sql3
    4.Sql4
    5.Sql5
    .....................................................
    n.Sqln
    Here i am getting failure error for different sql script for every time.
    "Connection failure. SQL Native Client is not installed correctly. To correct this, run SQL Server Setup."
    Can anyone help me on this why this was happening frequently and what was the solution?

  • July 11, 2017 at 4:22 am

    #1950319

    Have you tried running the SQL Server Setup like it suggests? What messages do you get when you do?

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • July 11, 2017 at 4:29 am

    #1950321

    This was production environment. We did not get this type of error before, suddenly we started getting from 2 days on wards.
    Application working fine to fetch data from the database. whenever running some sequence of SQL's through jenkins getting this error.
    FYI : we never faced before even we ran the same sequence of SQL's before.

  • July 11, 2017 at 4:41 am

    #1950323

    dudekula.kareemulla - Tuesday, July 11, 2017 4:29 AM

    This was production environment. We did not get this type of error before, suddenly we started getting from 2 days on wards.
    Application working fine to fetch data from the database. whenever running some sequence of SQL's through jenkins getting this error.
    FYI : we never faced before even we ran the same sequence of SQL's before.

    Ok, but what happens when you run the Setup? It's telling you you need to do so, however, you seem to implying that you haven't done so.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • July 11, 2017 at 5:29 am

    #1950334

    This setup was not installed recently, almost a few years back. At that time no issues. But I am facing error last 2 days onwards.

  • July 11, 2017 at 5:39 am

    #1950337

    Well, something's changed.  Maybe somebody made an update to the job?  Or perhaps the job code contains some data-dependent conditional logic such that the requirement to use SQL Native Client has only just been invoked?

    If you don't want run Setup on your live environment (and I don't blame you for your reluctance), recreate the issue on a test server and go from there.

    John

  • July 11, 2017 at 6:34 am

    #1950356

    What do those script do? Are they t-sql scripts that run on a database local to that server or do they do something else?
    Are they CmdExec steps or shelling out to the OS in some way? Is it the local server that they fail to connect to?

    Sue

  • July 12, 2017 at 12:21 am

    #1950468

    I got the issue and its fixed now. Actually, we are using sql 2012 database but the sql client tools version will be 2008R2.
    Now I uninstalled the sql 2008R2 tools and upgraded with sql server 2012 client connectivity tools and replaced the path variable with new.
    Thanks ...

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply