|
|
Posted by Erland Sommarskog on 06/30/05 00:27
(cerilocke@ev1.net) writes:
> Thanks for replying Erland. The three machines all belong to the same
> domain, and I have all three set up to only use Windows Authentication,
> with named pipes and tcp/ip (I have tried all permutations of removing
> those without any success). I have spent all day trying every possible
> suggestion that I have been able to find, including using SQL
> authorization, but I still have the same error. It seems that my
> identity does not get to the target server (S3) if I go from my machine
> through the web server using either Query Analyzer or Enterprise
> Manager, but I can connect to each of the two servers successfully from
> my machine, and connect to each of the servers from the other server. I
> hope that makes sense.
Apparently there is some fine-print about Windows networking, Active
directory and all that, of which I will have to admit ignorance.
But it seems to me that this is not really an intermittent error, but
a permanent, it just takes ten minutues for your store procedure to
get there. This can easilly be examined by connecting to the web server
from your XP machine, and then directly run a command that accesses
the linked server.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|