We have an SSIS package running inside a SQL Server 2008 environment.
The package is supposed to transfer data to a SQL 2012 table.
The package however often encounters the "TCP connection forcibly closed by remote host" or "Communication link failure" errors. And when it successfully completes, it runs in 4-5 hrs,
which does not happen to other packages.
Resources/resolutions on the web seem very specific to their issue.
Is this problem related to environment of the destination being SQL 2012?
Or can this be solved by disabling priority boost in the 2012 server?
Any help would be greatly appreciated. Thanks.
Perhaps you should try to establish the communication between the servers using the SQL Native Client [Named pipes] provider. You can set up the communication channels using the Server Configuration Utility.
HTH, let us know !
Greg.
Related
I have a physical Window Server 2008 R2 machine running SQLBase 8.5 and I have no problem connecting to it. Recently I migrated this server to a virtual machine and the problem come up. Sometimes I am able to connect to the Server and sometimes not.
I can pin my Virtual Server but not able to connect to it through SQLTalk or any client application.
Is anyone having the same issue running SQLBase 8.5 on a Virtual Machine?
Thanks!
Check how many users connect at a time. SQLBase 8.5 have some limitation when maximum number of users/cilents exceedes.
Try to find whether the issue occurs when a large query is executed. If so then try to simplify it.
Check for blocking issues. Try to test its working when disabling Internet security applications\antivirus\Firewall for some time.
Check for port issues. Check the 'listenport' value of sql.ini file.
Check for SQLBaseConnection properties and cross check the parmeters like 'connection lifetime'.
SQLBase 8.5 was only ever certified up to Windows Server 2003, and is so old I'm amazed it runs at all. You should be running at least SQLBase v12 if you're on Window Server 2008.
Here is a compatibility matrix: SQLBase compatibility v6 to v12.2
So assuming your SQLBase instance is actually up and running at the time you can't connect, check the CLIENT side sql.ini , there will be an ip address e.g. .
On the CLIENT at command prompt, run: ping -t (ipaddressofserver in CLIENT sql.ini)
I have a production server with transaction replication in place. I am only migrating the publisher server to a Windows Server 2012 for TLS 1.2 compliance. The SQL Server version is staying the same: 2008 R2. The distribution server and the subscription servers are not being moved. I have one subscription server with 48 separate subscriptions.
I need to find out what is the best way to deal with the replication. The new publication server will not have the same name. So what changes do I need to make on the distribution/subscription servers? Can I generate the script out on the publication server, run it on the new migrated server? I have been discouraged to do the system db restores on the new servers. So I am restoring the publisher databases on the new migrated server. Do I need to do the subscription database from scratch or leave it as is, and once I run the scripts on the publisher server and change some settings on the distribution and subscription server, it will catch on? I'm not sure. Please help if you can. Thanks.
I have installed a SQL Express 2008 Server on my Desktop for some local work. This has mixed authentication. I have enabled TCP/IP connection so that one colleague can connect to this server. However, this exposes the server to everyone in the network. How do i keep track of which PC in the network connected to this server and when ? This would just help me audit the usage of the server.
Well you can get information about current users, sessions, and processes in an instance by using
sp_who;
MSDN Documentation
I have been trying for SSRS 2008R2 reports access from my one of the server which are delpoyed on it (O.S windows 2008 R2 server) to my web
application which is hosted on another server ..
I tried by using reportviewer and by passing the server credentails.
I am getting an error :
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IPAddess:80
plzz can any one help me..
Looks more a firewall port blocking problem to me.
Can you open the report server via http://yourserver/reports on the machine itself?
If so then check your firewall settings on the server. On default they block all incoming port in "domain", "public" and "private".
EDIT:
Checkout the screenshot for firewall settings (german, but english gui is the same location)
I developed the Windows Application using Entity Framework 4.0 with SQL Server. In development the SQL Server has been installed in local machine it self. While moving production my client wants to deploy the SQL Server in remote location, the insert/update operation is taking bit more time in Remote Server but it executes very fast if it is local server.
Please guide me how to improve the performance?
The problem may be caused by network problems or something with the SQL Server, to rule out either the SQL Server, you can use the Profiler and look at the times and others.
Regards