Pardon me for making this so vague, but...

I have a script that uses CDO to access messages in a mailbox and delete
them based on age.

The script works fine in testing. It works some of the time in the
production environment, but intermittently causes the Exchange Server's
local delivery queue to stop processing, become unresponsive to a manual
reconnect, and require the server to be rebooted. The consequence not as
bad as it may sound. This server is used only for journaling copied
messages.

I know this sounds like an Exchange issue, but thought I would ask the
question here first to see if anyone had a similar issue. Is there some way
to throttle or "chunk" the amount of data transmitted in the session? This
might be similar to the ADO Recordset parameter that limits the number of
records returned in a query. There are typically a million messages in the
target folder...

Re: CDO script causes Exchange Server to hang by Al

Al
Wed Jun 25 21:53:14 CDT 2008

I'd ask in an exchange group as well, as perhaps there is a faq on this.

That said, have you tried including a delay in the loop that processes the
messages?

/Al

"Trey Shaffer" <Trey@Shaffer-Family.com> wrote in message
news:uMoqKxw1IHA.4492@TK2MSFTNGP02.phx.gbl...
> Pardon me for making this so vague, but...
>
> I have a script that uses CDO to access messages in a mailbox and delete
> them based on age.
>
> The script works fine in testing. It works some of the time in the
> production environment, but intermittently causes the Exchange Server's
> local delivery queue to stop processing, become unresponsive to a manual
> reconnect, and require the server to be rebooted. The consequence not as
> bad as it may sound. This server is used only for journaling copied
> messages.
>
> I know this sounds like an Exchange issue, but thought I would ask the
> question here first to see if anyone had a similar issue. Is there some
> way to throttle or "chunk" the amount of data transmitted in the session?
> This might be similar to the ADO Recordset parameter that limits the
> number of records returned in a query. There are typically a million
> messages in the target folder...
>