[DBNETLIB]ConnectionWrite (send()) &&&& Communication Link Failure
Mar 12, 2007
Hi ALL
I am facing a strange problem using ADO to connect Sql Server that I can not resolve it.
My program connected to SqlServer when it started, the state of the connectionPtr was adoStateOpen.Then I disable the network card and enable it immeditately, the errors happened when I executed the sql query probably because of connectionPtr was invalid,but the state of connectionPtr was always adoStateOpen.
1)Msg: Unspecified error Source: Microsoft OLE DB Provider for ODBC Drivers Description: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
2)Msg: Unspecified error Source: Microsoft OLE DB Provider for ODBC Drivers Description: [Microsoft][ODBC SQL Server Driver]Communication link failure.
Should I reconnect to SqlServer?How can I catch this error when the connection is valid except other errors?
Sorry,my english is poor and thanks for your response.
Thanks a lot.
Env:
1)OS : Windows 2000 Server
2)SqlServer:Sql Server 2000
View 1 Replies
ADVERTISEMENT
May 23, 2007
We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.
Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.
Does anyone have any ideas ?
View 4 Replies
View Related
Sep 20, 2007
Hi,
in our environment
- Windows XP
- SQL Server Express 2005
- Internet connection via TCP/IP protocol
The described network error occurs, when we unplug the network cable:
[DBNETLIB][ConnectionWrite (send()).] General network error.
The affected database resides on the locally installed SQLExpress, it doesn't use any network connections. The error doesn't occur immediately, in most cases there are up to 30 seconds where data can be (correctly!) written to the recordset, but after that timeout the connetion is broken.
We already tried out the described workarounds:
- disable named pipes protocol
- set SynAttackProtect=0 in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
The error doesn't occur with MSDE (SQL 2000) or under Vista.
Thanks for help!
Mathias
View 5 Replies
View Related
Jul 12, 2007
We just replaced an older Windows 2000 sp4 server with a new Window 2003 Standard Edition sp2 server to run our batch processing. We noticed that when the SQL command times out we now get the following error in the ADO command object error collection.
[DBNETLIB][ConnectionWrite (send()).] General network error. Check you network documentation.
Native Error: 11
SQL State: HY018
msado15.dll version 2.82.3959 is on this server.
On other servers running Windows 2003 Enterprise Edition sp1 the error on the ADO command object is normal with.
Timeout expired
Native Error: 0
SQL State: HYT00
msado15.dll version 2.82.1830 is on this server.
The SQL server they are talking to is on the other side of a firewall. It is SQL 2005 sp2 running on Windows 2000 sp4.
I have also tested this on a Windows 2003 sp2 server that doesn't have to cross a firewall and get the correct Timeout error. It also has the same version of msado15.dll as problem server.
The application is a collection of VB6 Components that are running in COM+ applications. I have isolated the test application to our one SQL interface component and have build a test vbs that can reproduce this on demand. The VB6 Components were not modified in any way for this change and have been working fine for many years prior to this.
All other aspects of our batch processing works as expected. Transactions are working fine. As long as the SQL doesn't timeout everything is normal. DTCPing was used to ensure both servers have correct ports open to allow DTC traffic. Checked the SynAttackProtect setting on SQL and this is not an issue since other clients have no problems.
One point I would like to add is that this new server was initially setup with a temporary server name and then was changed to use the name of the original server on move day. Don't know if this has any impact or not.
View 31 Replies
View Related
Oct 29, 2007
Hi,
Can anyone shed any light on a connectivity issue I am seeing 'in the field'?
I am using a SQL2005 Express SP2 'default' instance database running on a WEPoS (a prepackaged XPe SP2 variant for Point Of Service) platform.
The application connects to SQL via an ADO trusted connection / DSN pointing to '(local)'.
SQL2005 is configured to use shared memory for local connections and named pipes for remote connections.
This all runs fine (sometimes for days on end) ... Then out of the blue I get the following error:
[Microsoft][ODBC Sql Server Driver][Shared Memory]ConnectionWrite (send()).
SqlState 01000 Err: 0x2746
In the latest example this was on an 'INSERT INTO' statement with 7 parameters (~100 bytes the lot!)
Resetting the connection (.close->.open) in the connection error handler reconnects fine and catches the error in the majority of cases, but unfortunately this is not possible from some of the older (closed source) code we use.
Has anyone else had similar experiences?
Better still does anyone have a workaround that does not involve changing application code?
I also made the observation (and this may be a red herring as no LAN comms is required in this case) that the external PC LAN connection was intermittent around the time of the error - although the timestamps from the logs were off by 10/15 mins.
A/Virus McAffee v4.5.1 SP1 is also installed on the PC.
View 8 Replies
View Related
Aug 13, 2000
We are developing an ASP ad component for our web site. For the past one week
we are testing the component in real environment. All of a sudden we are getting the following error message.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Communication link failure
We are using SQL Server 7.0 with Windows NT4 SP4, IIS and ASP
We are not using any complex joins or view updation. We are using ADODB connection variable with an application scope to establish the connection. When we try to use the connection object to open a Recordset, this error occured. We colsed the connection and destroyed the ApplicationScope Connection object and re-created the object with out any success.
View 2 Replies
View Related
Apr 10, 2007
I get ODBC Error 823 when I try to access data from Crystal reports and I/O error, communication link failure...from query analyzer. But the weird thing is it is on and off. If I keep keep clicking 4 times in a row it happens 5 time or 7th time. It is alo only on one of the big tables. They are all stored on same primary filegroup?
Any ideas on what this might be? When I checked BOL it said disk error. The network team doesn't seem to agree. How can I make sure it is hardware or software problem?
Please help.
B.T.W we have SQL 2000 Enterprise.
View 9 Replies
View Related
Jul 20, 2005
Hello,We are the authors of an application written in PowerBuilder (typeClient-Server, database MSSQLServer2000).After some time (1 hour) of client inactivity happens disconnect from serverand aplication reports error 'Communication link failure ...'Please, would you help me, if exists some way how to set up an interval ofthe connectivity between Client and Server. I wasn´t able to find it out inany help or manual.Thank you very much in advance!Pavel
View 1 Replies
View Related
Mar 7, 2007
I am running an SSIS packsge across 2 servers. There at 33 Mil rows being copied over. At 5.6 mil rows I get this
[OLE DB Source [1]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: The specified network name is no longer available. ".
[DTS.Pipeline] Error: The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Is there any known cause of this?
Thanks
View 1 Replies
View Related
Aug 28, 2006
Hai,
Iam using VC++ application to connect remote database(MSSQL) through network.
Everything works fine, if the network connection is active. If the network breaks and resumes, the application throws "Communication Link Failure" and do not get connected even after the network is resumed.
Client :
* Windows 2000 Professional
* MDAC 2.5
* VC++, using framework- CRecordset to access database
* PEER to PEER network configuration
* DSN through ODBC
Server :
* Windows 2000 Professional
* MDAC 2.8
* MSSQL Server
how to resume the database connection ??
Any one help me????
Thanks in advance,
View 5 Replies
View Related
Jun 14, 2007
Hi Y'all,
When i alter 1 single value in my sql server 2000 sometimes i get following error:
1) [MICROSOFT][ODBC SQL SERVER DRIVER] Communication link failure
After clicking away:
2)CANNOT START MORE TRANSACTION ON THIS SESSION
Maybe someone can help me out on this?
Thanks!
View 1 Replies
View Related
May 22, 2000
We replicate from London to New York and Hong Kong. The New York replication is working fine but everytime we try the Hong Kong replication it starts doing it but when it gets to the bulk copying stage it'll still keep going but on a random table will suddenly fail with a communication link failure message ?? It used to do this and because it keeps trying it used to eventually succeed but recently it never succeeds ?? It keeps trying but we end up having to stop it as it just doesn't succeed anymore ?? Our link to Hong Kong appears fine, we can ping and PC Duo into their servers.
Any ideas would be greatly appreciated as we can't think what it may be ??
thanks
Paul
View 1 Replies
View Related
Jul 20, 2005
Hi,with SQL 2000 and Windows 2000, we're getting lots of this error message"Communication link failure" from our C++ application.Any idea why?Thanks,
View 2 Replies
View Related
Oct 12, 2006
Hi,
I am using ADO in my application to connect and retrieve data from Microsoft SQL Server 2000 SP4. When I start my application, it establishes connection to the server successfully and I am able to retrieve data from the server. here is my test scenario:
1. unplug the network cable from the client machine and put the cable back in after some time. I disconnect from the database in my code when the client machine disconnects from the network
2. Once the client machine comes back on the network, I try to reconnect and retrieve data from the sql server but I get the following error message when I try to execute a sql command:
[Microsoft][ODBC SQL Server Driver]Communication Link failure
This problem occurs only with Window XP SP2. With XP SP1 it works fine. It seems to be problem on the client side as with Windows XP SP1 I do not get this error message at all.
Here are the various details:
1. The firewall is off on the client workstation.
2. the connection string is:
driver={SQL Server};server=AA;uid=BB;pwd=CC;database=DD
where AA = DNS name of server machine where sql server is running.
BB = user name
CC = password
DD= database name
3. The client is remote to the server.
4. I can ping the server machine when the client machine reconnects to the network.
5. I can still telnet the server when the client machine reconnects to the network.
6. client database provider is MDAC odbc.
7. the client and server machines are in the same domain.
8. Shared memory and TCPIP protocols are enabled and TCP is at the top of the list.
9. No alias is being used.
10. Viris scan is not installed.
11. force encriptioned is NOT checked.
Please reply.
View 12 Replies
View Related
Aug 15, 2006
Hi Guys,
I am using C++ (Ver 6) that connects to a SQL Server 7 DB using ODBC drivers. The apps connects to the database in the start and listens to the users requests and replies with the required data.
The apps is working fine, but once in a while it looses connection and gives "Communication link failure" message.
I just restart the apps and it is able to reconnect and perform as normal without any problems.
I am not able to find the reason as this behaviour as its very much unpredictable!
The error is returned by SQLExecDirect() function.
The question is, since I still have the Connection Handle, is it possible to just reconnect to the database re-using the same handle ? or do I have any other choices ?
Thanks in advance.
Faisal.
View 4 Replies
View Related
Sep 1, 2004
Okay-- if anyone can solve this they are truly the SQL genius! We are getting this error when we run a VB program that we use to access an SQL database on a server across our network on a workstation. In fact we get this same error when we even run the program on the server where the SQL database is running or on any of our workstations. Here is the error message:
08501:[Micorsoft][odbc sql server driver] communications link failure
Now the odd thing is that many other functions in the workstation application work fine and retrieve data from SQL but certain data requests by the workstation application fail with the above error message and we get this message consistently. Even though it appears that different workstations running the identical Vb application will get this error consistently but in different locations when running the application. We were running SQL 6.5 on an old server, with the workstation application for literally years without any problems. We also decided to upgrade to a new server, installed server 2000 operating system and the latest version of SQl -- moved all the databases pointed the workstations odbc at this new server and get exactly the same error in the same location in the workstation applications. The programmer that wrote the application and designed the database in SQL can't find the problem and a number of other computer "experts" also could not find the error. We did add a new linksys DSL router/firewall but everything kept working after this installation for several weeks so I don't know if this is the problem on the network. THe programmer also noted that he had problems using terminal services on our network to connect to his office computer and decided that there must be some network issues that are causing the ODBC communicaitions to fail and also terminal services to fail-- or of course they may be unrelated. Has anyone ever seen this ODBC communication error in their travels through SQL implementations? Any help will be greatly appreciated. If we can't fix this we will have to abandon a software application that has been used for over five years and just too complex to rewrite.
Jeff Kilpatrick
View 3 Replies
View Related
Jul 12, 2007
Problem: We have intermittent failures of SQL Server jobs with the following error -
TCP Provider: The specified network name is no longer available. [SQLSTATE 08S01]
Communication link failure [SQLSTATE 08S01]
Types of job steps failing: DBCC Checkdb, LiteSpeed backups, re-indexing sql in stored procs, home-grown database update stored procs. These types of job steps are failing on 3 different servers in a 4-way active cluster although all 4 servers have the same type of job steps. No steps involved attempt cross-server processes, job only uses its own server and SAN.
Environment: 4-way active IA64bit cluster Windows 2003 datacenter running SQL2005 RTM. All 4 nodes attached to EMC Clarion SAN.
What we have already looked at: No additonal messages in event viewers. SQL Agent additional logging shows same error. Network services has monitored and sees nothing. Network services is current on firmware upgrades (just applied last batch 2 weeks ago) and still got 2 more errors after the upgrades. I've seen other postings (with no solutions) where people have same error with SQL2000 through SQL2005 SP2, so i don't believe SP2 will help this.
View 6 Replies
View Related
Nov 22, 2007
Hi Folks,
This is regarding the intermittent failure of communication between the application server and database server in one of our customer environment. Application error as well as SQL error log shows "General Network Error","Communication Link Failure". Please find below the server configuration
Application Server OS: Win 2003 server + Service Pack1, Standard Edition
Database Server OS: Win 2003 server + Service Pack1, MS SQL Server 2000 + SP4
We have checked the Client/Server Network utility associated with SQL Server and found TCP/IP protocol is used in communication neither than Named Pipes. DSN is used. We have also followed and implemented as per one KB article which mentioned Win 2003 server's feature of preventing Denial of Service attacks (Chance may be there to prevent the valid login packets).We made the registry changes and disabled this feature. A scheduled job which updates the database happens every morning. Also backup was done using a backup utility which needs the exclusive access to DB. So we have asked the customer to use enterprise manager for back up the DB instead of using the other utility to backup. If any one have experienced the same issue, please let me know.
Thanks,
Pranav.
View 2 Replies
View Related
Jan 28, 2008
Hi,
I have an SSIS package which runs subsequent packages in a batch. When I run the main package through command line or a SQL job and connect to a data warehouse that is on the same machine, it runs without a problem. When I try and connect to a warehouse on a remote machine (ideal configuration), it fails with this error:
Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ".
This seems to happen on random subpackages and isn't always consistent.
My Master.dts.Config file has this connection info:
<Configuration ConfiguredType="Property" Path="Package.Connections[Batch].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=RemoteServerName;Initial Catalog=DataWarehouse;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>
</Configuration>
Both machines have 64-bit operating system and 64-bit SQL software.
Any help would be great.
Thanks.
View 13 Replies
View Related
Aug 29, 2002
All,
I need a help from you all. I am getting this error if the users are running the application which is connecting from MSAccess97 to SQL Server 2000.
Error: [Microsoft][ODBC SQL Server Driver]Communication link failure
I would appreciate if you send me the resolution for this problem.
Thanks,
Reddy
View 1 Replies
View Related
Nov 16, 2005
I get the message Microsoft [ODBC Sql server driver]communication link failure error message in my VB 6 application with MSDE engine. This error does not happen often.
My connection string is as below.
"Provider=MSDASQL;Driver={SQL Server};Server=" & mSvrName & ";DATABASE=cnsClient;uid=uid;pwd=pwd"
Please help.
View 1 Replies
View Related
Apr 12, 2007
Hello
TestMachine1 runs SQL2005 SP2 and has as linked server myRemoteServer (SQL2000) server. I run an stored procedure in TestMachine1 which inserts about 20,000 rows to a table in myRemoteServer and brings back a similar quantity of rows. This stored procedures take about 1.5min to complete, but no error appears.
When running the same stored procedure in TestMachine2 (also SQL2005SP2), the following error appears after about 1 minute of execution (not the exact text):
SQLNCli. TCP Provider: network name is no longer available - communication link failure.
Please note that this stored procedure worked before on TestMachine2 (but with less than 10,000 rows) and that connectivity is proven among TestMachine1 and myRemoteServer, since I can execute "select * from synonym_MyRemoteTable" with no problems at all in the TestMachine2's Management Studio.
TestMachine1 and TestMachine2 have Windows XP Professional SP2; myRemoteServer has Windows 2003 and SQL Server 2000 SP4.
Can you please help me to avoid this error?
View 1 Replies
View Related
Nov 27, 2007
Several of our customers are getting a message intermitantly throughout the day where the connection is closed. The message being generated is [Microsoft][ODBC SQL Server Driver]Communication Link Failure.
These messages started in the last two weeks.
Thanks for any direction that can be thrown my way.
David
View 3 Replies
View Related
May 19, 2008
Hi all,
I am wondering if you guys have any experience with failing Stored Procedures running inside a SSIS package with the following error:
=====================================================
Message
Executed as user: GAALPSVR034FSYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:51:22 AM Error: 2008-05-19 09:06:55.15 Code: 0x00000000 Source: usp_SLIM_Site_PreProcess Description: TCP Provider: The specified network name is no longer available. End Error Error: 2008-05-19 09:06:55.18 Code: 0xC002F210 Source: usp_SLIM_Site_PreProcess Execute SQL Task Description: Executing the query "Exec usp_SLIM_Site_PreProcess" failed with the following error: "Communication link failure". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:51:22 AM Finished: 9:06:55 AM Elapsed: 932.203 seconds. The package execution failed. The step failed.
======================================================
Sometime it fails when gets called through a job and sometimes even when a package is open in a design mode. The actual Stored Procedure NEVER fails if called in SQL Server Management Studio.
Any ideas or suggestions will be very helpful and appreciated
Thanks for your help!
Jacob
View 3 Replies
View Related
Sep 1, 2015
Below the Error Log Reported in SQL Agent (64 bit SQLServer 2008R2 Enterprise Edition Service pack 2 ,32Core CPU Numa Node and 64GB Ram
Â
[298] SQLServer Error: 10054, TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01]
[298] SQLServer Error: 10054, Communication link failure [SQLSTATE 08S01]
[165] ODBC Error: 0, 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. [SQLSTATE 08001]
[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
View 2 Replies
View Related
Apr 1, 2014
When running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".
What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.
When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements,...
I had a look to all my (SSIS-etl)Â timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?
There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb sql server native client11.0 provider : SQLNCLI11.1.
View 7 Replies
View Related
Aug 20, 2015
I am looking for solution for "Communication link failure" Â since many months in google but no luck, am running an SSIS package to load data. job failing many times with error 'Communication link failure', searched every where but found nothing.
Below is the complete error description when job failed.
OS - Windows server 2008 R2 Enterprise Edition
RAM - 198GB
 SQL server 2008 R2 Enterprise Edition and error description is below,
Started: Â 6:22:40 AM Â Error: 2015-08-19 18:50:32.70 Â Â Code: 0xC0202009 Â Â Â
Source: Data Flow Task Lookup [193] Â Â Â
Description: SSIS Error Code DTS_E_OLEDBERROR. Â An OLE DB error has occurred.Â
Error code: 0x80004005. Â An OLE DB record is available. Â
[Code] ....
View 5 Replies
View Related
Feb 4, 2015
we have our cubes in Server A and SQL DB resides on Server B (we are on SQL 2014), from last couple of days are cube started failing due to below error:
OLE DB or ODBC error: Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Communication link failure; 08S01; TCP Provider: An existing connection was forcibly closed by the remote host.
; 08S01
I have been going through some blogs to understand the error but don't find any specific yet.
View 0 Replies
View Related
Aug 21, 2007
Since we change the web server to window 2003, we occasionally receive the message
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())
We use ASP and ODBC to access sql 2005. I have specified to use TCP/IP and port 1433 in ODBC.
Any idea to solve it?
Thank you in advance.
View 3 Replies
View Related
Sep 2, 2004
We have been seeing random inexplicable communication link failures when communicating with a Win2K SQL server for a while now. After a very detailed analysis of the various causes of the problem (network, name lookups, etc.), we've narrowed it down to possibly the ODBC driver. We are using TCP/IP.
I've stuck a packet sniffer on the connection between the SQL server and the client and in almost all cases, the connection suddenly terminates with the client sending a TCP reset to the server.
Looking at the packet traces further, it seems like in about 60% of the cases, there is period of activity on the TCP connection, then some inactivity during which there is a constant stream of TCP keepalives between the client and server and then suddenly the client resets the TCP connection.
Now, we can usually correlate this TCP reset to some new activity initiated on the client application, so could this be related to connection pooling in the ODBC? Thats the only inference I can obtain.
We are running Win2K SP3a on the server.
Any ideas on what else to look for or how to debug this further? I have 10GB of packet traces and can provide more details on the connection traces if necessary. The problem also is that we have ~100 clients constantly communicating with the SQL server and we will see anywhere from 10-20 random CLFs in a day.
I've searched the archives extensively and this does seem to be a problem for many people, but a few of them seem to have had genuine network problems and we've pretty much ruled that out since there are other simultaneous TCP connections between the client and the server and they seem to be okay.
Thanks,
TN
View 6 Replies
View Related
Aug 14, 2007
Hi...
We had a setup that used to work up until about a month ago, and I'm just getting around to investigating it. A previously functioning Service Broker app exchanging messages between 2 boxes in a dev/qa environment stopped delivering messages.
Both endpoints are set up to use AUTHENTICATION=WINDOWS and have connect granted to public on both.
The sender side has all the messages piling up in the sys.transmission_queue. When I profile the exchanges, I see initiator -> target connection then the target trace gets
10054(An existing connection was forcibly closed by the remote host.)
and the initiator trace gets
Connection handshake failed. An OS call failed: (80090350) 0x80090350(The system detected a possible attempt to compromise security. Please ensure that you can contact the
server that authenticated you.). State 66.
I've checked that the login that's used to run the target Sql Server instance is in the security list for the initiator instance. I've checked that I can log into the initiator instance with the creds for that account. Both machines can see the domain controller.
I've googled on the "forcibly closed" message in the target trace but all I've found so far says that it's either
1) mismatched security
2) no connect on the endpoints
3) expired certificates.
None of which appear to apply here. Haven't found any message mixing "forcibly closed" with the latter message.
Any ideas?
Thanks
Mark
View 3 Replies
View Related
Mar 15, 2007
I haev an ssis package that copies mulitpple tables from one sever to another.
Halfway thru one of the table copies i get:
[OLE DB Source [1]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: The specified network name is no longer available. ".
Does this look familiar to anyone?
View 2 Replies
View Related
Jul 23, 2005
On a Windows 2000 Server in MYDomain I can do the followingsuccessfully:Net Send JoeUser "test"However on a Windows Server 2003 (Standard Edition) in MyDomain I get:An error occurred while sending a message to JoeUser.The message alias could not be found on the network.More help is available by typing NET HELPMSG 2273.If I enter: net send /DOMAIN:MyDomain joeuser "test"net send comes back with:The message was successfully sent to domain MyDomainBUT... no popups are received.Is there something common to a Windows Server 2003 server that I needto configure to get this to work?How does this relate to SQL Server 2000? I figure that if I can get itto work via a command prompt that it will work for notification as well-- which at this point it doesn't.Thanks for any help.RBollinger
View 2 Replies
View Related
