I have an exchange 5.5 server that has experienced information store corruption. This is not the first time this has happened. I have always been able to use the eseutil /p /ispriv to resolve the issue in the past.
the repair of the edb files has never taken more than an hour to fix in the past.
Today I am running the same processes as I have done in the past, and the repair is still sitting and running after several hours (approx 6) the verbose shows it is rebuilding data on the table. Task manager shows the process is running but I am at a loss as to why it is taking forever and cannot determine if it is truly doing anything for certain. Ideas?????
the priv.edb file is only 397mb in size so it should not take very long at all.
Please help,
Thanks in advance,
cypherman.
the repair of the edb files has never taken more than an hour to fix in the past.
Today I am running the same processes as I have done in the past, and the repair is still sitting and running after several hours (approx 6) the verbose shows it is rebuilding data on the table. Task manager shows the process is running but I am at a loss as to why it is taking forever and cannot determine if it is truly doing anything for certain. Ideas?????
the priv.edb file is only 397mb in size so it should not take very long at all.
Please help,
Thanks in advance,
cypherman.