{"id":509,"date":"2013-06-14T09:00:25","date_gmt":"2013-06-14T16:00:25","guid":{"rendered":"http:\/\/www.sqldbpros.com\/?p=509"},"modified":"2014-03-03T13:40:56","modified_gmt":"2014-03-03T20:40:56","slug":"resolving-analysis-services-the-provider-sqlncli-1-is-not-registered","status":"publish","type":"post","link":"http:\/\/sqldbpros.com\/wordpress\/2013\/06\/resolving-analysis-services-the-provider-sqlncli-1-is-not-registered\/","title":{"rendered":"Resolving Analysis Services “The provider ‘SQLNCLI.1’ is not registered”"},"content":{"rendered":"

I know. While everyone else is moving on to SQL 2012 here I am upgrading a SSAS 2005 cube to SQL Server 2008 R2 Analysis Services. I can hear Garth imploring me to \"Live in the now man!<\/a>\"<\/p>\n

So as I went about the mundane task of upgrading a cube from a really old version to a not so old version: WHAM! Failure!<\/p>\n

Internal error: The operation terminated unsuccessfully.
\nServer: The current operation was cancelled because another operation in the transaction failed.
\nErrors in the back-end database access module. The provider 'SQLNCLI.1' is not registered.
\nThe following system error occured: Class not registered
\nErrors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of yaddayadda
\nErrors in the OLAP storage engine: An error occured while the dimension with the ID of blahblah
\nErrors in the OLAP storage engine: An error occured while the x attribute of the y dimension<\/p><\/blockquote>\n

Huh. Didn't see that coming.<\/p>\n

\"SQLNCLI<\/a><\/p>\n

So I dutifully tested my connection. Found it worked and started scratching my head. Then buried deep in the bowels of the MSDN forums<\/a> I spotted the answer (conveniently not labeled as the answer).<\/p>\n

\"You<\/a>
You call moving to SQL Server 2008 \"upgrading\"? It's 2013 man!<\/figcaption><\/figure>\n

It turns out that when the upgrade occurs you end up with the wrong SQL Native Provider. Open up your data source designer and examine the connection string. If you see SQLNCLI.1 you have just stumbled on the source of your problem. (Yes, I'm assuming you've got the same problem as me since that's more than likely the only reason you're still reading this masterpiece of technical literature).<\/p>\n

\"SQLNCLI.1<\/a><\/p>\n

Hit the Edit connection string button and take a look at the Provider drop down. Native OLE DB\\SQL Native Client? There's your issue.<\/p>\n

\"SQLNCLI<\/a>Hit the provider drop down and select \"SQL Server Native Client 10.0\" (or presumably SQL Server Native Client 11.0 if you're really hip).<\/p>\n

\"SQLCLNI<\/a><\/p>\n

That should be it my friend. Hit OK and process your cube and you should be good.<\/p>\n

But wait! When's the last time you watched a Wayne's World clip? How about the very one where Garth says \"Live in the now!\" Well thanks to the miracle of YouTube here it is:
\n