> Hi,
>
> I have a client that has an Exchange 2003 server residing on a Server
> 2003 installation. Last night I needed to move the public and private
> databases to new drives (same server, different volume).
>
> Right after the move was complete users started getting undeliverable
> and worse, confused responses to mail that, while just recieved by the
> reciepeint, had been sent as far back as December2008 by the folks in
> this office.
>
> This has caused great concearn of course by everyone and the company
> owner is expecting an explaination, rightfully so, but I haven't a
> clue as to way this happened.
> This did occur last time they had to move the database (whomever
> implemented this exchange server did a poor job of planning).
> The server has been rebooted between the dates of the messages and the
> exchange services have been stopped and started again during this
> time.
>
> No messages were ever spotted sitting in the VS1 queue folder.
>
> Where could have these messages been stuck?
> Why was there no "Delivery delayed..." msgs?
> Why weren't they sent until the databases were moved?
> HOW CAN I FIX THIS AND PREVENT IT FROM EVER HAPPENING AGAIN???
> Has anyone else had this happen?
>
> Thanks!

"Lanwench [MVP - Exchange]" wrote:

> chigrboy <chigr***@discussions.microsoft.com> wrote:
> > Hi,
> >
> > I have a client that has an Exchange 2003 server residing on a Server
> > 2003 installation. Last night I needed to move the public and private
> > databases to new drives (same server, different volume).
> >
> > Right after the move was complete users started getting undeliverable
> > and worse, confused responses to mail that, while just recieved by the
> > reciepeint, had been sent as far back as December2008 by the folks in
> > this office.
> >
> > This has caused great concearn of course by everyone and the company
> > owner is expecting an explaination, rightfully so, but I haven't a
> > clue as to way this happened.
> > This did occur last time they had to move the database (whomever
> > implemented this exchange server did a poor job of planning).
> > The server has been rebooted between the dates of the messages and the
> > exchange services have been stopped and started again during this
> > time.
> >
> > No messages were ever spotted sitting in the VS1 queue folder.
> >
> > Where could have these messages been stuck?
> > Why was there no "Delivery delayed..." msgs?
> > Why weren't they sent until the databases were moved?
> > HOW CAN I FIX THIS AND PREVENT IT FROM EVER HAPPENING AGAIN???
> > Has anyone else had this happen?
> >
> > Thanks!
>
> Embarrassing, isn't it?
> See if
> http://windowsitpro.com/article/articleid/50422/have-you-checked-your-smtp-mailbox-temporary-tables-lately.html
> helps.
>
>
>

"chigrboy" wrote:

> Thanks Lanwench (fantastic user name!),
>
> This gives me a good place to start as I had no clue where to begin.
> Embarrassing??? HELL YES!
> But it's far more troubling that that!
>
> If anyone else has any ideas whilst I try Lanwench's link please post.
>
> Thanks!!!
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > chigrboy <chigr***@discussions.microsoft.com> wrote:
> > > Hi,
> > >
> > > I have a client that has an Exchange 2003 server residing on a Server
> > > 2003 installation. Last night I needed to move the public and private
> > > databases to new drives (same server, different volume).
> > >
> > > Right after the move was complete users started getting undeliverable
> > > and worse, confused responses to mail that, while just recieved by the
> > > reciepeint, had been sent as far back as December2008 by the folks in
> > > this office.
> > >
> > > This has caused great concearn of course by everyone and the company
> > > owner is expecting an explaination, rightfully so, but I haven't a
> > > clue as to way this happened.
> > > This did occur last time they had to move the database (whomever
> > > implemented this exchange server did a poor job of planning).
> > > The server has been rebooted between the dates of the messages and the
> > > exchange services have been stopped and started again during this
> > > time.
> > >
> > > No messages were ever spotted sitting in the VS1 queue folder.
> > >
> > > Where could have these messages been stuck?
> > > Why was there no "Delivery delayed..." msgs?
> > > Why weren't they sent until the databases were moved?
> > > HOW CAN I FIX THIS AND PREVENT IT FROM EVER HAPPENING AGAIN???
> > > Has anyone else had this happen?
> > >
> > > Thanks!
> >
> > Embarrassing, isn't it?
> > See if
> > http://windowsitpro.com/article/articleid/50422/have-you-checked-your-smtp-mailbox-temporary-tables-lately.html
> > helps.
> >
> >
> >

>
> "chigrboy" wrote:
>
>> Thanks Lanwench (fantastic user name!),
>>
>> This gives me a good place to start as I had no clue where to begin.
>> Embarrassing??? HELL YES!
>> But it's far more troubling that that!
>>
>> If anyone else has any ideas whilst I try Lanwench's link please
>> post.
>>
>> Thanks!!!
>>
>> "Lanwench [MVP - Exchange]" wrote:
>>
>>> chigrboy <chigr***@discussions.microsoft.com> wrote:
>>>> Hi,
>>>>
>>>> I have a client that has an Exchange 2003 server residing on a
>>>> Server 2003 installation. Last night I needed to move the public
>>>> and private databases to new drives (same server, different
>>>> volume).
>>>>
>>>> Right after the move was complete users started getting
>>>> undeliverable and worse, confused responses to mail that, while
>>>> just recieved by the reciepeint, had been sent as far back as
>>>> December2008 by the folks in this office.
>>>>
>>>> This has caused great concearn of course by everyone and the
>>>> company owner is expecting an explaination, rightfully so, but I
>>>> haven't a clue as to way this happened.
>>>> This did occur last time they had to move the database (whomever
>>>> implemented this exchange server did a poor job of planning).
>>>> The server has been rebooted between the dates of the messages and
>>>> the exchange services have been stopped and started again during
>>>> this time.
>>>>
>>>> No messages were ever spotted sitting in the VS1 queue folder.
>>>>
>>>> Where could have these messages been stuck?
>>>> Why was there no "Delivery delayed..." msgs?
>>>> Why weren't they sent until the databases were moved?
>>>> HOW CAN I FIX THIS AND PREVENT IT FROM EVER HAPPENING AGAIN???
>>>> Has anyone else had this happen?
>>>>
>>>> Thanks!
>>>
>>> Embarrassing, isn't it?
>>> See if
>>> http://windowsitpro.com/article/articleid/50422/have-you-checked-your-smtp-mailbox-temporary-tables-lately.html
>>> helps.

"Lanwench [MVP - Exchange]" wrote:

> chigrboy <chigr***@discussions.microsoft.com> wrote:
> > Lanwench,
> > My thanks to you again for that link, it got me started in the right
> > direction.
> > There's a hotfix available for this problem which I've installed and
> > hopefully can say resolved this issue. Time will tell.
> >
> > Here's the link to that KB:
> > http://support.microsoft.com/kb/950757/
>
> Hi - sorry, I lost track of this. Oops. Did the hotfix work?
>
>
> >
> > "chigrboy" wrote:
> >
> >> Thanks Lanwench (fantastic user name!),
> >>
> >> This gives me a good place to start as I had no clue where to begin.
> >> Embarrassing??? HELL YES!
> >> But it's far more troubling that that!
> >>
> >> If anyone else has any ideas whilst I try Lanwench's link please
> >> post.
> >>
> >> Thanks!!!
> >>
> >> "Lanwench [MVP - Exchange]" wrote:
> >>
> >>> chigrboy <chigr***@discussions.microsoft.com> wrote:
> >>>> Hi,
> >>>>
> >>>> I have a client that has an Exchange 2003 server residing on a
> >>>> Server 2003 installation. Last night I needed to move the public
> >>>> and private databases to new drives (same server, different
> >>>> volume).
> >>>>
> >>>> Right after the move was complete users started getting
> >>>> undeliverable and worse, confused responses to mail that, while
> >>>> just recieved by the reciepeint, had been sent as far back as
> >>>> December2008 by the folks in this office.
> >>>>
> >>>> This has caused great concearn of course by everyone and the
> >>>> company owner is expecting an explaination, rightfully so, but I
> >>>> haven't a clue as to way this happened.
> >>>> This did occur last time they had to move the database (whomever
> >>>> implemented this exchange server did a poor job of planning).
> >>>> The server has been rebooted between the dates of the messages and
> >>>> the exchange services have been stopped and started again during
> >>>> this time.
> >>>>
> >>>> No messages were ever spotted sitting in the VS1 queue folder.
> >>>>
> >>>> Where could have these messages been stuck?
> >>>> Why was there no "Delivery delayed..." msgs?
> >>>> Why weren't they sent until the databases were moved?
> >>>> HOW CAN I FIX THIS AND PREVENT IT FROM EVER HAPPENING AGAIN???
> >>>> Has anyone else had this happen?
> >>>>
> >>>> Thanks!
> >>>
> >>> Embarrassing, isn't it?
> >>> See if
> >>> http://windowsitpro.com/article/articleid/50422/have-you-checked-your-smtp-mailbox-temporary-tables-lately.html
> >>> helps.
>
>
>
>