I am having an issue with a single user's freebusy showing no information when I check the scheduling assistant to see their availablity. I see the same problem when I attempt the same task through OWA. I am using OL2007 as my client but if I use OL2003 i can see their availbility so that shows the FB on the PF DB's we have setup are getting updated for legacy clients. Also I have taken a random sampling of users and I don't see this problem with anyone else's mailbox calendar.Steps I have taken.1. I have used the outlook.exe /cleanfreebusy switch2. I have moved users mailbox3. I have verified "Default" has free/busy set in calendar permissions4. I have used MFCMapi and deleted the PR_FREEBUSY_ENTRYIDS, in Root Container and Inbox. Then I ran the outlook.exe /cleanfreebusy switch.5. Verified all my availability services URL's to make sure they are correct and ran test-outlookwebservices but did not see any errors.Not sure what else to check or do other than deleting the mailbox and re-importing his data back to the newly created mailbox. Sr. Exchange Engineer - Constellation Energy

Hi Aaron, I suggest you enable Outlook Logging to check the issue: 1. Outlook 2007, Tools->Options->Other->Advanced Options->Enable Logging (troubleshooting) 2. Use scheduling assistant to check the Free/Busy status of the problem user, when the Outlook indicated No Information (No free/busy information could be retrieved), please run %temp%\olkas and check related Free/Busy log file. The log file is like 2009430-XXXXX-fb.log. Or you can post the result here. In addition, you can also increase diagnostic logging of Availability service to help troubleshooting the issue: Set-eventloglevel msexchange availability\availability service level expert Set-eventloglevel msexchange availability\availability service general level expert Set-eventloglevel msexchange availability\availability service authentication level expert Set-eventloglevel msexchange availability\availability service authorization level expert Then, repro the issue and check the Application Event Log for any related error. Mike

Figured it out from another post that I believe you replied to about granting the SELF account fullaccess, readpermissions to the mailbox. After doing that the problem was fixed.Sr. Exchange Engineer - Constellation Energy