Thanks to any and all who may have responded. Unfortunately given the
condition of our Exchange Server most replies never made it here.
Fortunately everything was fixed by the consultant who came in. I have a
local outfit with some pretty good Windows/Exchange gurus who also have
accounts with Microsoft Tech Support to back them up.
In case anyone is interested and for future reference:
1. We (with MS blessing) deleted the newly created very small PRIV.EDB
2. Copied the TempDefrg.edb file from the other server where eseutil had put
it to where priv.edb was
3. Deleted all log files in that folder
4. Renamed it to Priv.edb and ran an integrity check (OK)
5. Fired up the Exchange Services and all was OK - all old messages,
contacts and celendar items were back
Only downside was messages in the Priv.edb that we blew away were lost.
Before the copy I had users move anything critical to local archive .pst but
I was so busy I did not do mine. Compared to getting things back to normal
that was the least of my worries.
Out of all of this the Priv.edb was reduced from 1.6GB to 990MB so we have a
little breathing room on that old server. I have a brand new server already
to go and will have the consultants back before year end to migrate to
Exchange-2000 on it and Win2K on all the other servers.
The root cause of eseutil not writing the temorary defrag edb back to
priv.edb was probably Norton Corporate Antivirus Exchange add-in locking the
priv.edb somehow. For reasons like this the consultant strongly advised
that eseutil is a bit dangerous and probably should be avoided. Live &
learn I guess.
Thanks,
-Todd C.
condition of our Exchange Server most replies never made it here.
Fortunately everything was fixed by the consultant who came in. I have a
local outfit with some pretty good Windows/Exchange gurus who also have
accounts with Microsoft Tech Support to back them up.
In case anyone is interested and for future reference:
1. We (with MS blessing) deleted the newly created very small PRIV.EDB
2. Copied the TempDefrg.edb file from the other server where eseutil had put
it to where priv.edb was
3. Deleted all log files in that folder
4. Renamed it to Priv.edb and ran an integrity check (OK)
5. Fired up the Exchange Services and all was OK - all old messages,
contacts and celendar items were back
Only downside was messages in the Priv.edb that we blew away were lost.
Before the copy I had users move anything critical to local archive .pst but
I was so busy I did not do mine. Compared to getting things back to normal
that was the least of my worries.
Out of all of this the Priv.edb was reduced from 1.6GB to 990MB so we have a
little breathing room on that old server. I have a brand new server already
to go and will have the consultants back before year end to migrate to
Exchange-2000 on it and Win2K on all the other servers.
The root cause of eseutil not writing the temorary defrag edb back to
priv.edb was probably Norton Corporate Antivirus Exchange add-in locking the
priv.edb somehow. For reasons like this the consultant strongly advised
that eseutil is a bit dangerous and probably should be avoided. Live &
learn I guess.
Thanks,
-Todd C.