Returned message login timeout expired linked server

OLE DB provider "SQLNCLI" for linked server "SERVER" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "SERVER" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].

Hi Lukesh,
According to your description, you cannot connect to one of your linked servers with the error "Login timeout expired", right?
If in this case, please follow the troubleshooting methods below on the linked server.
Select "Using both TCP/IP and named pipes" in SQL Server 2005 Surface Area Configuration.
In SQL Server Configuration Manager, make sure that TCP/IP is enabled for the Network protocol.
If you turn on the Firewall, make sure the TCP port 1433 is in the Firewall exception list.
Reference
http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/
If the issue persists, please provide us more information, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

The adapter "SQL" raised an error message. Details "Login timeout expired".

Hi All
Please help me to understand "Login timeout". All feedback is welcome.
BizTalk Server 2009 on Windows Server 2008 R2 64 bit
SQL Server 2008 SP1 64 bit
BizTalk Adapter Pack 2.0
Event Viewer -> Windows Logs -> Application
The adapter "SQL" raised an error message. Details "Login timeout expired".
The adapter failed to transmit message going to send port "ALL.Exceptions" with URL "SQL://xxxxxxxxx/EsbExceptionDb/". It will be retransmitted after the retry interval specified for this Send Port. Details:"Login timeout expired".
Regards
Steve

Hi Abhishek,
Thank you for your input.
I found errors in the Table [EsbExceptionDb].[dbo].[Fault] relating to the write to the target Oracle database
Microsoft.ServiceModel.Channels.Common.MetadataException: Metadata resolution failed for OperationId:ATHENA/Table/WO_ADDITIONAL/Delete ---> System.TimeoutException: Timeout Expired at
The BizTalk send port timeout has been increased from 1 minute to 30 minute and all is well
Regards
Steve

2008 r2 Copy Database Wizard Error code 0x80004005 (login timeout expired).

While on copy database wizard, step Configure the package I
get this error:
while trying to find a folder on sql an ole db error was encountered with error code 0x80004005 (login timeout expired).
If I try to run it any way, I got the following in the Execute stage:
the job failed. check the event log on the destination server for details
In the destination server, job history:
Message
Executed as user: WORKGROUP\servername$. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1
for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:26:57 PM Could not load package "package name omitted" because of error 0xC0014062. Description: The LoadFromSQLServer method
has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. Source: Started: 3:26:57 PM Finished: 3:27:44 PM Elapsed: 47.83 seconds. The package could
not be loaded. The step failed.
I check the job permission with the integration service connection. try with default and with db_ssisadmin.
other info:
Source: Other SQL Server Version, Microsoft SQL Server Enterprise Edition , Build 1617, Microsoft Windows NT 6.0 (6002) NT INTEL X86
Destination: Other SQL Server Version, Microsoft SQL Server Data Center Edition (64-bit) , Build 1600, Microsoft Windows NT 6.1 (7601) NT
x64 Using SMO online transfer

Hi kexinger,
This issue might be caused by the insufficient permission for the SQL Agent account, please check the SQL Agent service account has sufficient permissions to the various folders. For detail information, please take a look at the following article:
http://mattsql.wordpress.com/2014/01/06/quick-tip-could-not-load-package-xxx-because-of-error-0xc0014062/
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Login timeout expired-2EETW169 no connect possible:"DBMS = MSSQL" DBNAME=""

Hi, SDN fellows.
I finished applying SPs for Solman Manager 7.0 (updated to Solman 7.1 EHP1 - just the Java Stack with JSPM). Then, I decided to start install SAP ECC 6.0 IDES in D drive (solman currently installed in C drive). When I ran the SAP ECC installer till the screen where it require Solution Key, I stopped the process due to invalid solution key provided.
After that, my Solman system became not able to connect to MS SQL server anymore. Here is the trans messages I got from "R3Trans -d".
Not sure what isthe root cause, but I found couple messages maybe the leads to root cause.
I wonder why the DBNAME become empty on this line: 2EETW169 no connect possible: "DBMS = MSSQL                            --- SERVER = 'MYSERVER101' DBNAME = ''".
These message also shown that this maybe login related issue:
4 ETW000 [     dev trc,00000] CopyLocalParameters: dbuser is 'dbo'                                      19 0.004714
4 ETW000 [     dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000
LOG BY0=>Login timeout expired [dblink#4 @ 433]
Thanks for advices,
KC

4 ETW000                                                                                45 30.272192
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 30.272209
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000                                                                                63 30.272272
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 20 30.272292
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000                                                                                42 30.272334
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 30.272351
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000                                                                                38 30.272389
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 30.272406
4 ETW000 [     dev trc,00000] Using Provider SQLNCLI                                                 10214 30.282620
4 ETW000 [     dev trc,00000] OpenOledbConnection: MARS property was set successfully.                  75 30.282695
4 ETW000 [     dev trc,00000] Sun Jul 24 07:23:58 2011                                             15172939 45.455634
4 ETW000 [     dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000                                                                                41 45.455675
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000                                                                                43 45.455718
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 45.455735
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000                                                                                75 45.455810
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 27 45.455837
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000                                                                                43 45.455880
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 16 45.455896
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000                                                                                38 45.455934
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 45.455951
4 ETW000 [     dev trc,00000] failed to establish conn to np:(local).                                 6519 45.462470
4 ETW000 [     dev trc,00000] Retrying without protocol specifier: (local)                              30 45.462500
4 ETW000 [     dev trc,00000] Using Provider SQLNCLI                                                    60 45.462560
4 ETW000 [     dev trc,00000] OpenOledbConnection: MARS property was set successfully.                  57 45.462617
4 ETW000 [     dev trc,00000] Sun Jul 24 07:24:14 2011                                             15636603 61.099220
4 ETW000 [     dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000                                                                                51 61.099271
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000                                                                                45 61.099316
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 61.099333
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000                                                                                60 61.099393
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 61.099410
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000                                                                                41 61.099451
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 61.099468
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000                                                                                37 61.099505
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 61.099522
4 ETW000 [     dev trc,00000] Using Provider SQLNCLI                                                  5453 61.104975
4 ETW000 [     dev trc,00000] OpenOledbConnection: MARS property was set successfully.                  59 61.105034
4 ETW000 [     dev trc,00000] Sun Jul 24 07:24:29 2011                                             15620154 76.725188
4 ETW000 [     dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000                                                                                43 76.725231
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000                                                                                45 76.725276
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 18 76.725294
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000                                                                                79 76.725373
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 76.725390
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000                                                                                42 76.725432
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 76.725449
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000                                                                                103 76.725552
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 25 76.725577
4 ETW000 [     dev trc,00000] Using Provider SQLNCLI                                                  5413 76.730990
4 ETW000 [     dev trc,00000] OpenOledbConnection: MARS property was set successfully.                  78 76.731068
4 ETW000 [     dev trc,00000] Sun Jul 24 07:24:45 2011                                             15600542 92.331610
4 ETW000 [     dev trc,00000] OpenOledbConnection: line 24466. hr: 0x8000ffff Login timeout expired
4 ETW000                                                                                42 92.331652
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Login timeout expired
4 ETW000                                                                                45 92.331697
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 92.331714
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
4 ETW000                                                                                60 92.331774
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 16 92.331790
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
4 ETW000                                                                                42 92.331832
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 16 92.331848
4 ETW000 [     dev trc,00000] sloledb.cpp [OpenOledbConnection,line 24466]: Error/Message: (err 0, sev 0), Invalid connection string attribute
4 ETW000                                                                                38 92.331886
4 ETW000 [     dev trc,00000] Procname: [OpenOledbConnection - no proc]                                 17 92.331903
4 ETW000 [     dev trc,00000] failed to establish conn. 0                                             5491 92.337394
4 ETW000 [    dblink ,00433] ***LOG BY2=>sql error -1     performing CON [dblink#4 @ 433]             119 92.337513
4 ETW000 [    dblink ,00433] ***LOG BY0=>Login timeout expired [dblink#4 @ 433]                        27 92.337540
2EETW169 no connect possible: "DBMS = MSSQL                            --- SERVER = 'MYSERVER101' DBNAME = ''"

IPad Air wifi works but Safari returns message cannot connect to Apple server?

using iPad Air wifi works but Safari returns message cannot connect to Apple server? (Friends iPad otherwise couldn't post!)

Many thanks for contacting me Carolyn. However the wifi was working fine and I found the solution from this posting:
https://discussions.apple.com/message/25449630
So resetting the iPad by holding down the Home and Sleep buttons together to reset it did the job.
Cheers
Peter
Sent from my iPad

Return message for timeout in BPM

Hey
I have a synchronous scenario using BPM. My question is: If the web service I'm calling is down and I receive a timeout, can I then create a return message from BPM to the sender system that can take attributes from the original message that did not reach it's target? I have read that I can do this in case of an error, but I read someone saying this is not possible when we have a timeout...
Thanks!
regards Ole
Edited by: Ole on Sep 23, 2008 1:16 PM

Hi Ole,
You can implement a Dedadline branch in your BPM that catches your time out.
You can follow theese links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/7c5c41fe06cf1ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/8e2d4233c8db2ce10000000a1550b0/frameset.htm
Carlos

Lengthen or Remove Login Timeout on Workflow Server?

How do I lengthen or remove the login timeout for users on Workflow Server?

Perry,
The default is currently set to 20min - I ran a quick test here and if you de-Select "Enable Session State" chkBox you will be unable to login.
I was under the impression that WA no longer relies on sessions, more of a stateless connection. Meaning that everytime an action is performed in WA by an EU it looks in memory ( I think ) for past credentials for that person and uses it again to reconnect. This allows the abilty for web farming.
InTempo (older version) relied heavily on ASP Sessions which was indirectly related to the setting in IIS.
You may wish to ask your IIS Admin or possibly bring it up with Adobe Support. I'll see if I can follow-up with a bit more research but I'm quite busy at the moment so it probably won't be until late next week.
Good luck.

Connection Failed SQL State: 'HYT00' SQL Server Error: 0 [Microsoft] [ODBC SQL Server Driver] Login Timeout expired

I backed up my database   on old Notebook    SQLSTRINGCONNECT worked all day for any database in SQL SERVR I created
have brand new computer Notebook
installed SQL SERVER 2008 THE EXACT SAME WAY
I RESTORED THE DATABASE
However, I cannot connect to it via Visual FoxPro 9.0 with   SQLSTRINGCONNECT
or even Windows 7    ODBC Data Source ADministrator

Hi,
We need more information as Olaf asked, but my first guess is that you have permissions problem since the users are not the same users in different machines (local users, or SQL Server users),
even if they have the same name :-)
[Personal Site] [Blog] [Facebook]

Linked Server Error message

Hi,
I have 3 SQL servers, A, B, and C.
i am able to establish a linked server from A to C and C to A
i am able to establish a linked server from B to C and C to B.
but when i try to establish a linked server from A to B, i have been getting this error, i am goin nuts because if there is any problem with A, then even C shud not ne able to connect but its connecting, if theres any problem with B , C shud not connect but its connecting.
C is connecting to both A and B without errors.
Also A is connecting to C and B is connecting to C.
But the problem is between A and B Servers.
when i test the connection from B to A i get this message,
A is SQl 2000, B is 2008, c is 2008.
Pls suggest wat do i do.
Y is there a problem of connection between only A to B and B to A.
While making a linked Server from B to A without using Security, i get the error
The OLE DB provider "SQLNCLI10" for linked server "A" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "A".
OLE DB provider "SQLNCLI10" for linked server "A" returned message "Invalid authorization specification". (.Net SqlClient Data Provider)
when i connect using the sa account i get the folowing error,
VIA Provider: The specified module could not be found.
OLE DB provider "SQLNCLI10" for linked server "A" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "A" 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.". (.Net SqlClient Data Provider)
Thanks a Ton for any kind a help

Muchas gracias por la ayuda con el problema:
The OLE DB provider "SQLNCLI10" for linked server "A" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "A".
OLE DB provider "SQLNCLI10" for linked server "A" returned message "Invalid authorization specification".
Esto me ayudo a resolverlo:
https://sites.google.com/site/greateindiaclub/software-zones/database-community/sql-server/cannotinitializethedatasourceobjectofoledbprovidersqlncli10forlinkedserver
Pero despues me apareció el siguiente problema:
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "B" was unable to begin a distributed transaction.
OLE DB provider "SQLNCLI10" for linked server "B" returned message "El administrador de transacción ha deshabilitado su soporte para transacciones de red o remotas.".
Y lo resolví con esto:
EXEC sp_serveroption @server = 'ServerB',@optname = 'remote
proc transaction promotion', @optvalue = 'false' ;
Fuente: http://www.sqlservercentral.com/Forums/Topic1102122-146-1.aspx#bm1102224
Saludos...
Desarrollador en .NET

A network-related error has occurred where Connecting to Hive ODBC by Linked Server

1) I have created Hive ODBC Driver (Succesfully Tested)
2) I have created Linked Server on SQL Server 2014 (Succesfully Tested)
3) SELECT * FROM OpenQuery([SQLHive],
'SELECT * FROM hivesampletable;')
ERROR:
OLE DB provider "SQLNCLI11" for linked server "SQLHive" returned message "Login timeout expired".
OLE DB provider "SQLNCLI11" for linked server "SQLHive" 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 67, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [67].
INSTRUCTIONS FOLLOWED:
http://ayadshammout.com/2013/05/27/import-hadoop-data-into-sql-bi-semantic-model-tabular/
CONFIGURATIONS OF ON TEST:
-Firewall is OFF
-SQL Server and Windows Authentication mode is ON
- Named Pipes is ON on SQL Server Confi manager
Kenny_I

The subject line and the first point on your list indicates that you want to connect to a Hive data source using ODBC. But the error message tells us that you have set up a linked server with SQL Server Native Client, which is the OLE DB provider you would
use if you want to connect to another SQL Server instance.
For using an ODBC driver, you need to use the MSDASQL provider, and in the @provstr argument you specify which ODBC driver you want to use. That is, something like:
EXEC sp_addlinkedserver 'SQLHive', '', 'MSDASQL',
@provstr = 'Driver={Hive ODBC Driver}....'
As I have not worked with the Hive ODBC Driver, I don't know exactly what goes into the @provstr parameter, but it would be the same as if you connected to Hive from an application.
Erland Sommarskog, SQL Server MVP, [email protected]

Linked Server "Could not open a connection to SQL Server [1909]" after reboot

We have two production servers, with RCP [out] enabled linked servers set up back and forth between them. When they are rebooted at the same time one of the linked servers will throw this error:
Named Pipes Provider: Could not open a connection to SQL Server [1909]. 767462021 OLE DB provider "SQLNCLI10" for linked server "server3" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "server3" 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.".
I've been fixing it by dropping and re-creating the linked server. It's completely identical as before (in sp_linkedservers), so I'm thinking this shouldn't be necessary. My guess is it's only happening because during startup the other server was not available.
If this is true, can I force a reset of the linked server, without having to restart the server instance, or recreate the linked server?

Hi Chuck, thanks for the reply. Both servers were already set to 20. I think this might work if in the ensuing 10 seconds the other server happened to come on line. I could also set it to 60, but then production queries would be waiting 60 seconds
for timeout. I'm really after a cause and solution. It's as though the server tries once, sees that the other server is unavailable, and henceforth refuses to try again. I'd like it to try again. Really, it should try every time.
Could it be that upon startup SQL Server looks for all its linked servers and marks ones it can't reach in that moment as forever invalid? I'm sure this doesn't happen after startup, only during.

Linked Server Problem while SQL Data Transfer using Non-sys Admin Account

Hi Team,
I've an issue while transferring the data from ServerA to ServerB. I've made the ServerB as "Linked Server" to Server A. Pre requisite like:
1) SQL Account is been created on ServerB.
2) Timeout settings for remote connections is set to "No Timeout".
When I execute the below script using Query Window, It executes successfully:
Insert into ServerB.DBName.dbo.TableName1
Select * from dbo.TableName1
But when I execute the same step by creating a SQL Job, it fails with the below error message:
Message
Executed as user: DomainName\UserName. Named Pipes Provider: Could not open a connection to SQL Server [1450]. [SQLSTATE 42000] (Error 1450) OLE DB provider "SQLNCLI" for linked server "ServerB" returned message "Login
timeout expired". [SQLSTATE 01000] (Error 7412) OLE DB provider "SQLNCLI" for linked server "ServerB" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,
this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". [SQLSTATE 01000] (Error 7412). The step failed.
Could you please help me in fixing the above error message and I can transfer the SQL Data between 2 Servers.
Thank You
Sridhar D Naik

Sridhar,
Is this still an issue?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

OLE DB provider "SQLNCLI10" for linked server "(null)

Hi guys,
I am keep getting this error message when I am trying to connect to one SQL 2008R2 Instance which is clustered from SSIS ( SQL Server Data tools)...
Exception from HRESULT: 0xC0202009
Error at Data Flow Task [OLE DB Source [548]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E14 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E14 Description: "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.".".
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E14 Description: "OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Login timeout
expired".".
Any workaround for this error message if anyone has encountered before?
Thank you
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

Hi Logicinisde,
In addition to Olaf's answer, if package configurations are enabled, the issue may occur because the package configurations are not applied correctly. Please give that a check.
Regards,
Mike Yin
TechNet Community Support

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL Server Expres 2008R2 on Windows 7 peer to peer network using MS Access to connect - ODBC Login Timeout

Hello,
I have had a Microsoft Access database that was running on Windows XP against a SQL Server 2000 database. We are running on a peer to peer network. This all worked fine. Recently I upgraded all the systems to Windows 7 and the Access database
to Office 2013 and setup SQL Server Express 2008R2. I am running into strange problems trying to connect the access database to SQL Server Express.
SQL Server Express was setup with mixed authentication mode.
What is strange to me is that if I run the Access database on the same server as SQL Server Express 2008R2, everything works fine. However, if I run the Access database from a separate system (Windows usernames and passwords are identical on all systems
for all accounts). I get a spinning circle, then after 5 minutes or so I get an error box that says "Connection Failed SQL State S1-T00 - ODBC Login Timeout Expired.
I click OK and then there is a ODBC login box, It has trusted connection box checked. So, I just click ok and everything runs fine.
I have checked with the Access database the ODBC connection string (How do you change this to imbed a username and pwd?) and the connection specifies that trustedconnection = yes.
I have tried setting the odbc connection up to use a SQL Account, I have setup all of the security in SQL so that Windows accounts have access and either works on the system that is hosting the SQL database. But when I try to connect from a separate
machine we have to wait with the timeout and then click okay.
Any Ideas.
Thank you!!!

I have TCP/IP and named pipes.
I will take a look at the kb article.
What puzzles me is that odbc connection is set for trusted connection, the access database is set for trusted connection. But yet it seems that it wants to do a SQL authentication. Then it fails, and then if you simply hit okay to do the Trusted
Connection then it is fine.
I will read about setting the UID and PWD in code. Been a long time since I have done that, but very doable. Then see if the Access DB is setup with the UID and Pwd in the odbc connection string, then switch the odbc connection to be a SQL Server
connect, then maybe it will work.. Crossing my fingers.
I will be back on site next week and will give it a try then.
I will check the ports, but suspect they are fine as it works fine after it has it timed out and you hit okay to connect with a trusted connection.
Thanks for your ideas.

Returned message login timeout expired linked server

Similar Messages

Maybe you are looking for