I have a SSIS package that runs on a SQL Server 2005 instance that currently migrates data from one SQL Server 2000 database on another server to a SQL Server 2005 database on the server running the SSIS package. The database on SQL Server 2003 is migrating to SQL Server 2008 R2. When I try to run the current SSIS package on the SQL Server 2005 database (after changing the connection strings), I receive the following error:
Error: 2011-10-20 15:09:45.85 Code: 0xC0202009 Source: SSIS_Job Connection manager "2008R2Conn" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2011-10-20 15:09:45.85 Code: 0xC020801C Source: Step [121] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "2008R2Conn" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2011-10-20 15:. The step failed.,00:00:17,0,0,,,,0
I changed the connection string from:
<Configuration ConfiguredType="Property" Path="\Package.Connections[2008R2Conn].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=TargetDB;User ID=;Initial Catalog=TargetCatalog;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue>
</Configuration>
to:
<Configuration ConfiguredType="Property" Path="\Package.Connections[2008R2Conn].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=TagetDB\Instance,<Port #>;User ID=;Initial Catalog=TargetCatalog;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue>
</Configuration>
I know I had to change the SQL Server Native Client provider b/c the original one is not included in SQL Server 2008 R2.
I set up a test instance of SQL Server 2008 R2 and ran the package from there and it worked successfully, but my client doesn't want to run the SSIS package from one of the servers with SQL Server 2008 R2 on it, so I'm stuck trying to get the SQL Server 2005 SSIS package to call the SQL Server 2008 DB. Any suggestions?
I know I had to change the SQL Server Native Client provider b/c the original one is not included in SQL Server 2008 R2.
You only need to change the SQL Native Client provider if you're going to run the package on a SQL Server 2008 box, because the SQLNCLI.1 provider doesn't ship with SQL Server 2008. (We're in the middle of a 2005->2008R2 upgrade and got bit by this.)
However, the SQLNCLI.1 provider is perfectly capable of communicating with SQL Server 2008 R2, so you should be able to run the package on your SQL Server 2005 box and have it update the data on the SQL Server 2008R2 database. (I just tried it on a Windows 2003 server running SQL Server 2005 and it worked fine.)
Related
Trying to open SQLSTD configuration file, but can't access it. Anything am doing wrong here? I have all the permission
Error message when you open SQL Server Configuration Manager in SQL Server: "Cannot connect to WMI provider. You do not have permission or the server is unreachable"
Please help
MS KB shows some cause and fixes as well
Cause:
This problem occurs because the WMI provider is removed when you uninstall an instance of SQL Server. The 32-bit instance and the 64-bit instance of SQL Server share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.
Resolution:
run below commmand in command prompt
mofcomp "%programfiles(x86)%\Microsoft SQL Server\number\Shared\sqlmgmproviderxpsp2up.mof"
Your number depends on version you are using
Microsoft SQL Server 2012 110
Microsoft SQL Server 2008 R2 100
Microsoft SQL Server 2008 100
Microsoft SQL Server 2005 90
Re-installation of sql server worked for me
I have a SQL Server 2005. I am trying to create a linked server to Azure SQL.
I set it up and tested the connection says it succeeded. However running any queries against it yields this
Enumerate columns failed for LinkedServer 'EBPCLOUD'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot obtain the schema rowset "DBSCHEMA_COLUMNS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7311)
The exact same queries work on a different box, albeit with a newer version of SQL Server.
SQL Server 2005 will not connect to Azure, 2008 R2 or higher required.
Am trying to connect SQL Server Analysis Services from PowerPivot for Excel. This was working fine and if I use existing connections it works fine. But when I try to create a new connection throw an error as below:
Failed to connect to the Server. Reason 'MSOLAP' provider is not registered on the local machine.
Version of SQL Sever am using is 2012.
Any clues?
Looks like you are missing "Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server®"
You should be able to find the component if you search for "Microsoft® SQL Server® Feature Pack" (SQL 2012 version (MSOLAP.5) here) - you then need to expand the "Install Instructions" section to find the "Microsoft® Analysis Services OLE DB Provider for Microsoft® SQL Server®" section.
(For reference, MSOLAP.4 is in the SQL Server 2008 R2 feature pack)
Is it possible to switch from 2005 to 2008 including the databases made in 2005? Or would that give an error? I have tried this but it gives me error 26.
This is the error:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: SQL
Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
are you trying to connect SQL Management Studio 2005 to a SQL2008R2 instance? explain better please;
sql server 2005 backups can be restored on 2008R2 without problems on most cases;
are both instances on the same computer? is SQL Browser started? remember that if you keep more than 1 sql server instance on the same computer it's better if you start the SQL Browser service
I am facing a strange problem during data migration. We "restored" data from 3 shards(on diff SQL Server 2005 machines) to single SQL Server 2008. We have single 2008 server now but the shards are unchanged from 2005.
Now I am trying to exec a SP on Master but I get the following error
Creating SP
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].
All shards are on SQL Server. We are not using SQLNCLI10 provider. But it's strange to see this error.
My SP use some dynamically created distributed queries in SP.
eg. Shard01.dbo.Update.....
What could possible go wrong.
Solved the problem.
My SP was using a view which was moved restored from 2005 to 2008. 2008 has different shards configurations and SQLNCLI10 was used for OPENROWSET in 2005 but not in 2008 as all the DBs were on same server.
Redefining the view solved the issue.