|
|
Posted by Erland Sommarskog on 09/11/06 21:33
(dotnetfellow@yahoo.com) writes:
> There is no error message returned. Just hangs for hours until a
> timeout is encountered. Looking at it through Profiler Trace it
> appears that no activity is occurring on either server once the
> transaction is begun. Or, in the case of the delete triggers, it
> appears that everything comes to a complete standstill once the delete
> statement is executed.
Let me guess: the source server runs Windows 2000, and the target server
runs Windows 2003? Where as the server you replaced ran Windows 2000?
No, I don't know anything. But I think I've seen this scenario at work. As
that has only been with development and test servers I have not dug into it.
But chance had it that one of our customer ran into precisely this
problem today. They have a brand-new server (which I assume runs Win 2003),
and in one place our gateway database that runs on another server (which
I suspect runs Win 2000) tries to use INSERT-EXEC to the linked server.
Worked find Friday. Today it just hung. SQL 2000 on both machines.
We will probably open a case with Microsoft on this. I suspect it's one
of these RTFM things, but I just don't know which manual. My gut feeling
is that this is a DTC problem. Maybe as simple, as opening the correct
port in Windows firewall. Whatever, I believe it's more a Windows problem
than an SQL Server problem per se.
If we open a case, and I hear about the resolution, I'll try to post
back.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|