Corrupt public store file

[YFronts]

Hi all,
I have this recurring problem with my public folder store on my Exchange server. This is the .edb file. The folder appears in System Manager as offline or 'unmounted' for no reason, yet when I mount it I get this message:
The store could not be mounted because the Active Directory information was not replicated yet.
If you click either Retry or Cancel, you receive the following error message:

The Microsoft Exchange Information Store service could not find the specified object. ID no:c1041722
In the Application Event Log, I find most of the following errors on the link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;303390

Anyhow, having tried everything I can only deduce that the actual file is corrupt! What I'd like to know is can I restore this .edb file from an old backup (before it became corrupt?). What would be the implications? Thanks

 

[YFronts]

Ok, I don't necessarily think a straight restore is actually the ideal solution.

I am trying to use the eseutil.exe as MS documentation indicates that an offline defrag should do the trick. This is what I have done:

- Dismounted store (it was already like this)
- Ran eseutil.exe from C:\program files\exchsrvr\bin
- Used following syntax:

eseutil /d D:\exchange\public dbs\public store.edb /i

This told me I had an invalid argument at 'public'. So I tried putting underscores instead of spaces between names eg:

eseutil /d D:\exchange\public_dbs\public_store.edb /i

Now it tells me it cannot find the file!! Anyone with experience of offling .edb file defrags your advice would be very much appreciated right now as I'm sure I'm doing something stupid!

Thanks

 

[YFronts]

OK I used this tool, and it found no apparent faults!
I still have this problem, for months now. I suspect it may be a disk integrity problem, does anyone have any advice?

Thanks

 

[YFronts]

This problem finally was fixed but only by calling MS support.
In case any of you experience the same issue, it was solved by using ADSI edit from the resource tools to empty the lost and found folder from the child domain. We then replicated the changes using replmon to the root. This enabled the public store to be mounted and must have cleaned out a load of other stuff too.