Hi, when I try to activate my address book, i get the error "There is no pool available for this operation. Exit the wizard. (Error Code: 0xc3EC78D9)".
I have verified my mmc shows that LCS is at SP1, it is activated, and
functioning properly (users able to interact via OC2005). It is locally
installed on the standard edition server.
I am trying to setup an alert system for our new application. Idea is to create triggers on the tables that we need updates about. When a table changes trigger will be fired and that will send a change data message to a service on a
different sql server. That service will process the message and create an event in the notification services database. Notification service will later send an email or sms etc depeding on what is required.
Currently i got the message exchange working between two service in the same database. Now I am working on exchanging message between two SQL Servers with no luck. Can anyone please post an article on how to setup communications between two services on different servers.
I did try to expose service broker as an endpoint and create a route on the other server to call it? (This don't work)
Thanks,
Fahad
Hi,
I am struggling establishing message communications between Service Broker instances setup on two SQL server machines. I used nielsb Service Broker examples scripts to setup these service brokers but messages always get stuck in sys.transmission_queue with transmission_status field with the error....
"Error: Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: 5). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation."
I setup the certificate security like this...
use [master];
go
create master key encryption by password = 'masterhello1';
go
1- create certificate TrpCertServ1
with subject = 'TrpCertServer1',
start_date = '06/01/2005',
expiry_date = '06/01/2009'
go
2- BACKUP CERTIFICATE TrpCertServ1
TO FILE = 'C:ServiceBrokerTrpCertServ1Pub.cer';
go
3-CREATE ENDPOINT SSB1
STATE = STARTED
AS TCP
(
LISTENER_PORT = 4026
)
FOR SERVICE_BROKER
(
AUTHENTICATION = CERTIFICATE TrpCertServ1,
ENCRYPTION = REQUIRED
);
go
4-create login remconnlogin1
with password = 'remserver@1';
go
5-create user remconnuser1
from login remconnlogin1;
go
6-grant connect on endpoint::ssb1 to remconnlogin1
go
7- Repeated the above steps for SQL Server 2
8-create certificate TrpCertServ2Pub
authorization remconnuser1
from file = 'C:ServiceBrokerTrpCertServ2Pub.cer';
go
I know it has do something with certficates, I also tried setting encryption=off on Begin dialogue conversation but no luck , same error.
Any help will be appreciated, thanks,
leo
Hi,
I have created vb6 app to connect to sql server 2000 db, and now i have a new requirement: to publish this app on web, but I should use an exising vb6 application that includes all buisness logic and all communication with database: quieries, stored procedures, etc.
To implement this, i create a client :HTML interface and server: asp file that receives an input from client and calls vb6 functions with parameters he received from client. My question is: how can i call from asp application a vb6 application?
I have a database where it will be simple to calculate needed data. Specifically I need to calculate the sum of several columns based on a number of WHERE constraints. I can write the SQL statements - up to a point. The point is the transition to VB. For a simple example
Select sum(Costs) from Research where (Code = 01213).
Now somewhere I have floatiing around in the machine I have my answer but how do I get the SQL results as a variable I can equate to my Visual Basic variable Total_Research_Costs?
Please also let me know if I have won the stupid question of the month?
Thanks for your help.
Whe I try to save the package to sql server. I am getting the below error.. there is no error in a package..
"The save to sql server method has encountered OLE DB error code 0X800004005(communication link failure) in ssis"
What is wrong? and how can i fix it?
I need to get two servers to talk to each other so they can run queries on each other. Any info?
View 2 Replies View RelatedWe 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.
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.
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 RelatedHi...
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
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
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,
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!
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
Sql version
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I have dts running 24 X 7 every 5 minutes
I noticed DTS failed few times a day with error
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:Transaction (Process ID 74) was deadlocked on thread | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Step Error code: 80004005
Step Error Help File:
Step Error Help Context ID:0
The is no entry about in Server server log files.
will trace identify deadlock and why deadlock info not entred into log file ?
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
Dear All,
I am facing one problem on my SQL server 2000.
While accessing some records from the database I am getting this error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Unable to load communication module. Driver has not been correctly installed.
I am using ODBC connection with sql authentication
How to solve this issue.
with regards
Shaji
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 RelatedHi,
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.
Hello.
I have my database and client application. I want my application to know (and to do certain things) when something has happened to a database (for example a row has been inserted). By means of what can it be done??I hope this forum is right place to ask such questions. Thanks for replies!
Hi,
I have a Flat File Source and I want to retrieve few properties of it in an Script Component. How do I?
Also, How could I make the file path of Flat File Source or Connection manager dynamic or configurable through some file ?
any input is appreciated.
Fahad
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.
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
SQL 2005 Standard x64 Service Pack 2
Windows 2003 R2 X64 service pack 2
The principle, partner and witnesss have two NICs each (NIC1 and NIC2). I want them to communicate in NIC2 for sending logs and establishing quorum. This will happen in their own private network (say 192.168.1.0/24). The NIC1 in each server will be available for client communication. The domain and clients are in the network (say 10.1.1.0/24).
I am using the same domain account as SQL server service account in all three servers.
How can I do this?
Thanks
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.
We are running SQL 2000 sp4, only one user database (SAP) the database is 63 GB.
The ldf files were trashed so I went to tape to restore.
We are using veritas backup exec 9.1 sp4. Veritas is on the same server. I can restore the master db and the msdb fine. However when we attempt to restore the DEV db it runs for 2 hours and then fails with a communication error from veritas.
When we restore the master the DEV db comes up suspect as there are no files for it to attach to) so we cannot attach to it to restore, so I have deleted it and attempted to restore - same communication error. I have recreated a db named DEV with the mdf etc created to the size needed plus some to be sure, no good same behavior (behavior described below).
The job starts and it creates all the folders for the database (there are 1 MDF, 5 NDF, and 4 LDF files each in its own folder). Then it begins to create teh individual files it gets ~half way through at about an hour-hour and fifteen. During this time there are a large number of writes being performed by SQL (I assume it is creating the structures). Then it switches over to reading from tape a large number of read by beengine for another 45-1.5 hours then the job fails with the error unable to communicate with the device. I ahve noticed that once it starts reading from tape the db is gone from enterprise manager, and the mdf etc. files that were being created are now gone.
Help this has gone on for three days!!!
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.
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
I suspect this is very poor design but I've been asked to research this: can I maintain a persistent communication session inside an sqlclr proc? (tcp/binary packets)
The process has to maintain very high throughput - setting up and tearing down a connection on each transaction is cost prohibitive. For TCO and deployment reasons it is preferable not to have a separate windows service etc that accepts requests from inside the clr proc. Is there the luxury of an alternative integrated into the database?
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.
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
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.