Yes, the update has been applied.
This problem exists in Windows XP Pro as well, prior to sp2. After applying
"Jeremy" <jeremy@progear.com> wrote in message
news:%23G%23F9ZiuEHA.2196@TK2MSFTNGP14.phx.gbl...
> Have you applied this update to your server? I don't know if you are
> getting these error codes are not.
>
>
http://support.microsoft.com/?id=827214 >
> The Inetinfo.exe process repeatedly crashes and restarts, and "Event ID
> 7031" and "Event ID 7034" error events are repeatedly logged in the system
> log in Windows Server 2003
>
> "Tim Watts" <timwatts@builddirect.com> wrote in message
> news:Og3tznEuEHA.3932@TK2MSFTNGP10.phx.gbl...
>> There is definitely no spam clogging up our smtp queue.
>>
>> The SMTP service on the web server is used ONLY by local web sites to
>> send emails from local web applications such as invoices, form
>> submissions etc.
>>
>> Here is an excerpt of the logs from each of the servers:
>> ===============================================
>>
>> ====== EXCHANGE 2003 SERVER LOG ======
>> 2004-10-21 07:24:35 192.168.x.xxx web.server.com EHLO - +web.server.com
>> 250 0 316 28
>> 2004-10-21 07:24:35 192.168.x.xxx web.server.com MAIL -
>> +FROM:<xxxxxx@yahoo.com> 250 0 42 29
>> 2004-10-21 07:24:35 192.168.x.xxx web.server.com RCPT -
>> +TO:<john@xxxxxxxxxxxxx.com> 250 0 0 35
>> 2004-10-21 07:27:54 192.168.x.xxx - QUIT - - 240 0 72 4
>> 2004-10-21 07:34:45 192.168.x.xxx web.server.com TIMEOUT - web.server.com
>> 121 2885920960 38 14
>> 2004-10-21 07:34:45 192.168.x.xxx web.server.com QUIT - web.server.com
>> 240 609984 38 14
>> 2004-10-21 07:37:54 192.168.x.xxx - QUIT - - 240 0 72 4
>>
>> ====== SMTP LOG ON WINDOWS 2003 WEB SERVER ======
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionResponse - -
>> 220+exch.server.com+Microsoft+ESMTP+MAIL+Service,+Version:+6.0.3790.211+ready+at++Thu,+21+Oct+2004+01:04:45+-0700+
>> 0 0 122 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionCommand EHLO -
>> web.server.com 0 0 4 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionResponse - -
>> 250-exch.server.com+Hello+[192.168.x.xxx] 0 0 49 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionCommand MAIL -
>> FROM:<xxxxxx@yahoo.com> 0 0 4 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionResponse - -
>> 250+2.1.0+xxxxxx@yahoo.com....Sender+OK 0 0 40 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionCommand RCPT -
>> TO:<@xxxxxxxxxxxxx.com> 0 0 4 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionResponse - -
>> 250+2.1.5+john@xxxxxxxxxxxxx.com+ 0 0 36 0
>> 2004-10-21 08:04:45 192.168.x.xxx OutboundConnectionCommand BDAT -
>> 2936+LAST 0 0 4 0
>> 2004-10-21 08:15:17 192.168.x.xxx OutboundConnectionResponse - -
>> 451+Timeout+waiting+for+client+input 0 0 36 0
>> 2004-10-21 08:15:17 192.168.x.xxx OutboundConnectionCommand QUIT - - 0 0
>> 4 0
>>
>> ===============================================
>>
>>
>>
>> Tim
>>
>>
>>
>>
>> "Jeremy" <jeremy@progear.com> wrote in message
>> news:OEKqNV%23tEHA.2624@TK2MSFTNGP11.phx.gbl...
>>> We have the same problem with ours with pretty much the same set up. We
>>> are running all the latest service packs on Win 2003 Server. I get a
>>> lot of messages in the que that is just spam email that goes to the bad
>>> message directory.
>>>
>>> "Tim Watts" <timwatts@builddirect.com> wrote in message
>>> news:OAx2Aj6tEHA.3016@TK2MSFTNGP12.phx.gbl...
>>>> I have a web server running win2k3, it is configured to relay all
>>>> messages to the smart host, an internal exchange 2k3 box. It will run
>>>> flawlessly for a while (anywhere from a few months to a few days), and
>>>> then all of the messages start getting stuck in the queue for no
>>>> apparent reason.
>>>>
>>>> I have tried stopping and restarting the SMTP service. Still stuck in
>>>> the queue.
>>>>
>>>> I next tried restarting IIS, and all dependent services (IISAdmin, WWW,
>>>> SMTP Etc) . Still the messages remain stuck in the queue.
>>>>
>>>> Finally, I have to reboot the server, and upon restart the messages get
>>>> sent immediately once the web server finishes restarting.
>>>>
>>>> Does anyone have any idea why this is happening, and why the only
>>>> solution appears to be restarting the server.
>>>>
>>>> This is happening on a number of win2k3 servers, where they are set to
>>>> relay to an internal exchange 2k3 server (Two different ex2k3 servers).
>>>> The only thing being logged is that the exchange server is "dropping
>>>> the connection".
>>>>
>>>> Any insight would be most helpful.
>>>>
>>>> Tim
>>>>
>>>
>>>
>>
>>
>
>