M
Mallar5d
Hi,
Here is a fun one:
I have an Exchange 5.5 server in a Win2k environment. I
have 300 workstations that run Win 4.0 and Win2k.
Everyone is up to date on patches and service packs.
Generally speaking, this is a very clean environment.
Recently, one of the exchange transaction logs became
corrupted. In order to recover from this I ran an eseutil
repair and then an isinteg to recover. All of this worked
great, except.And here is my question.
During the 2 hours that the lost log files covered, all
of my clients can still see e-mails that no longer exist
because they were lost during the recovery process. My
clients can see them, but can't open or delete them. If I
connect via Outlook on another system and log in as a
problem client, the questionable emails are not there. It
appears that each Outlook client remembers the e-mails.
If I uninstall Outlook and then reinstall Outlook, the
client is fine. I don't really want to do that with 300
clients.
Is there a way around this?
Thanks,
Mallard
Here is a fun one:
I have an Exchange 5.5 server in a Win2k environment. I
have 300 workstations that run Win 4.0 and Win2k.
Everyone is up to date on patches and service packs.
Generally speaking, this is a very clean environment.
Recently, one of the exchange transaction logs became
corrupted. In order to recover from this I ran an eseutil
repair and then an isinteg to recover. All of this worked
great, except.And here is my question.
During the 2 hours that the lost log files covered, all
of my clients can still see e-mails that no longer exist
because they were lost during the recovery process. My
clients can see them, but can't open or delete them. If I
connect via Outlook on another system and log in as a
problem client, the questionable emails are not there. It
appears that each Outlook client remembers the e-mails.
If I uninstall Outlook and then reinstall Outlook, the
client is fine. I don't really want to do that with 300
clients.
Is there a way around this?
Thanks,
Mallard