We encountered an issue today with our Exchange 2000 server where one user 
has lost the contents of her Imbox. The client is an MS Office 2003 client 
(cached mode). All of the users folders are intact (sent items, calendar) 
and even the folders that are sub-folders to the Inbox are intact with all 
messages. The only component missing are the messages that were directly 
contained in the Inbox folder. No other users have this issue and the items 
have not been deleted by the user.

To troubleshoot, we stopped the Exchange services, copied the EDB and STM 
files and then restarted Exchange. Using the EDB file along with an Exchange 
Recovery tool (www.officerecovery.com- esrdemo.exe), we were able to convert 
the EDB file into individual PST files (one PST for each user). We find that 
the missing messages ARE inside the PST file in the Inbox where they are 
suppose to be.

So the question is: If the inbox messages can be extracted from and offline 
copy of the PRIV1.EDB file and show up in the users 'inbox' folder when 
viewed in PST format, why can't the user see these messages when connecting 
to the Exchange server via MS Outlook? We also performed an ESEUTIL /P check 
on the server; no errors detected. We recreated the users e-mail profile on 
a different PC but this didn't resolve the issue. Any ideas on 1) why the 
client can't see the messages or 2) what cause this issue in the first 
place?

Comments welcome...

"WhiteZin2000"  wrote in message 
news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
> We encountered an issue today with our Exchange 2000 server where one user 
> has lost the contents of her Imbox. The client is an MS Office 2003 client 
> (cached mode). All of the users folders are intact (sent items, calendar) 
> and even the folders that are sub-folders to the Inbox are intact with all 
> messages. The only component missing are the messages that were directly 
> contained in the Inbox folder. No other users have this issue and the 
> items have not been deleted by the user.
>
> To troubleshoot, we stopped the Exchange services, copied the EDB and STM 
> files and then restarted Exchange. Using the EDB file along with an 
> Exchange Recovery tool (www.officerecovery.com- esrdemo.exe), we were able 
> to convert the EDB file into individual PST files (one PST for each user). 
> We find that the missing messages ARE inside the PST file in the Inbox 
> where they are suppose to be.
>
> So the question is: If the inbox messages can be extracted from and 
> offline copy of the PRIV1.EDB file and show up in the users 'inbox' folder 
> when viewed in PST format, why can't the user see these messages when 
> connecting to the Exchange server via MS Outlook? We also performed an 
> ESEUTIL /P check on the server; no errors detected. We recreated the users 
> e-mail profile on a different PC but this didn't resolve the issue. Any 
> ideas on 1) why the client can't see the messages or 2) what cause this 
> issue in the first place?
>
> Comments welcome...
>

When this happened, did you try something easier first, like

a) opening her mailbox in OWA
b) setting up a new mail profile for her in Outlook, and/or disabling cached 
mode?
c) trying to open her mailbox in OL2003 on another computer, without cached 
mode?

It's a bit late to do that sort of troubleshooting now, but that's what I'd 
have tried before mucking around with anything else.

Yes - Tried each of these, except OWA (not configured on this Exchange 
system). None solved the issue. I was expecting non-cached mode on another 
PC to be a success, but if failed as well. All good ideas, any others?

"Lanwench [MVP - Exchange]" 
 wrote in message 
news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
>
> "WhiteZin2000"  wrote in message 
> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
>> We encountered an issue today with our Exchange 2000 server where one 
>> user issue in the first place?
>>
>> Comments welcome...
>>
>
> When this happened, did you try something easier first, like
>
> a) opening her mailbox in OWA
> b) setting up a new mail profile for her in Outlook, and/or disabling 
> cached mode?
> c) trying to open her mailbox in OL2003 on another computer, without 
> cached mode?
>
> It's a bit late to do that sort of troubleshooting now, but that's what 
> I'd have tried before mucking around with anything else.
>

"WhiteZin2000"  wrote in message
news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
> Yes - Tried each of these, except OWA (not configured on this Exchange
> system).

Eh? OWA is installed and running by default.

> None solved the issue. I was expecting non-cached mode on another PC to be
> a success, but if failed as well. All good ideas, any others?

I'm out of ideas, sorry - isinteg?

>
> "Lanwench [MVP - Exchange]"
>  wrote in
> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
>>
>> "WhiteZin2000"  wrote in message
>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
>>> We encountered an issue today with our Exchange 2000 server where one
>>> user issue in the first place?
>>>
>>> Comments welcome...
>>>
>>
>> When this happened, did you try something easier first, like
>>
>> a) opening her mailbox in OWA
>> b) setting up a new mail profile for her in Outlook, and/or disabling
>> cached mode?
>> c) trying to open her mailbox in OL2003 on another computer, without
>> cached mode?
>>
>> It's a bit late to do that sort of troubleshooting now, but that's what
>> I'd have tried before mucking around with anything else.
>>
>
>

Not on this server... it was opriginally setup by someone who didn't know 
what they were doing (I inherited it). Although the setup wasn't proper, it 
has been reliable until recently. Thanks for the efforts. Just to update - 
we've recovered the missing messages via other methods and repopulated the 
users inbox. and the messages now show up as they should. But who knows how 
long it may last (or what caused this in the first place). My advice to 
rebuild the server properly has been to no avail. As does the advice of many 
system/network admins, unfortunately.

"Lanwench [MVP - Exchange]" 
 wrote in message 
news:eDObo5VSGHA.4952@TK2MSFTNGP09.phx.gbl...
>
> "WhiteZin2000"  wrote in message
> news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
>> Yes - Tried each of these, except OWA (not configured on this Exchange
>> system).
>
> Eh? OWA is installed and running by default.
>
>> None solved the issue. I was expecting non-cached mode on another PC to 
>> be
>> a success, but if failed as well. All good ideas, any others?
>
> I'm out of ideas, sorry - isinteg?
>
>>
>> "Lanwench [MVP - Exchange]"
>>  wrote in
>> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
>>>
>>> "WhiteZin2000"  wrote in message
>>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
>>>> We encountered an issue today with our Exchange 2000 server where one
>>>> user issue in the first place?
>>>>
>>>> Comments welcome...
>>>>
>>>
>>> When this happened, did you try something easier first, like
>>>
>>> a) opening her mailbox in OWA
>>> b) setting up a new mail profile for her in Outlook, and/or disabling
>>> cached mode?
>>> c) trying to open her mailbox in OL2003 on another computer, without
>>> cached mode?
>>>
>>> It's a bit late to do that sort of troubleshooting now, but that's what
>>> I'd have tried before mucking around with anything else.
>>>
>>
>>
>
>
>

Back up fully.
Install OWA, reapply the service pack, get any hotfixes you can. Update / 
patch Windows to date. Ensure AV is good and up to date on both file 
(excluding the Exchange dir!!) and inbound SMTP. Stop every service to do 
with Exchange, set to manual, restart server, clear temp folder, start all 
Exchange services and set to automatic.
Back up fully again.

Ensure Exchange data is on most appropriate volumes and move if that is not 
the case.

"WhiteZin2000"  wrote in message 
news:Zf-dnWJnSrqhsIfZRVn-vw@comcast.com...
> Not on this server... it was opriginally setup by someone who didn't know 
> what they were doing (I inherited it). Although the setup wasn't proper, 
> it has been reliable until recently. Thanks for the efforts. Just to 
> update - we've recovered the missing messages via other methods and 
> repopulated the users inbox. and the messages now show up as they should. 
> But who knows how long it may last (or what caused this in the first 
> place). My advice to rebuild the server properly has been to no avail. As 
> does the advice of many system/network admins, unfortunately.
>
> "Lanwench [MVP - Exchange]" 
>  wrote in 
> message news:eDObo5VSGHA.4952@TK2MSFTNGP09.phx.gbl...
>>
>> "WhiteZin2000"  wrote in message
>> news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
>>> Yes - Tried each of these, except OWA (not configured on this Exchange
>>> system).
>>
>> Eh? OWA is installed and running by default.
>>
>>> None solved the issue. I was expecting non-cached mode on another PC to 
>>> be
>>> a success, but if failed as well. All good ideas, any others?
>>
>> I'm out of ideas, sorry - isinteg?
>>
>>>
>>> "Lanwench [MVP - Exchange]"
>>>  wrote in
>>> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
>>>>
>>>> "WhiteZin2000"  wrote in message
>>>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
>>>>> We encountered an issue today with our Exchange 2000 server where one
>>>>> user issue in the first place?
>>>>>
>>>>> Comments welcome...
>>>>>
>>>>
>>>> When this happened, did you try something easier first, like
>>>>
>>>> a) opening her mailbox in OWA
>>>> b) setting up a new mail profile for her in Outlook, and/or disabling
>>>> cached mode?
>>>> c) trying to open her mailbox in OL2003 on another computer, without
>>>> cached mode?
>>>>
>>>> It's a bit late to do that sort of troubleshooting now, but that's what
>>>> I'd have tried before mucking around with anything else.
>>>>
>>>
>>>
>>
>>
>>
>
>

I have a similar issue (if not identical).  One user is having their inbox 
messages disappear as soon as the send/receive function is initiated.  For 
example, an email comes in, it can be viewed, and it stays there.  The next 
time a send/receive is performed, the email is blown away.

The same thing happens with OWA.

I've setup another user and auto-forwarded emails to that box as a temporary 
fix to ensure I don't miss any emails, but this is obviously a very serious 
issue....especially if it starts happening to more users....or if it already 
is and they're just not aware of it.

Thanks for any help you can provide.


"Nick Gillott [MVP]" wrote:

> Back up fully.
> Install OWA, reapply the service pack, get any hotfixes you can. Update / 
> patch Windows to date. Ensure AV is good and up to date on both file 
> (excluding the Exchange dir!!) and inbound SMTP. Stop every service to do 
> with Exchange, set to manual, restart server, clear temp folder, start all 
> Exchange services and set to automatic.
> Back up fully again.
> 
> Ensure Exchange data is on most appropriate volumes and move if that is not 
> the case.
> 
> "WhiteZin2000"  wrote in message 
> news:Zf-dnWJnSrqhsIfZRVn-vw@comcast.com...
> > Not on this server... it was opriginally setup by someone who didn't know 
> > what they were doing (I inherited it). Although the setup wasn't proper, 
> > it has been reliable until recently. Thanks for the efforts. Just to 
> > update - we've recovered the missing messages via other methods and 
> > repopulated the users inbox. and the messages now show up as they should. 
> > But who knows how long it may last (or what caused this in the first 
> > place). My advice to rebuild the server properly has been to no avail. As 
> > does the advice of many system/network admins, unfortunately.
> >
> > "Lanwench [MVP - Exchange]" 
> >  wrote in 
> > message news:eDObo5VSGHA.4952@TK2MSFTNGP09.phx.gbl...
> >>
> >> "WhiteZin2000"  wrote in message
> >> news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
> >>> Yes - Tried each of these, except OWA (not configured on this Exchange
> >>> system).
> >>
> >> Eh? OWA is installed and running by default.
> >>
> >>> None solved the issue. I was expecting non-cached mode on another PC to 
> >>> be
> >>> a success, but if failed as well. All good ideas, any others?
> >>
> >> I'm out of ideas, sorry - isinteg?
> >>
> >>>
> >>> "Lanwench [MVP - Exchange]"
> >>>  wrote in
> >>> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
> >>>>
> >>>> "WhiteZin2000"  wrote in message
> >>>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
> >>>>> We encountered an issue today with our Exchange 2000 server where one
> >>>>> user issue in the first place?
> >>>>>
> >>>>> Comments welcome...
> >>>>>
> >>>>
> >>>> When this happened, did you try something easier first, like
> >>>>
> >>>> a) opening her mailbox in OWA
> >>>> b) setting up a new mail profile for her in Outlook, and/or disabling
> >>>> cached mode?
> >>>> c) trying to open her mailbox in OL2003 on another computer, without
> >>>> cached mode?
> >>>>
> >>>> It's a bit late to do that sort of troubleshooting now, but that's what
> >>>> I'd have tried before mucking around with anything else.
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >
> > 
> 
> 
>

FYI - I sent a copy of my Exchnage EDB  and STM file to a recovery lab that 
specializes in Exchange servers. They diagnosed my issue as 'Damaged ID 
Tables'. They recovered the inbox messages to a PST file and we uploaded the 
PST contents to the Exchange Server. Now, the users inbox is properly 
showing all messages.

I'd say this issue was related to the setup of our Exchange server being a 
bit dodgy, but if you want the web address of the Exchange data recovery 
lab, lemme know.

"Just some guy"  wrote in message 
news:8D1C8609-6528-44B0-997F-BAD5B6A6A31E@microsoft.com...
>I have a similar issue (if not identical).  One user is having their inbox
> messages disappear as soon as the send/receive function is initiated.  For
> example, an email comes in, it can be viewed, and it stays there.  The 
> next
> time a send/receive is performed, the email is blown away.
>
> The same thing happens with OWA.
>
> I've setup another user and auto-forwarded emails to that box as a 
> temporary
> fix to ensure I don't miss any emails, but this is obviously a very 
> serious
> issue....especially if it starts happening to more users....or if it 
> already
> is and they're just not aware of it.
>
> Thanks for any help you can provide.
>
>
> "Nick Gillott [MVP]" wrote:
>
>> Back up fully.
>> Install OWA, reapply the service pack, get any hotfixes you can. Update /
>> patch Windows to date. Ensure AV is good and up to date on both file
>> (excluding the Exchange dir!!) and inbound SMTP. Stop every service to do
>> with Exchange, set to manual, restart server, clear temp folder, start 
>> all
>> Exchange services and set to automatic.
>> Back up fully again.
>>
>> Ensure Exchange data is on most appropriate volumes and move if that is 
>> not
>> the case.
>>
>> "WhiteZin2000"  wrote in message
>> news:Zf-dnWJnSrqhsIfZRVn-vw@comcast.com...
>> > Not on this server... it was opriginally setup by someone who didn't 
>> > know
>> > what they were doing (I inherited it). Although the setup wasn't 
>> > proper,
>> > it has been reliable until recently. Thanks for the efforts. Just to
>> > update - we've recovered the missing messages via other methods and
>> > repopulated the users inbox. and the messages now show up as they 
>> > should.
>> > But who knows how long it may last (or what caused this in the first
>> > place). My advice to rebuild the server properly has been to no avail. 
>> > As
>> > does the advice of many system/network admins, unfortunately.
>> >
>> > "Lanwench [MVP - Exchange]"
>> >  wrote in
>> > message news:eDObo5VSGHA.4952@TK2MSFTNGP09.phx.gbl...
>> >>
>> >> "WhiteZin2000"  wrote in message
>> >> news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
>> >>> Yes - Tried each of these, except OWA (not configured on this 
>> >>> Exchange
>> >>> system).
>> >>
>> >> Eh? OWA is installed and running by default.
>> >>
>> >>> None solved the issue. I was expecting non-cached mode on another PC 
>> >>> to
>> >>> be
>> >>> a success, but if failed as well. All good ideas, any others?
>> >>
>> >> I'm out of ideas, sorry - isinteg?
>> >>
>> >>>
>> >>> "Lanwench [MVP - Exchange]"
>> >>>  wrote in
>> >>> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
>> >>>>
>> >>>> "WhiteZin2000"  wrote in message
>> >>>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
>> >>>>> We encountered an issue today with our Exchange 2000 server where 
>> >>>>> one
>> >>>>> user issue in the first place?
>> >>>>>
>> >>>>> Comments welcome...
>> >>>>>
>> >>>>
>> >>>> When this happened, did you try something easier first, like
>> >>>>
>> >>>> a) opening her mailbox in OWA
>> >>>> b) setting up a new mail profile for her in Outlook, and/or 
>> >>>> disabling
>> >>>> cached mode?
>> >>>> c) trying to open her mailbox in OL2003 on another computer, without
>> >>>> cached mode?
>> >>>>
>> >>>> It's a bit late to do that sort of troubleshooting now, but that's 
>> >>>> what
>> >>>> I'd have tried before mucking around with anything else.
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>

Absolutely!

I'd appreciate it.  Thanks.



"WhiteZin2000" wrote:

> FYI - I sent a copy of my Exchnage EDB  and STM file to a recovery lab that 
> specializes in Exchange servers. They diagnosed my issue as 'Damaged ID 
> Tables'. They recovered the inbox messages to a PST file and we uploaded the 
> PST contents to the Exchange Server. Now, the users inbox is properly 
> showing all messages.
> 
> I'd say this issue was related to the setup of our Exchange server being a 
> bit dodgy, but if you want the web address of the Exchange data recovery 
> lab, lemme know.
> 
> "Just some guy"  wrote in message 
> news:8D1C8609-6528-44B0-997F-BAD5B6A6A31E@microsoft.com...
> >I have a similar issue (if not identical).  One user is having their inbox
> > messages disappear as soon as the send/receive function is initiated.  For
> > example, an email comes in, it can be viewed, and it stays there.  The 
> > next
> > time a send/receive is performed, the email is blown away.
> >
> > The same thing happens with OWA.
> >
> > I've setup another user and auto-forwarded emails to that box as a 
> > temporary
> > fix to ensure I don't miss any emails, but this is obviously a very 
> > serious
> > issue....especially if it starts happening to more users....or if it 
> > already
> > is and they're just not aware of it.
> >
> > Thanks for any help you can provide.
> >
> >
> > "Nick Gillott [MVP]" wrote:
> >
> >> Back up fully.
> >> Install OWA, reapply the service pack, get any hotfixes you can. Update /
> >> patch Windows to date. Ensure AV is good and up to date on both file
> >> (excluding the Exchange dir!!) and inbound SMTP. Stop every service to do
> >> with Exchange, set to manual, restart server, clear temp folder, start 
> >> all
> >> Exchange services and set to automatic.
> >> Back up fully again.
> >>
> >> Ensure Exchange data is on most appropriate volumes and move if that is 
> >> not
> >> the case.
> >>
> >> "WhiteZin2000"  wrote in message
> >> news:Zf-dnWJnSrqhsIfZRVn-vw@comcast.com...
> >> > Not on this server... it was opriginally setup by someone who didn't 
> >> > know
> >> > what they were doing (I inherited it). Although the setup wasn't 
> >> > proper,
> >> > it has been reliable until recently. Thanks for the efforts. Just to
> >> > update - we've recovered the missing messages via other methods and
> >> > repopulated the users inbox. and the messages now show up as they 
> >> > should.
> >> > But who knows how long it may last (or what caused this in the first
> >> > place). My advice to rebuild the server properly has been to no avail. 
> >> > As
> >> > does the advice of many system/network admins, unfortunately.
> >> >
> >> > "Lanwench [MVP - Exchange]"
> >> >  wrote in
> >> > message news:eDObo5VSGHA.4952@TK2MSFTNGP09.phx.gbl...
> >> >>
> >> >> "WhiteZin2000"  wrote in message
> >> >> news:CJydnYy9QoK7zoTZnZ2dnUVZ_sSdnZ2d@comcast.com...
> >> >>> Yes - Tried each of these, except OWA (not configured on this 
> >> >>> Exchange
> >> >>> system).
> >> >>
> >> >> Eh? OWA is installed and running by default.
> >> >>
> >> >>> None solved the issue. I was expecting non-cached mode on another PC 
> >> >>> to
> >> >>> be
> >> >>> a success, but if failed as well. All good ideas, any others?
> >> >>
> >> >> I'm out of ideas, sorry - isinteg?
> >> >>
> >> >>>
> >> >>> "Lanwench [MVP - Exchange]"
> >> >>>  wrote in
> >> >>> message news:%238FizWLSGHA.4452@TK2MSFTNGP12.phx.gbl...
> >> >>>>
> >> >>>> "WhiteZin2000"  wrote in message
> >> >>>> news:v7idnVjlffLhBoXZRVn-gg@comcast.com...
> >> >>>>> We encountered an issue today with our Exchange 2000 server where 
> >> >>>>> one
> >> >>>>> user issue in the first place?
> >> >>>>>
> >> >>>>> Comments welcome...
> >> >>>>>
> >> >>>>
> >> >>>> When this happened, did you try something easier first, like
> >> >>>>
> >> >>>> a) opening her mailbox in OWA
> >> >>>> b) setting up a new mail profile for her in Outlook, and/or 
> >> >>>> disabling
> >> >>>> cached mode?
> >> >>>> c) trying to open her mailbox in OL2003 on another computer, without
> >> >>>> cached mode?
> >> >>>>
> >> >>>> It's a bit late to do that sort of troubleshooting now, but that's 
> >> >>>> what
> >> >>>> I'd have tried before mucking around with anything else.
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >> 
> 
> 
>

There are several groups around that do this kind of thing, but I used 
www.ITCexchange.com in Florida USA. They are an MS Gold partner which is 
somewhat reassuring.

"Just some guy"  wrote in message 
news:FDA15940-3432-4E0F-A28F-1E54B4C857D5@microsoft.com...
> Absolutely!
>
> I'd appreciate it.  Thanks.
>
>
>
> "WhiteZin2000" wrote:
>
>> FYI - I sent a copy of my Exchnage EDB  and STM file to a recovery lab 
>> that
>> specializes in Exchange servers. They diagnosed my issue as 'Damaged ID
>> Tables'. They recovered the inbox messages to a PST file and we uploaded 
>> the
>> PST contents to the Exchange Server. Now, the users inbox is properly
>> showing all messages.
>>
>> I'd say this issue was related to the setup of our Exchange server being 
>> a
>> bit dodgy, but if you want the web address of the Exchange data recovery
>> lab, lemme know.
>>