If a user sets permission levels only to allow free/busy or free/busy limited details, an Outlook 2011 user will not be able to see any details of the shared calendar. PC users must grant 'full details' to the Outlook 2011 user. Mac users must grant the 'Reviewer' role to Outlook 2011 users.
Just got a ticket from User A. When trying to schedule a meeting with User B, they get a hashed line with 'No free/busy information could be retrieved.' I've seen that before and solved it with a new profile in the past, but this seems to be something different. User A can see the free/busy information for everyone except User B (at least as far as I can tell, taking a random sampling of 25 other users). Had user A try to schedule with people from different departments and authority levels to rule out something to do with group permissions. Also, again through random sampling, I have determined that everyone apart from User A is able to see User B's free/busy. Same thing, several people from different departments at different levels of authority within the company.
My only other thought was that somehow, User B was 'hiding' from User A, but that shouldn't be possible in our environment. I checked my own calendar permissions and as expected, it's not possible to set the Read permission on Free/Busy time to None for a specific user - that radio button is greyed out. In my environment I have versions of Office that sprawl from 2007 to 2016. One of the most common problems from this is that Office 2010 and above have ways of granting custom permissions (where you can view just the time and subject line but no other details, but nothing else). Office 2007 has no way of interpreting these permissions, and consequently interprets it as having no permissions at all. The only workarounds are to upgrade the 2007 user to office 2010 or above, or to have the 2010 user specifically set their permissions to one of the defaults (Reviewer, Author, Editor, Free/Busy Time). Office 2016 (and I suspect 2013) has still more different permission sets than 2010, and I imagine similar problems occur when those are configured and 2010 has no idea how to handle them.
It sounds like your issue might be going upstream of my theory though, with the permission source user being on a lower version than the user experiencing the issue. Still, custom permissions would be the first thing I'd check. AlexG2490 wrote: Christian5842 wrote: The default permission for default user should be, availability, if it's none, then no one can see that person's free busy info I'll double check that as soon as I can get access to User B's machine. But if that were the case, then I and the other few people I had try to schedule a meeting with her would have the same issue, right? It's only User A who experiences the issue with User B. All the rest of us can see User B's calendar.Of course if the person A is the only one who cannot see Calendar from person B, then it's something else.
Just had User A try this. It does work from OWA, so the problem is client-side.
But I have no idea what could actually cause this. Also, I just learned that this has happened between these 2 users before. Each time the profile was rebuilt and it resolved the issue. At this point I could probably fix it the same way, but I'd rather find out what the root cause is and solve that instead.
But I am totally stumped as to what it could be. It's always the same 2 users, and it's apparently happened 3 times now. So, the Free/Busy issue happens only between User A and User B, and User A is the one who experiences the problem each time. Does User A ever experience this issue with anyone else in the organization-i.e. Is Free/Busy working flawlessly when used against any other user? If the answer to that is yes, I'd still want to take a look at what User B's calendar sharing settings are in regards to User A to determine if that's in any way different from the default.
There was an update years ago that really jacked up Outlook 2013's free/busy processing, but it's highly unlikely that'd be the culprit here unless User A hasn't run updates on his/her machine in a very long time. Correct, User A never experiences this issue with anyone else. At least not that I can tell.
I didn't make User A check all 1000 users in the organization, just did some random sampling. Here's User B's sharing settings with User A. They are consistent with all others with whom User B has shared their calendar. I cleared and re-set these settings to no avail.
User A can view User B's calendar as a shared calendar, as these settings allow, but Free/Busy still refuses to load, even though User A has full access to User B's calendar. Both users are now confirmed to be on Office 2013. I can rebuild User A's profile again but this has happened several times now so I still want to find the ultimate cause and solve that instead, rather than just have to rebuild User A's profile every few months. Not sure if you are still monitoring this or not, but I've had luck with the following. Be sure you do this on the computer of the user having issues.
Create a new meeting request. While in the Appointment View, start to type the name of the user that they are having issues with. When typing their name, they should see a dropdown/autocomplete of the user's name (assuming they've emailed them directly or invited them to a meeting before). Click the stylized X on the right side of the dropdown item to delete it (I believe you can hit down arrow and press Delete on the keyboard as well). Once the dropdown entry is gone, use the Check Names button to have it check against GAL and complete the entry. HOPEFULLY that will cause it to try to queue for free/busy again.
Check Scheduling Assistant and see if that resolves. Again, this has worked for me multiple times in our environment.
![]()
I actually had this problem follow a user from a computer to a new computer, so I think it may be something that Office 365 migrates from computer to computer with your account. Not sure if you are still monitoring this or not, but I've had luck with the following.
Be sure you do this on the computer of the user having issues. Create a new meeting request. While in the Appointment View, start to type the name of the user that they are having issues with. When typing their name, they should see a dropdown/autocomplete of the user's name (assuming they've emailed them directly or invited them to a meeting before). Click the stylized X on the right side of the dropdown item to delete it (I believe you can hit down arrow and press Delete on the keyboard as well). Once the dropdown entry is gone, use the Check Names button to have it check against GAL and complete the entry.
HOPEFULLY that will cause it to try to queue for free/busy again. Check Scheduling Assistant and see if that resolves. Again, this has worked for me multiple times in our environment. I actually had this problem follow a user from a computer to a new computer, so I think it may be something that Office 365 migrates from computer to computer with your account.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |