I am trying to create linked servers in SQL Server 2000 and SQL Server 2005 x64 to a Sybase Advantage database using the Advantage OLE DB Provider, 32-bit and 64-bit respectively.
I kept getting the following error when trying to browse the catalog and when performing a query with openquery from both SQL Servers:
OLE DB error trace [OLE/DB Provider 'Advantage OLE DB Provider' IUnknown::QueryInterface returned 0x80070005: Access denied.].
Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Advantage OLE DB Provider' reported an error. Access denied.
The following Stack Overflow question and answer helped me resolve this problem on SQL Server 2005 x64:
Advantage to SQL 2008 Linked Server Access Denied Error
However, I am still getting the access denied error in SQL Server 2000, despite setting Allow inprocess as suggested above.
Both linked servers use the same data source, login credentials and server options. Any help is greatly appreciated.
Try running a query in the Query Analyzer. You should see the Advantage specific OLE DB errors returned. For example:
Server: Msg 7399, Level 16, State 1,
Line 1 OLE DB provider 'Advantage OLE
DB Provider' reported an error.
[OLE/DB provider returned message:
Error 7078: The Advantage Database
Server cannot authenticate the user.
Make sure the user name and password
are correct. axServerConnect
AdsConnect]
In this case it was a bad user/password
Related
I want to access another SQL Server to import and update data of that server's database through a stored procedure.
For that I created linked server using sp_addlinkedserver.
EXEC sp_addlinkedserver
#server = N'LINKEDSERVER'
,#srvproduct=N''
,#provider=N'SQLOLEDB'
,#datasrc=N'[DB-Instance.cuprxxxlj.ap-xxxxxxx-x.rds.amazonaws.com]';
Then try to access by SQL query
SELECT *
FROM [LINKEDSERVER].[DATABASE].[dbo].[TABLE]
And getting errors like
OLE DB provider "SQLNCLI11" for linked server "LINKEDSERVER" returned message "Login timeout expired".
OLE DB provider "SQLNCLI11" for linked server "LINKEDSERVER" 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].
I had created database instance on amazon server and another is also on the amazon server and both are publicly accessible but don't know why I'm getting Server is not found or not accessible. Am I missing any server site setting or something else?
Please guide me if I am going in wrong direction.
I found the answer. The problem was an instance, I had created "Amazon RDS for SQL Server" which is currently not supporting to "Linked servers".
So I create a new AWS EC2 instance for Windows Server 2012 R2 and then I create Linked servers in it and tried to assess remotely. Now its working fine as I wanted.
Here is detailed document to Running SQL Server Linked Servers on AWS
Thanks.
Maybe try changing the timeout settings?
sp_configure 'remote query timeout', 0
go
reconfigure with override
go
This article explains in detail how to link one AWS Sql Server to another (https://aws.amazon.com/blogs/apn/running-sql-server-linked-servers-on-aws/). I am not certain what is wrong in your case, but this has a lot of steps that I do not see in your description.
And the one thing that does jump out at me is that you haven't configured any login security/access control. So unless the target server is open to the world, I would guess that you have to add that as a minimum.
When I create a linked server in SQL Server, it causes an error
Cannot create a instance of OLEDB provider SQLNCLI10 for linked server 'linked server name '(microsoft sql server error 7302)
How can I rectify this error?
The OLEDB provider may not properly installed. What you chose is the SQL Server native client. Do you have SSMS installed on server? This should come with sql native client OLE DB.
I would like to share an experience when I faced following error
Cannot create an instance of OLE DB provider "xxx.YYYY" for linked server "test". Error 7302.
I observed this message from a failed SQL Server job. On analysis it is found that Allow Inprocess was not enabled for the provider. When this is enabled, everything worked fine for me.
Server Objects --> Linked Servers --> Providers
Also refer following
"Cannot create an instance of OLE DB provider" error as Windows Authentication user
Linked Server Properties (Provider Options Page)
Configuring OLE DB Providers for Distributed Queries
I developed a school DBMS using ASP.NET and SQL Server, and I tried to transfer to another system then I installed SQL Server 2014. After going on my through my default page inserting my user and pass all that will display is :
Unable to establish connection to database.
Error information:
Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Other possible cause of this problem:
The database cannot be opened, most likely due to incorrect connection settings or insufficient security set on your database folder or file.
Can you please let know what would be issue.
Had this before, follow this guide
TLDR: Change the provider to SQLOLEDB.1
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/fab0e3bf-4adf-4f17-b9f6-7b7f9db6523c/communication-link-failure-when-connecting-to-remote-database?forum=sqlintegrationservices
SOURCE:http://stackoverflow.com/questions/6946265/ssis-package-creating-hresult-0x80004005-description-login-timeout-expired-e
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.
following error occur when i try to insert record from SQL server 2000 to SQL server 2005, while select query is running fine
OLE DB provider "SQLNCLI" for linked server "insight_db" returned message "Protocol error in TDS stream".
OLE DB provider "SQLNCLI" for linked server "insight_db" returned message "Communication link failure".
Msg 10053, Level 16, State 1, Line 0
TCP Provider: An established connection was aborted by the software in your host machine.
If the insertion is convoluted can you do it with a stored procedure? Minimise the size of the chunk of info passing between DBs. Then check the network traffic: is the link being overwhelmed with competing "stuff" ?