Permabanned
- Joined
- 28 Dec 2009
- Posts
- 13,052
- Location
- london
We had a full building power cut a few weeks ago at one of our sites and everything was shut down and came back up uncleanly. We had no data loss, we lost two drives in our raid 5 qnap array. But the data was not lost and I just rma the drives and created a new raid 6 array. But that is not relevant as the qnap is just used for non essential data.
Since the power cut there has been a lot of errors in the exchange application logs. It keeps saying that the background clean up is failing and now we just had this even log entry:
event id 8230:
An inconsistency was detected in [email protected]: /Calendar/{A5FBAD29-F73B-4F7A-B782-E9B3B7068B26}.EML. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
I have looked in to it and it seems it is trying to repair itself. This user specifically wants to use a blackberry z10 and as we have exchange 2003 we have to use active sync for the device and the sync stops working and the fix is to reset the IIS using IISRESET. But I have told the guys on the support desk that it is not a good too be doing IISRESET every week. But the user is difficult to say no to. I am not sure if the IISRESET and blackberry is causing the problems for the user if it is related to the dirty shutdown we had a few weeks ago.
This is the event log of the clean up failure.
event id 623
Information Store (5848) First Storage Group: The version store for this instance (0) has reached its maximum size of 108Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0xBD334120
Session-context: 0x00000000
Session-context ThreadId: 0x00001DF8
Cleanup: 1
then straight afterwards
event id 3005
Unexpected Exchange mailbox Server error: Server: [ User: [[email protected]] HTTP status code: [500]. Verify that the Exchange mailbox Server is working correctly.
The ESE online defrag has since completed a full pass, well the event logs show it has. But since then I have started to get these calendar repair events.
Since the power cut there has been a lot of errors in the exchange application logs. It keeps saying that the background clean up is failing and now we just had this even log entry:
event id 8230:
An inconsistency was detected in [email protected]: /Calendar/{A5FBAD29-F73B-4F7A-B782-E9B3B7068B26}.EML. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
I have looked in to it and it seems it is trying to repair itself. This user specifically wants to use a blackberry z10 and as we have exchange 2003 we have to use active sync for the device and the sync stops working and the fix is to reset the IIS using IISRESET. But I have told the guys on the support desk that it is not a good too be doing IISRESET every week. But the user is difficult to say no to. I am not sure if the IISRESET and blackberry is causing the problems for the user if it is related to the dirty shutdown we had a few weeks ago.
This is the event log of the clean up failure.
event id 623
Information Store (5848) First Storage Group: The version store for this instance (0) has reached its maximum size of 108Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0xBD334120
Session-context: 0x00000000
Session-context ThreadId: 0x00001DF8
Cleanup: 1
then straight afterwards
event id 3005
Unexpected Exchange mailbox Server error: Server: [ User: [[email protected]] HTTP status code: [500]. Verify that the Exchange mailbox Server is working correctly.
The ESE online defrag has since completed a full pass, well the event logs show it has. But since then I have started to get these calendar repair events.
Last edited:
