Error 17824, Severity 10 State 0
Error 17824 commonly occurs when a client process (such as yours) terminates
before SQL Server is able to send the results of the client query. Do you
have source code and a de{*filter*} to this process? If so, it sounds like you
need to find out why your client process is causing the Dr. Watson error.
Using SQL Trace might provide some insight as well.
See also, BOL and articles Q169521, Q109787.
James Brake
AECI
Quote:
>We have installed SP 5a and are also encountering 'strange' connection
>related problems' namely 17832 errors and Threadwait errors. Has anybody
>come across these? I'm sorry but I haven't had exactly the problem you
>describe, however, I'll let you know if I do.
>Cheers
>> Hi everyone,
>> I installed SQL sever 6.5 SP 5a at work, but while running a process
which
>> executes quite a lot of querries, I get a Dr. Watson error and SQL error
>log
>> has error 17824, severity 10, state 0 Unable to write to ListenOn
>connection
>> <servername>, loginname, <login ID>, hostname<hostname>
>> OS Error: 64 The specified network name is no longer available.
>> Error 1608 A network error was encountered while sending results to the
>> front end.
>> MSDN online document # Q187370 and Q187278 talks about a Microsoft bug in
>> the SQL Server. They recommended to apply service pack 5a , which we
>> already have.
>> Does someone know how to fix this problem? Please help!!
