Never ran into that, no, but here's one possible option.
Microsoft absolutely *LOVES* using Jet for *everything*. (Even Exchange's information store is a Jet database.) If this is actually a Jet-format database, you can try to copy it somewhere else, rename it to have an extension of .mdb, and see if MS Access will open it. (If it's open in "deny read" mode, then you'll have to shut down anything that has it open before you can copy it: probably the FRS service at minimum, maybe the whole DC. If you have to shut down the whole DC, reboot into the "recovery console", and the file shouldn't be open anymore.)
If Access will open it, then you can try to "compact and repair" it; this is basically standard procedure for any Access database about once every couple months or so anyway. (More for high-usage databases.)
If the "repair and compact" works, then you may have to reboot the DC into the recovery console again before you can replace its existing ntfrs.jdb with the repaired one. (Unless stopping the FRS service lets the file get replaced.) MAKE A BACKUP OF THE EXISTING FILE, too, just in case! This *shouldn't* change any of the data in the file, but it might. |
