Posted by Erland Sommarskog on 06/28/05 00:58

(cerilocke@ev1.net) writes:
> I have an identical SQL database on two machines (my machine and a web
> server) that links to a database on a third server (S3). When I execute
> a stored procedure on my machine that accesses a database on S3, it
> always runs without a problem. However, when I run the same stored
> procedure on the webserver (via Query Analyzer on my machine, connected
> to the webserver), the stored procedure runs without a problem for
> about ten minutes, and then I suddenly receive the error "Login failed
> for user '(null)'. Reason: Not associated with a trusted SQL Server
> connection.". If I then connect remotely to the webserver via Remote
> Desktop Connection and run the stored procedure there it works, and
> then I can run it again on the webserver via Query Analyzer on my
> machine, but the same problem will occur again after about ten minutes.
> The only difference between my machine and the webserver is that the
> webserver is running Windows Server 2003, whereas my machine runs
> Windows XP. All settings in SQL on the two machines are identical, so I
> would love to know if anyone has a possible solution to this seemingly
> random problem.

When it dies after ten minutes, does it hit a new code path, or is
that access in a loop, and thus the same statement executed again
and again?

In the latter case, maybe you should consider to replace the loop,
so the procedure does have to run for ten minutes...


--
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

[Back to original message]