Issue 1: "Reminders" either calendar, task, or flagged items. Some mailboxes don't pop up the reminder in outlook or owa. If i move the mailbox to another mailstore, then the past and upcoming reminders pop up, this led me to think mailstore corruption. Running eseutil finds nothing. before I ran isinteg, i moved all the mailboxes to a temp store and then ran isinteg and it fixed a bunch of errors, then moved the mailboxes back. A couple months later, the missing reminders issue is starting to come back.Questions 1: Has anyone had this issue? Do I need to run isinteg with the mailboxes on the mailstore in order to fix mailboxes? Does anyone have a fix or idea to resolve this?Issue 2: When creating new resources (Rooms) and I grant user or group permissions, they are listed but the user does not get granted access. The get a prompt in outlook asking if they would like to ask the calendar owner for access, but that does not work either. I have tried everything on this one, moved them to antoher store, granted full mailbox permissions, nothing works, it worked before. And now I am starting to see the same issue when users try and share calendars. I think it may be related to the mailstore corruption or perhaps a bug in one of the Update Roll-Ups.Question 2: Has anyone seen this? Can someone test creating rooms and granting non admin access, regular review and editor stuff?Currently Storage Servers are EX 2007 SP1 Rollup 6, I was thinking about appyling Rollup 8 to see if it might resolve the issues, but running isinteg accross 34 production mailstores does not seem like a good idea to me.Any help would be greatly appriciated,Scott

Hi, I don't recommend to run Isinteg on the Mailbox Database which associated with mailboxes since the data will be lost. I suggest we move all the mailboxes to the new Mailbox Database, and delete the problematic store. For the second issue, did you try the PFDAVAdmin tool? Please download the tool from following URLhttp://www.microsoft.com/downloads/details.aspx?FamilyId=635BE792-D8AD-49E3-ADA4-E2422C0AB424&displaylang=en 1, Run the Tool on the Exchange 2007 mailbox server and connect to All Mailboxes.2, Expand Mailboxes, find the room mailbox and right click it, select Folder permissions, you can check it.3, You can also check the Calendar permissions. Thanks Allen

Moving the mailboxes to other stores or even a new store was only a temp fix for the reminders and it did not resolve the calendar permissions issue, so doing that for 3,000+ users and 34 Mailstores would just be a waste of time sadly.Installing Rollup 8 and possibly running the isinteg fixes solved both issues.I have not seen any adverse affects from the isinteg from the users, though I will try and just install the Rollup 8 on the other 2 servers.It should be noted that there are thousands of errors in the isinteg logs, is this normal for stores with only 120 mailboxes?Below is a sample of my isinteg logfrom my store with rooms & generic email accounts...Started: 06/27/09 01:13:02Server name: Pickering.SPCollege.eduDatabase name: SG30\MS30 - Gen & ResOutput log: C:\Logs\MS30-isinteg-20090627-011301.logCheck mode: check and fixOptions: -log C:\Logs\MS30-isinteg-20090627-011301.log -Fix -RefDbLoc -Test testFldRcv testFldSub testMsgRef testMsgSoftRef testAttachRef testACLListRef testACLItemRef testNewsfeedRef testFolder testDelFolder testMessage testAttach testMailbox testReceiveFld testACLList testACLItem testOofHist testPerUser testGlobal testDlvrTo testSearchQ testTimedEvents testMoreFld testTombstone testNewsfeed testSearch testDumpsterProps testFreeDocUrl testEnd The Information Store has not been shut down clean.Hence enabling the Row Count/Dumpster Count test.You may also specify -test rowcounts (or) -test dumpsterref to run these testsStarting test 1 of 21, 'Categorization Tables'Fix: Deleting categorization table and row fid-0001-0000C5C69208Fix: Deleting categorization table and row fid-0001-0000C5C69209Fix: Deleting categorization table and row fid-0001-0000C5CB9BCAFix: Reset the number of CategFolder folder to 0Fix: Deleting links to categorization table in row fid-0001-00000222273EFix: Deleting links to categorization table in row fid-0001-00000222274FFix: Deleting links to categorization table in row fid-0001-000002222756. Time: 0h:0m:50s, number of fixes = 229Starting test 2 of 21, 'Restriction Tables'Fix: Deleting restriction table, row, and all links to fid-0001-00027FF9C8E2Fix: Deleting restriction table, row, and all links to fid-0001-00027FEF3569Fix: Deleting restriction table, row, and all links to fid-0001-0000032307DD. Time: 0h:2m:44s, number of fixes = 5470Starting test 3 of 21, 'Search Folder Links'Fix: updated ptagSearchBacklinks(67870102) on fid-0001-00009330258F. Fix: updated ptagSearchBacklinks(67870102) on fid-0001-000094BD842C. Fix: updated ptagSearchBacklinks(67870102) on fid-0001-00009509D86D. Starting test 9 of 21, 'Folder'MsgFolder 167 (Fid=0001-0000C51BC47B, Mid=0001-0000C6EB08B1, Inid=0001-0000C7F4DD83): Ignoring message size because it is a CDO generated appointment instance.MsgFolder 168 (Fid=0001-0000C51BC47B, Mid=0001-0000C6EB08B2, Inid=0001-0000C7F4058C): Ignoring message size because it is a CDO generated appointment instance.MsgFolder 169 (Fid=0001-0000C51BC47B, Mid=0001-0000C6EB08B3, Inid=0001-0000C7F4058C): Ignoring message size because it is a CDO generated appointment instance., number of rows = 20344. Time: 3h:9m:19s, number of warnings = 1, number of fixes = 1Starting test 10 of 21, 'Deleted Messages'. Time: 0h:0m:0sStarting test 20 of 21, 'reference count verification'Fix: Folder[0001-000000000022].RcvCt: Bad count - Prop(1) <> Calc(0) .. FixedFix: Folder[0001-000094E3D586].: updated ptagSearchBacklinks on fid-0001-000094E3D586. Fix: Folder[0001-0000C53EB3D6].: updated ptagSearchBacklinks on fid-0001-0000C53EB3D6. Fix: Folder[0001-0000C5C9C035].: updated ptagSearchBacklinks on fid-0001-0000C5C9C035. Fix: Folder[0001-0001E744598A].RcvCt: Bad count - Prop(1) <> Calc(0) .. FixedFix: Mailbox[0001-0000C51C46EB].MailboxContentCount: Bad count - Prop(515) <> Calc(591) .. FixedFix: Mailbox[0001-0000C7A444A4].MailboxContentCount: Bad count - Prop(195) <> Calc(197) .. FixedFix: Mailbox[0001-0000C7A95CCC].MailboxContentCount: Bad count - Prop(214) <> Calc(216) .. FixedFix: The performance monitor counters are set to the correct valuesFix: DumpsterCount Calc(13505) <> Prop(13450)Fix: DumpsterCount Calc(553046440) <> Prop(542443582). Time: 0h:0m:0s, number of warnings = 10, number of fixes = 3 . . . . . SUMMARY . . . . .Total number of tests : 21Total number of warnings : 39Total number of errors : 0Total number of fixes : 5863Total time : 4h:18m:58sIt is stripped down as showing 30,000 lines is a bit much.There are 20,000+ "Ignoring message size because it is a CDO generated appointment instance." that do not get fixed, should I be concerned?I will try the PFDAVAdmin tool when I have some time, right now waiting to see nothing is broken from RU8 so I can install them on the other 2 clusters.Scott

We are doing migration from Exchange 5.5 to Exchange 2003 server. User has shared permission on calendar as reviewer for others (Exchange 5.5). After moving mailboxes to exchange 2003 server the permissions will be remain same on client end but other users who are on exchange 5.5 not able to see his calendar. Before moving his mailbox to Exchange 2003 it was accessible for users who have permission. Error Message: Unable to display folder. The calendar folder couldnt found. This problem is intermittent. Out of 10 mailboxes, its creating problem for 2 users after moving to Exchange 2003 Temp Solution: After resetting permission on calendar its working fine without any issue and other users are able to access his calendarIf anyone have fix solution without resetting permission, please revert as soon as possible. One solution i can think export pewrmission from PFDAVADMIN and import again it might help me to resolve the problem.Whats root cause of this issue that needs to be find out ? Its not showing any error message on the server..