SSIS connection package configuration throwing error (SQLNCLI.1 is not registered) when executed from sql agent.
I'm storing the connection string in sql table (ssis_config) and the Provider=SQLNCLI10.1; but when it executes from sql agent I get the message that: "Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider SQLNCLI.1 is not registered -- perhaps no 64-bit provider is available. " What gives?
May 9th, 2011 8:16pm

If it runs outside the SQL Agent job, will the package succeed?Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 8:19pm

Yes, it indicates it is "attempting to configure from SQL server using the configuration string" and works fine. I can check the 'data sources' tab in the job step and everything looks good there too (Provider=SQLNCLI10.1).
May 9th, 2011 8:21pm

Then the culprit lies somewhere in the way the SQL Agent job is configured and I can tell you specifically it would be the account the Agent Job is running under. This account cannot access the database driver (SQLNCLI10.1) to connect to the table containing the config setting.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 8:26pm

ok, I know how to find the account the agent is running under but how do I verify what has access to the database driver?
May 9th, 2011 8:39pm

One common way of figuring out is to create a test UDL connection. Creating and Configuring Universal Data Link (.udl) Files: http://msdn.microsoft.com/en-us/library/e38h511e%28v=vs.71%29.aspxArthur My Blog
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 8:45pm

When you said it "runs fine outside of Agent", please let us know EXACTLY how you intiated package execution - on what machine, and with what tool. Second, please describe your server environment. Do you have a 32-bit or 64-bit OS? Is the SQL install 32-bit or 64-bit? Talk to me now on
May 9th, 2011 8:46pm

Environment for the sql server is is Windows Server Enterprise service pack 1, SQL server 2008 service pack 1, both 64 bit. I am able to run the package successfully from the 'run package' option in integration services from my personal machine.
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 9:00pm

Running a package on your personal machine does not equal running it on the server. Todd (I think) and I suspect you do not have the driver even installed. Arthur My Blog
May 9th, 2011 9:07pm

I think you're on to something, when I run it from integration services on the sql server I get: "Error: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_ERROR. The requested OLE DB provider SQLNCLI.1 is not registered...".
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 9:24pm

Strange that in this error message it is not Provider=SQLNCLI10.1, but SQLNCLI.1 What should it be? But in any case it is driver related, thinking may be you tinkered with the conn. string? Arthur My Blog
May 9th, 2011 10:18pm

no, ran it directly from the server from SSMS integration services. That is the message I get when it tries to read from the ssis_config table. Since it's a sql 2008 instance shouldn't it be SQLNCLI10.1?
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 10:28pm

Yes, but make sure there is no typo anywhere in the conn string, this is what I meant. Arthur My Blog
May 9th, 2011 10:52pm

That means you do not have the SQL Server Native Client provider ("SQLNCLI") installed on the client computer. Install the SQL Server Native Client tools or you can try to change the provider to "sqloledb" to use OLE DB and see if that works. http://uk.linkedin.com/in/ramjaddu
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 10:59pm

Arthur, thank you. The real issue turned out to be a leftover attribute from an earlier attempt in one of the connection strings. Thanks everybody for your help.
May 9th, 2011 11:36pm

I am having the same problem - could you tell me what leftover attribute was causing your problem?
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2011 4:40am

Thanks to all posters who have helped me solve this issue. I had a SSIS from a SQL 2005 server running on a 2008R2 server with this error. It would run fine in BIMS but not from the SQL agent. I tried NTFS permissions, 32-bit runtime, SQL agent user, provider string - all to no avail. Simply creating a new connection string in the SSIS job made all the pain disappear. Must have been a parameter incorrectly set but I'm happy now!
August 21st, 2011 5:51am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics