Software

Ask something
Discussion Locked

Error running Isinteg -patch on Exch 5.5

0 helpful
11 replies

by del smith

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
At client site who has enountered an Exchange 5.5 database problem. There is no backup at all. I have ran the eseutil to both defrag and repair the database. No errors were recieved from running these. I have also ran the isinteg -fix which reportedcorrecting numerous errors. When attempting to run isinteg -patch I receive the error "Private store could not be updated = Reason: Jeterr_RecordNotFound". I cannot start the information store and the event viewer says that I just completed an offline restore and must run isinteg -patch before I can start the store. Anyone seen this of have suggestions. Many points to the person who provides insight. Thanks in advance. Del Smith

11 replies

by [_rick_>

The first thing that came to mind was that the 'Restore in Progress' key might be set preventing the ISINTEG -patch from working.

Check here for the key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Restore in ProgressIf it does exist se the following Technet Article for steps on how to remove safely:

XADM: How the Restore in Progress Registry Key Works [Q200941]

by [_rick_>

The first thing that came to mind was that the 'Restore in Progress' key might be set preventing the ISINTEG -patch from working.

Check here for the key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Restore in ProgressIf it does exist se the following Technet Article for steps on how to remove safely:

XADM: How the Restore in Progress Registry Key Works [Q200941]

by a.grogan

Hiya, Just a random thought - but were there any patches applied to the information store? - if so you could try re-installing the correct patch or reinstall SP4 for Exchange 5.5 and then run isinteg -patch again.

by brasslet

You mention you ran isinteg -fix and it reported correcting numerous errors. Did you continue to run isinteg -fix until it no longer reports errors? If not, that's probably what you need to do. It doesn't always get everything in the first pass.

This discussion is closed to new replies.