Class not registered error after restoring an Analysis Services database that uses the SQL Server 2005 SQL Native Client.

sqlblog — Wed, 15 Apr 2009 18:02:00 GMT

After restoring an Analysis Services database that uses the SQLNCLI.1 SQL Native Client (SNAC) on a server which has never had SQL Server 2005 installed, an error similar to the following occurs during processing operations:

Internal error: The operation terminated unsuccessfully.

OLE DB error: OLE DB or ODBC error: Class not registered.

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'.

Errors in the OLAP storage engine: An error occurred while processing the 'Internet_Sales_2001' partition of the 'Internet Sales' measure group for the 'Adventure Works' cube from the Adventure Works DW database.

Server: The operation has been cancelled.

During execution of queries that access data contained in ROLAP storage, an error message similar to the following is returned:

Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Adventure Works DW', Name of 'Internet Sales Order Details' was being processed.

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'.

OLE DB error: OLE DB or ODBC error: Class not registered.

Server: The operation has been cancelled.

Opening the Property Sheet for the Data Source from SQL Server Management Studio (SSMS) or the Data Source Designer in Business Intelligence Development Studio (BIDS) and attempting to edit the connection string returns the following error from Connection Manager:

The specified provider is not supported. Please choose different provider in connection manager

Checking the connection string from either SSMS or BIDS, it is similar to the following:

Provider=SQLNCLI.1;Data Source=MyServer;Persist Security Info=True;User ID=sa;Initial Catalog=AdventureWorksDW

Changing the connection string to use the native OLE DB provider, similar to the following:

Provider=SQLOLEDB.1;Password=Olapolap1;Persist Security Info=True;User ID=sa;Initial Catalog=AdventureWorksDW;Data Source=MyServer

Likewise, modifying the connection string to use the SQL Server 2008 SQL Server SNAC, similar to the following.

Provider=SQLNCLI10.1;Integrated Security="";Persist Security Info=False;User ID=sa;Initial Catalog=AdventureWorksDW;Data Source=MyServer;Initial File Name="";Server SPN=""

The issue occurs because the SQLNCLI.1 provider does not ship with SQL Server 2008 and the provider name for SNAC connections changed in SQL Server 2008. The SNAC Version Provider names for SQL Server 2005 and SQL Server 2008 are:

SQL Server 2005 SQLNCLI.1

SQL Server 2008 SQLNCLI10.1

To workaround this issue, any of the following options can be used:

Edit the Data Source(s) for the database and switch from the SQLNCLI.1 provider to the SQLOLEDB.1 provider
Edit the Data Source(s) for the database and switch from the SQLNCLI.1 provider to the SQLNCLI10.1 Native Client provider.
Download and install the SQL Server 2005 SQL Native Client from the following link: http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&DisplayLang=en

John Desch

Microsoft SQL Server Escalation Engineer

General network errors (GNEs), Timeout expired, SQL Server not found or Access Denied…

sqlblog — Thu, 06 Sep 2007 16:17:00 GMT

Many times, the key to solving these errors is a network packet trace. The problem is that these errors are often thrown intermittently. This can obviously make it problematic to capture a network trace.

Network Monitor 3 (AKA Netmon3) solves this problem quite nicely. Netmon3 has the built-in ability to capture rolling traces. This allows you to start the trace and then walk away and be sure that you will have captured the error.

Here are my steps for configuring Netmon3 for a rolling trace:

Please see the steps below in order to configure Network Monitor:

1. Download Network Monitor 3

a. (http://www.microsoft.com/downloads/details.aspx?FamilyID=18b1d59d-f4d8-4213-8d17-2f6dde7d7aac&DisplayLang=en)

2. Install Network Monitor on both the client and server experiencing the problem. If you are not able to install it on the server you can install it on another machine that is connected to the same hub as the server or to the admin port of the switch that the server is on. If you go this route you must synchronize the time between the client, server, and this third machine.

3. Synchronize the clocks on the Client and SQL machines

a. At one of the machines bring up a command prompt and execute the following:

i. Net time <\\machinenamewewanttosynchwith> /set /yes

4. Turn off TCP Chimney if any of the machines are Windows 2003

a. bring up a command prompt and execute the following:

i. Netsh int ip set chimney DISABLED

5. Using the NMCap command-line utility, start the chained trace (chained = create a new capture file after reaching the “Temporary capture file size” rather than overwriting the current capture)

a. [Netmon 3 installation folder]\NMCap /network * /capture /file test.chn:100M (creates 100 MB chained files)

i. NOTE: YOU MUST USE THE .CHN EXTENSION TO CAPTURE CHAINED TRACES

ii. NOTE: The target folder must exist for NMCap to create the trace file

b. More information can be found:

i. http://blogs.technet.com/netmon/archive/2006/10/24/nmcap-the-easy-way-to-automate-capturing.aspx

ii. Or by running the command-line switch /examples

iii. Or by running the command-line switch /?

6. Get the IP addresses of the client and the server

a. ipconfig /all on the client > client.txt

b. ipconfig /all on the server > server.txt

7. Reproduce the problem, please note the exact time the problem reproduces. Also, please note the exact error message.

8. Stop the trace by hitting Ctrl-c in the command-line window

Please note that Netmon3 does not run on Windows 2000. Also, step #6 is probably the single most important step (besides actually starting the trace). If you don’t know the timestamp of the error, it is extremely difficult to find the offending packets in the trace.

Happy captures!

Posted By: Evan Basalik

Microsoft SQL Server Support Blog : SQL Connectivity

Class not registered error after restoring an Analysis Services database that uses the SQL Server 2005 SQL Native Client.

General network errors (GNEs), Timeout expired, SQL Server not found or Access Denied…