That's all well and good but

http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;234551

If it is the FTP server which is throwing the Dr Watxon error then I =
don't see how this article applies at all. Since when did the FTP =
server use ISAPI?

What I am finding is that if my FTP Server (Windows 2000) has a =
substantial load on it whil using the MMC to look at CurrentSessions, it =
can throw a Dr Watson Exception error without regularity.

--=20
George Hester
__________________________________

"George Hester" <hesterloli.DeleteThis@hotmail.com> wrote in message
news:OQRMiFCqEHA.3300@TK2MSFTNGP12.phx.gbl...
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;234551" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;234551</a>

 >If it is the FTP server which is throwing the Dr Watxon error then I don't
 >see how this article applies at all. Since when did the FTP server use
 >ISAPI?

It's about third parties that run in IIS memory and thus also can corrupt
<a style='text-decoration: underline;' href="http://FTP." target="_blank">FTP.</a>
Do you run thirdparty ISAPI dlls? If so, place them in process isolation,
and the FTP server will be stable.

 >What I am finding is that if my FTP Server (Windows 2000) has a substantial
 >load on it whil using the MMC to look at CurrentSessions, it can throw a Dr
 >Watson Exception error without regularity.

--
George Hester
__________________________________<!-- ~MESSAGE_AFTER~ -->