Menu
-->
- Busy Season For Machu Picchu
- Busy For My Work
- Busy Forms
- Busy To Do For Mac And Cheese
- Busy To Do For Mac Os
- Busy For A While
- This tutorial provides instructions for getting started with BusyCal and an overview of its features. BusyCal is a calendar and to do list manager for OS X El Capitan that can be used as an alternative to the built-in Calendar and Reminders apps on OS X.
- BusyCal for iOS is a full-featured mobile companion to BusyCal for Mac, the leading calendar solution for Mac OS X that thousands of users have trusted and depended on for years. Calendar Views. Display your calendar by Month, Week, Day or List. Pinch and zoom to control the number of weeks shown per month, and days shown per week.
Original KB number: 10106
10.5: Avoid 'resource busy' errors in Disk Utility Authored by: lexicon5 on Jul 15, '09 06:35:56AM Works perfectly well.and this issue is still present in 10.5.7.
Note
If you would like to share calendar or folder to others, or change permissions after sharing rather than opening, check the following articles at first:
- Outlook 2016/2013/2010/2007: Share an Outlook calendar with other people
- Outlook.com: Share your calendar in Outlook.com
- Outlook on the Web or Outlook Web App: Share your calendar in Outlook on the web for business
- Outlook 2016 for Mac: Share your calendar in Outlook 2016 for Mac
- Outlook for Mac 2011: Share a folder in an Exchange account
Who is it for?
Users of Outlook, Outlook for Mac, Outlook on the Web and Outlook Web App who can't open shared calendars from an invitation.
How does it work?
We'll begin by asking you questions about the Outlook version you are using and the issue you're experiencing. Then we'll take you through a series of troubleshooting steps that are specific to your situation.
Important
The third party mail services such as Gmail,AOL,Yahoo are not supported by Microsoft and this guide might not apply to them.
Estimated time of completion:
10-15 minutes.
Select your version of Outlook
Don't know which version of Outlook you are running
First determine which outlook version you are using.
For Windows
If you find Office Account:
If you find Help:
If you do not find either Office Account or Help on the File menu, then follow these steps:
- Start Outlook.
- Select File, and then find either Office Account or Help, and follow the steps for which option you find. If you do not find either option, see the steps below.
- Select Office Account, and then select About Outlook.
- The product version will be listed here.
- Select OK.
Or- Select Help, and then select Additional Version and Copyright Information.
- The product version will be listed here.
- Select OK.
Or- On the Help menu, select About Microsoft Office Outlook.
- The product version will be listed here.
- Select OK.
For Mac
- Start Outlook for Mac.
- On the Outlook menu, select About Outlook.
- The About Outlook window will appear similar to one of the following, depending on your version of Outlook for Mac.
Outlook 2016 for Mac Outlook for Mac 2011
For Outlook on the web or Outlook Web App
If you are using browser to connect an Office 365 or Exchange mailbox, select Outlook On the Web/Outlook Web App.
Or
For Outlook app on mobile or tablets devices
If you are using Outlook App on mobile devices or tablets, including Windows Phone, iPhone, iPad, Android phones, select the option Outlook App on mobile/tablet devices at the bottom.
Open a shared calendar in Outlook 2010
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook 2010, please check Share an Outlook calendar with other people.
To open a shared calendar from the Outlook sharing invitation, select Open this Calendar in the sharing invitation.
If you see something different, what problem do you encounter?
Open a shared calendar in Outlook for Mac 2011
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook for Mac 2011, see See and share multiple calendars.
The sharing invitation that you receive resembles the following screenshot. Notice that there's no option to open the shared calendar.
To open the shared calendar, follow these steps:
- On the File menu, point to Open, and then select Other User's Folder.
- Select Find User .
- Type the name of the person who granted you access, select Find, select the person's name, and then select OK.
- On the Type menu, select Calendar, and then select OK.The shared calendar appears in the navigation pane under the Shared heading.
If you cannot open the shared calendar, what problem do you encounter?
Open a shared calendar in Outlook Web App
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook Web App, please check Sharing your calendar in Outlook Web App.
To open a shared calendar from the sharing invitation, select Accept to open the shared calendar, and then you will see the shared calendar in the left pane under Other Calendar and the events in the right pane.
If you see something different, what problem do you encounter?
There is no Accept option
To work around this problem, open directly into the shared calendar.
For example, assume that your Outlook on the Web (formerly known as Outlook Web App) URL is
https://yourdomain/owa
, and that a user (user@yourdomain.com) shared his or her calendar with you.You can use the following URL to open the user's calendar:
https://yourdomain/owa/[email protected]/?cmd=contents&module=calendar
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
There is no Open this Calendar option
This problem occurs when the person who shared the calendar with you is running a later version of Outlook.
In the invitation, notice whether Microsoft Exchange appears before the shared calendar name, as in the following screenshot.
If Microsoft Exchange appears before the shared calendar name
If Microsoft Exchange appears before the shared calendar name, this typically indicates that the shared calendar is an Outlook default calendar. To open it, follow these steps:
- On the File menu, point to Open, and then select Other User's Folder.
- In the Open Other User's Folder dialog box, type the name of the user who shares the calendar with you in the Name box. In the Folder type box, select the type of shared calendar, and then select OK.
If Microsoft Exchange does not appear before the shared calendar name
If Microsoft Exchange does not appear before the shared calendar name, this typically indicates that the shared calendar is not an Outlook default calendar. In this situation, first add the user's Exchange mailbox to your Outlook profile.
- In Outlook, select Account Settings on the Tools menu.
- In the E-mail Accounts dialog box, select the E-mail tab, select your Exchange Server account, and then select Change.
- Select More Settings.
- In the Microsoft Exchange dialog box, select the Advanced tab, and then select Add.
- In the Add Mailbox dialog box, type the name of the person who shares the calendar with you, and then select OK.
- Select OK > Next > Finish > Close.
- In the navigation pane, expand Mailbox - UserNameOfFolderOwner, and then select the calendar that the user shared with you.
Note
If you cannot expand the mailbox, see the Cannot expand the mailbox of another person section of this guide for the workaround.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Cannot expand the mailbox of another person
To work around this problem, ask the person who shared the calendar with you to grant you the Reviewer permission for his or her mailbox.
Important
The following steps are performed on the computer of the person who shared the calendar with you.
- Use one of the following methods, depending on the version of Outlook that you're running:In Outlook 2007, right-click Mailbox - UserName, and then select Change Sharing Permissions.In Outlook 2010 or Outlook 2013, right-click your email address at the top of the folder list, and then select Folder Permissions.
- Select the Permissions tab, and then select Add.
- In the Add Users dialog box, specify the user with whom you want to share the calendar, select Add, and then select OK.
- In the Name list, select the name of the user whom you added, select Reviewer in the Permission Level box, and then select OK.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
You see nothing or you don't have the necessary permission to open the shared calendar
Ask the person who shared the calendar with you to perform the following steps on his or her computer.
For Outlook Desktop Client:
- Use one of the following methods, depending on the version of Outlook that you're running:In Outlook 2016, Outlook 2013 or Outlook 2010, right-click the calendar you want to share, select Share, and then select Calendar Permissions.In Outlook 2007, right-click the shared calendar, and then select Change Sharing Permissions.NoteIf the Change Sharing Permissions is grayed out or unavailable, you might be using an internet calendar managed by third-party services, such as Gmail, Yahoo or AOL. Although you can modify most Internet calendars, calendar permissions are not supported.It is also possible that your organization restricts access to sharing permissions in your account for security purposes. In this case, contact your system administrator for help.
- On the Permissions tab, select the user for whom you want to grant the permission.
- In the Permission Level list, select Reviewer, and then select OK.
For Outlook on the Web or Outlook Web App:
In Outlook on the Web or Outlook Web App, select on the left top corner or the bottom in the left pane to open the calendar. Right-click the calendar you want to share to others, and then select Sharing Permissions. Next, follow the instructions in Sharing your calendar in Outlook on the web.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Open a shared calendar in Outlook 2016
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook 2016 or Outlook 2013, check Share an Outlook calendar with other people.
To open a shared calendar from the Outlook sharing invitation, select Open this Calendar in the sharing invitation.
If you see something different, what problem do you encounter?
Open a shared calendar in Outlook 2016 for Mac
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook 2016 for Mac, see Share your calendar in Outlook 2016 for Mac.
The sharing invitation that you receive resembles the following screenshot. Notice that there's no option to open the shared calendar.
To open the shared calendar, follow these steps:
- At the bottom of the navigation bar, select Calendar.
- On the Organize tab, select Open Shared Calendar.In the Search box, type the name of the person who has granted you access to their calendar, and press Enter.
- Select their name, and select Open.NoteThe shared calendar appears in the left navigation pane under the Shared Calendar heading, with the person's name who shared the calendar below it.
If you cannot open the shared calendar, what problem do you encounter?
The Open Shared Calendar is not available
Symptoms
When you open your Calendar in Microsoft Outlook 2016 for Mac or Outlook for Mac 2011, the Open Shared Calendar button on the ribbon is unavailable.
Additionally, when you point to Open on the File menu, the Calendar option is unavailable.
Cause
This issue occurs if the Group similar folders, such as Inboxes, from different accounts check box is selected and the Hide On My Computer folders check box is cleared in General Preferences.
Workaround
To work around this issue, use one of the following methods:
Select the Exchange folder in My Calendars
- Open the calendar.
- Expand My Calendars to display the Exchange mailbox calendar, the On My Computer calendar, and calendars that are associated with any other accounts that are open in Outlook for Mac.
- Select the Exchange check box.
After you do this, the Open Shared Calendar button on the ribbon is available.
Open another user's Calendar
- On the File menu, point to Open, and then select Other Users Folder.
- Search for and then select the user whose calendar you want to open.
- In the Folder Type box, select Calendar.
- Select Open.
Change the preferences settings that are related to the On My Computer folders
- On the Outlook menu, select Preferences.
- Select General.
- Clear the Group similar folders, such as Inboxes, from different accounts check box.
- If you want, select the Hide On My Computer folders check box.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Open a shared calendar in Outlook 2013
Note
If you would like to share an Outlook calendar to other people rather than open a shared calendar from others in Outlook 2016 or Outlook 2013, please check Share an Outlook calendar with other people.
To open a shared calendar from the Outlook sharing invitation, select Open this Calendar in the sharing invitation.
If you see something different, what problem do you encounter?
Open a shared calendar in Outlook 2007
Note
If you would like to share a Outlook 2007 calendar to other people rather than open a shared calendar from others, see Share your calendar information.
To open a shared calendar from the Outlook sharing invitation, select Open this Calendar in the sharing invitation.
If you see something different, what problem do you encounter?
Additional resources
Congratulations! We are glad that this guide helps solved your problem.
Here are some additional resources that you may find useful:
Additional help
We are sorry that this guide didn't solve your problem. We recommend that you go the Microsoft Community for more help.
Here are some additional resources that you may find useful:
Workaround for opening shared calendar on Mobile/Tablet devices
If you are using Outlook App on mobile or tablet devices, such as Windows Phone, iPhone, iPad, Android Phones, you cannot see other user's calendars on these devices as they only sync your own calendars. The workaround is that you need to use Outlook on the web or Outlook Web App to view the shared calendar, or view it when on a Desktop Outlook for Windows or Mac client.
To use Outlook on the web or Outlook Web App to open the shared calendar from an invitation, sign in with your exchange or office 365 account, you will see the share invitation like this:
Select Accept to open the shared calendar, and then you will see the shared calendar listed in the left pane under Other Calendars and the events on this calendar in the right pane.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Outlook 2016 stops responding when you try to open shared calendar
This issue might occur when you upgrade to Outlook 2016 without fully uninstall the previous Outlook version, which makes Outlook 2016 offline. The solution is completely removing the older Outlook version and restart Outlook 2016. Follow the instructions:
- Tap Windows key, search Control Panel and open it.
- Select Programs > Program and Features.
- Check the list to find the older Outlook version, right-click on it and choose Uninstall to remove it.
- Reboot your computer and restart Outlook 2016.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Get other errors when you try to open shared calendar
If the other solution doesn't work for you and you get a different error message, try the instructions below:
- Make sure you have installed the latest Outlook version and fully patched.
- Enable Download shared folders.
- Select the File tab.
- Select Account Settings, and then select Account Settings.
- On the E-mail tab, select the Exchange account, and then select Change.
- Select More Settings, select Advanced tab, select Download shared folders
- Select OK, select Next, select Finish, and then select Close in the Account Settings window.
- Quit and restart Outlook.
- If still doesn't work, try to turn off Cache Exchange Mode with following steps:CautionWe do not recommend turn off cache Exchange mode, especially you are using Office 365 mailbox. If you take this action, do remember to turn it on after resolving shared calendar issue.
- Select the File tab.
- Select Account Settings, and then select Account Settings.
- On the E-mail tab, select the Exchange account, and then select Change.
- Under Offline Settings, clear the Use Cached Exchange Mode check box.
- Quit and restart Outlook.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
You receive error message when you open shared calendar in Outlook 2013
What error message do you receive?
Solution for receiving error messages when open shared calendar in Outlook 2013
This problem occurs when the following conditions are true:
- You have Outlook 2013 configured to use a MAPI over HTTP connection.
- Your primary mailbox is in cached mode.
- The Download Shared Folders option is disabled.
To resolve this issue, use this workaround to enable Download Shared Folders in Outlook 2013:
- In Outlook, select File, select Account Settings, and then select Account Settings (again).
- Select the Microsoft Exchange account, and then select Change.
- Select More Settings.
- Select the Advanced tab. Select the Download Shared Folders option.
- Select OK, select Next, select Finish, and then select Close in the Account Settings window.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
General troubleshooting for other errors when open shared calendar in Outlook 2013
If you get other errors, try the following instruction for general troubleshooting:
- Ensure the user has shared the calendar with you, with proper permissions. You can check Share an Outlook calendar with other people to get instructions about how to share calendar and grant proper permission.
- Check the right bottom corner in Outlook to see if the status looks like below to make sure Outlook is connected to the network and able to receive mail successfully, and isn't too busy performing other tasks such as updating folders.If you see , it indicates that the Outlook 2013 is connected to the network and Exchange server successfully.If you see , it indicates that the Outlook 2013 isn't connected to the network or Exchange server, check your network cable connection or contact your Network Admin.
- Try again later to see if the shared calendar works.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
You don't have permission to view a shared calendar in Outlook 2016 for Mac or Outlook for Mac 2011
When you try to open a shared Calendar folder in Microsoft Outlook 2016 for Mac or Outlook for Mac 2011, you receive the following error message even though you were granted permission to the folder:
Outlook cannot open the folder. You do not have permission to open this folder. Contact<Calendar owner's name> for permission.
This issue occurs because the owner of the folder that you want to access shares the sub calendar folder with you but does not share their default (primary) Calendar folder. To fix this issue, the calendar owner must share both the primary and the secondary Calendar folders with you. For more information, see 'You do not have permission' error message when you try to open a shared Calendar folder in Outlook for Mac.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
You get blank calendar or permission error on Mac even if you have free/busy permission in Outlook 2016 for Mac or Outlook for Mac 2011
A user grants you Free/Busy permission to their calendar, but when you try to open that user's calendar in Microsoft Outlook 2016 for Mac or Outlook for Mac 2011, you receive the following error message:
Outlook cannot open the folder. You do not have permission to open this folder. Contact <user_name> for permission.
This issue occurred because the Free/Busy feature is only available in Outlook 2010 and Outlook 2013 for Windows. To open a shared calendar in Outlook for Mac, the user must grant you permissions of Reviewer or higher. Or, you can view the user's Free/Busy information by creating a new meeting request and then adding that user in the Scheduling Assistant. For more information, see User with Free/Busy permission can't open another calendar in Outlook for Mac.
Dis this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Can't open one or more of the shared Calendar folders in Outlook 2016 for Mac or Outlook for Mac 2011
In Outlook 2016 for Mac and Outlook for Mac 2011, you cannot open a shared Calendar folder that is not a subcalendar of the user's shared default Calendar folder.
- Calendar
- Second Calendar
- Third Calendar
In this example, the Second Calendar folder is a subcalendar of the user's shared default Calendar folder. Therefore, you can open the Second Calendar folder in Outlook for Mac. However, the Third Calendar folder is not a subcalendar under the default Calendar folder. Therefore, you cannot open this folder in Outlook for Mac. To resolve this issue, have the calendar owner create all shared calendars under the default Calendar folder.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Workaround for opening shared calendar on Mac system
We recommend using Outlook on the Web or Outlook Web App as a workaround to open shared calendar in Mac system.
Log in Outlook on the Web or Outlook Web App with your Exchange or Office 365 account in browser, select Accept in the invitation email, and then you will see the shared calendar in the left pane under Other Calendar and the events in the right pane.
Note
If you don't know the Outlook web url, please contact your system admininistrator for help.
If you see something different, what problem do you encounter?
Open a shared calendar in Outlook 2016 (only for Office 365 users on Monthly Channel)
To open a shared calendar from the Outlook sharing invitation, select the Accept button in the sharing invitation. The shared calendar will be added to your Calendar pane under the Shared Calendars section.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Open a shared calendar in Outlook on the web
To open a shared calendar from the sharing invitation, select the Accept button in the sharing invitation. The shared calendar will be added to your Calendar pane under the People's calendars section.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Open a shared calendar in Outlook mobile apps for iOS & Android
To open a shared calendar from the Outlook sharing invitation, select Accept button in the sharing invitation. The Accept button will then change to View and you can then select it to view shared calendar. You can also locate the Calendar pane in your Outlook app to view a shared calendar by selecting the hamburger menu icon and then selecting that shared calendar from the list of calendars that is displayed in that menu.
Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Open a shared calendar from Outlook.com
When you share your
Outlook.com
calendar with people, they can add it directly to their calendar view in Outlook. Depending on the permission that you give them, they can view your calendar or edit it.For detailed information about how to share a calendar in
Outlook.com
, refer to Share your calendar in Outlook.com.Did this solve your problem?
- If yes, see Additional resources.
- If no, see Additional help.
Original KB number: 10092
Who is it for?
Tenant administrators. Elevated access will be required for many of the steps.
How does it work?
We'll begin by asking you the issue you are facing. Then we'll take you through a series of troubleshooting steps that are specific to your situation.
Estimated time of completion:
30-60 minutes.
Welcome to the hybrid environment free/busy troubleshooter
Select the option that best describes the issue that you are facing:
Note
If you want to review how free/busy works in a hybrid deployment, select the I want to better understand how Hybrid Free/Busy is supposed to work option.
On-premises Exchange server version in your environment
To better understand how Hybrid Free/Busy is supposed to work, review the following flowcharts. Select the version of the on-premises Exchange server that matches your environment:
The Exchange 2010/2013 free/busy workflow
The following diagram shows the Exchange 2010/2013 free/busy workflow:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Welcome to the hybrid environment free/busy troubleshooter.
The Exchange 2007 free/busy workflow
The following diagram shows the Exchange 2007 free/busy workflow:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Welcome to the hybrid environment free/busy troubleshooter.
Exchange 2003 free/busy workflow
The following diagram shows the Exchange 2003 free/busy workflow:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Welcome to the hybrid environment free/busy troubleshooter.
Does Free/busy work on-premises
Sign in to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment.
Were you able to see the Free/busy information?
- If yes, see Cloud user cannot see On-premises user's Free/Busy.
- If no, see You have an on-premises free/busy issue.
You have an on-premises free/busy issue
This troubleshooter is used to diagnose free/busy issues in a hybrid environment. This does not seem to be your immediate issue. After the on-premises free/busy issues are addressed, restart this troubleshooter.For information about how to troubleshoot some common on-premises free/busy issues, see Troubleshooting Free/Busy Information for Outlook 2007.
Cloud user can't see On-premises user's Free/Busy
Use the following methods to verify that Autodiscover can be resolved from an external source and that the Firewall is open.
Method 1: Verify that Autodiscover is resolving to the on-premises Exchange CAS server
- From an external computer, open Command Prompt and type the following commands and press ENTER after each command:
- NSLookup
- autodiscover.<Your_Domain.com>
- In the response to the command, the 'Address' value should be the external IP of the on-premises Exchange CAS server. For example: Name:
autodiscover.contoso.com
Address: 38.96.29.10
Method 2: Verify that you can send an Autodiscover POST request to potential Autodiscover URLs
- Go to Microsoft Remote Connectivity Analyzer.
- On Microsoft Office Outlook Connectivity Tests select Outlook Autodiscover, and then select Next.
- Complete the Outlook Autodiscover form (Email address, User Name and password), then select Perform Test.
If the Exchange connectivity tests fail for autodiscover, check the on-premises Autodiscover Internet Access configuration. For more information about how to do this, see the Microsoft TechNet topic Configure the Autodiscover Service for Internet Access.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user cannot see On-premises user's Free/Busy (if issue isn't resolved)
Verify that the autodiscover endpoint is pointing to the on-premises Exchange Hybrid Server(s).
Check the IIS logs on the Exchange Hybrid server to verify that the Autodiscover POST request is being received by this server:
- On the Exchange Hybrid Server, select Start > Run, type %SystemDrive%inetpublogsLogFiles, and then press ENTER.
- Open the W3SVC1 folder, then open the most recent IIS log file.
- Search for Autodiscover.
- The following screenshot shows an example of the Autodiscover POST request on IIS log:
If you do not see any entry for Autodiscover in your on-premises Exchange hybrid deployment server, the firewall may be pointing to a wrong CAS server.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user cannot see On-premises user's Free/Busy (if issue not resolved)
Is the domain name present in the org relationship?
To verify the domain name value in the Organization Relationship, follow these steps:
- Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
- In Windows PowerShell, run the following command:
- Check DomainName value. The vanity domain (
yourdomain.com
) should be present. - If the DomainName value is missing your vanity domain, run the following command:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user can't see On-premises user's Free/Busy (if issue can't be solved)
Is IIS handler Mapping missing?
Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the Autodiscover endpoint.
- On the on-premises Exchange 2010 hybrid deployment server, open Internet Information Services (IIS) Manager.
- Expand ServerName > Site > Default Web Site, and then select Autodiscover.
- On IIS section, open Handler Mappings. The following screenshot shows an example of the svc-Integrated handler mapping in IIS:
If the IIS is missing the svc-Integrated handler mapping, see 'Exception has been thrown by the target' error in a hybrid deployment of Microsoft 365 and your on-premises environment.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user cannot see On-premises user's Free/Busy (if issue is still not solved)
Follow these steps to verify if EWS has External URL set:
- On the on-premises Exchange hybrid deployment server, open Exchange Management Shell, and then run the following cmdlet:
- If the ExternalURL is missing on the Exchange hybrid deployment server, run the following cmdlet:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user cannot see On-premises user's Free/Busy (if issue still not resolved)
Verify that the Microsoft Exchange Web Services (EWS) is resolvable and there are no firewall issues.
Check IIS logs on the Exchange 2010/2013 CAS server(s) to confirm that Web Services request is being received by this server. To do this, follow these steps:
- On the Exchange 2010/2013 CAS server, select Start > Run, type %SystemDrive%inetpublogsLogFiles, and then press ENTER.
- Open the W3SVC1 folder, and then open the latest IIS log file.
- In the latest IIS log file, search for exchange.asmx/wssecurity. The following screenshot shows an example of the request in the IIS log:
- If you do not see any entry for exchange.asmx/wssecurity in your on-premises Exchange 2010/2013 hybrid deployment server, the firewall may be pointing to a wrong CAS server, or you may have pre-authentication configured on the firewall. For information about how to bypass firewall pre-authentication, see Configure Forefront TMG for a hybrid environment.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user cannot see On-premises user's Free/Busy.
Cloud user can't see On-premises user's Free/Busy (if issue isn't solved)
Is IIS handler mapping missing on EWS?
Determine whether Internet Information Services (IIS) configuration is missing the svc-Integrated handler mapping for the EWS endpoint
- On the on-premises Exchange hybrid deployment server, open Internet Information Services (IIS) Manager.
- Expand ServerName > Site > Default Web Site, and then select EWS.
- In the IIS area, open Handler Mappings. The following screenshot shows an example of the svc-Integrated handler mapping in IIS:
- If the IIS is missing the svc-Integrated handler mapping, see Exception has been thrown by the target' error in a hybrid deployment of Microsoft 365 and your on-premises environment.
Did this solve your issue?
- IF yes, congratulations, your issue is resolved!
- If no, see Cloud user can't see On-premises user's Free/Busy.
Cloud user can't see On-premises user's Free/Busy (if issue is still not solved)
Is WSSecurity enabled as an authentication method?
On the on-premises Exchange hybrid deployment server, run the following command in Exchange Management Shell:
If the WSSecurity is missing for ExternalAuthenticationMethods is missing on Exchange hybrid deployment server run the following command:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Cloud user can't see On-premises user's Free/Busy.
Cloud user cannot see On-premises user's Free/Busy (should verify Org Relationship settings)
Verify Org Relationship settings are configured correctly to enable Free/busy for the users.
For Online Settings
- Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect to Exchange Online using remote PowerShell.
- In Windows PowerShell, run the following command:
The output should resemble the following
- TargetApplicatioURI:
FYDIBOHF25SPDLT.Contoso.com
- TargetAutodiscoverURI:
https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
- DomainNames: {
Contoso.com
} - FreeBusyAccessEnabled: True
- FreeBusyAccessLevel: LimitedDetails
If a value must be changed, use the
set-OrganizationRelationship
cmdlet to fix the property. For more information about syntax and options, see Set-OrganizationRelationship.For On-Premises settings
- On the Exchange 2010/2013 CAS, run the following command in the Exchange Management Shell:
The output should resemble the following:
- TargetApplicatioURI:
outlook.com
- TargetAutodiscoverURI:
https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
- DomainNames: {
xxxx.mail.onmicrosoft.com
,contoso.com
} - FreeBusyAccessEnabled: True
- FreeBusyAccessLevel: LimitedDetails
If a value must be changed, use the
set-OrganizationRelationship
cmdlet to fix the property. For more information about syntax and options, see Set-OrganizationRelationship.Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Contact support.
On-Premises user can't see cloud user's Free/busy
On which version of Exchange is the on-premises users' mailbox located?
Your Exchange 2003 user cannot see cloud user's free/busy
Can you reproduce the issue by using an on-premises Exchange 2010 mailbox?
- Log on to Outlook or an OWA client as a user who has an Exchange 2010 on-premises mailbox.
- Create a new meeting request and add a cloud user to the meeting request.
- When you view the scheduling assistant do you see hash marks for the cloud user?
- If yes, see On-premises user cannot see cloud user's Free/busy.
- If no, see Your Exchange 2003 user cannot see cloud user's free/busy.
Your Exchange 2003 user cannot see cloud user's free/busy (if issue not solved)
Verify that there is no hard-coded Public folder routing that would prevent the legacy Free/busy request from succeeding.
Verify that the
ms-Exch-Folder-Affinity-List
attribute on the Exchange Server 2003 properties has Exchange 2010 ObjectGUID with the lowest cost (The format of this property is as follows: {guid of server},cost).- On a Domain Controller, select Start, select Run, type adsiedit.msc, and then select OK.
- Right-click ADSI Edit, and then select Connect to.
- On Select a well known Naming Context, select Configuration, and then select OK.
- Expand Configuration > Services > Microsoft Exchange > First Organization > Exchange Administrative Group (FYDIBOHF23SPDLT) > Servers.
- Right-click Exchange 2010 server, and then select Properties.
- Copy the objectGUID value and then paste it in a notepad text file.
- Move to Configuration > Services > Microsoft Exchange > First Organization > First Administrative Group > Servers.
- Right-click Exchange Server 2003, and then select Properties.
- Verify that
ms-Exch-Folder-Affinity-List
value is set with Exchange 2010 objectGUID. If the Exchange 2010 objectGUID is not listed onms-Exch-Folder-Affinity-List
, you can add it by using the format: {guid of server},cost.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Contact support.
Your Exchange 2003 user cannot see cloud user's free/busy (can't reproduce)
Is the External Free/busy present and replicated correctly?
Add the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder. To do this, follow these steps:
- Connect to the on-premises Exchange 2010 SP1 or later public folder server.
- Open Windows PowerShell.
- Run the cmdlet
Add-PsSnapin Microsoft.Exchange.Management.Powershell.Setup
. - Run the cmdlet
Install-FreeBusyFolder
.
Note
The OU=EXTERNAL (FYDIBOHF25SPDLT) public folder should only be present on Exchange 2010 servers and NOT replicated to Exchange 2003 or Exchange 2007.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Your Exchange 2003 user cannot see cloud user's free/busy.
Your Exchange 2003 user cannot see cloud user's free/busy (if issue not resolved)
Verify that the recipient object on the on-premises server has the correct LegacyExchangeDN configured.
Every cloud mailbox will have a corresponding on-premises Mail enabled object. For this kind of Free/busy query, we use the LegacyExchangeDN to route our request to the Proper Public folder server. To make sure that this value is accurate, follow these steps:
- On the Exchange 2010 server, run the following command in the Exchange Management Shell:where username is the name of the cloud user that you are trying to see free/busy information for.
- In the results, verify that the External (FYDIBOHF25SPDLT) is in the path. For example, the results should show the path as follows:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Your Exchange 2003 user cannot see cloud user's free/busy.
Your Exchange 2003 user cannot see cloud user's free/busy (if issue isn't resolved)
Verify Permissions on Public folder.
To use the Exchange 2010 Public Folder Management Console to change the client permissions for the External (FYDIBOHF25SPDLT) free/busy replica, follow these steps:
- Start the Exchange 2010 Exchange Management Console.
- In the console tree, select Toolbox.
- In the result pane, select Public Folder Management Console, and then in the action pane, select Open Tool. The Public Folder Management Console appears.
- In the Public Folder Management Console, in the action pane, select Connect to Server.
- In Connect to server, select Browse to view a list of the available Mailbox servers that contain a public folder database.
- In Select Public Folder Servers, select the Exchange 2010 server. Select OK, and then select OK.
- In the Public Folder tree, move to System Public Folder > SCHEDULE+ FREE/BUSY.
- In the Result pane, right-click EX:/O=FIRST ORGANIZATION/OU=EXTERNAL (FYDIBOHF25SPDLT), and then select Properties.
- On the Permissions tab, confirm that Edit all permission level is selected for the **Default user:
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Your Exchange 2003 user cannot see cloud user's free/busy.
Your Exchange 2003 user cannot see cloud user's free/busy (if issue is still not solved)
Is the arbitration mailbox missing or corrupted?
The Arbitration mailbox can be edited by using ADSIEdit. The federated.email account should be located in the default users container of Active Directory for the Exchange 2010 domain.
Use one of the following options:
- Use adsiedit.
- Connect to the default naming context in Active Directory.
- Browse to the Users container and view the properties of the federated email account.
- Change the proxyaddress attributes of the account to either have ONE of the SMTP addresses already federated, or add the already existing proxy address namespace present into the federation trust.
- From the Exchange Server 2003 open Active Directory Users and Computers.
- Move to the Users container and right-click the FederatedEmail account - then select Properties.
- If you go to the email addresses tab that you can add another proxy address to match the federation namespaces already configured, or add the pre-existing primary SMTP namespace to the federation trust.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Your Exchange 2003 user cannot access cloud user's free/busy.
Your Exchange 2007 user cannot access cloud user's free/busy
Can you repro with an on-premises Exchange 2010 or 2013 mailbox?
- Sign in to your Outlook or OWA client as a user who has an Exchange 2010 or 2013 on-premises mailbox.
- Create a new meeting request and add a cloud user to the meeting request.
- When you view the scheduling assistant do you see hash marks for the cloud user?
- If yes, see Exchange 2010/2013 user cannot see cloud user's free/busy.
- If no, see Your Exchange 2007 user can't access cloud user's free/busy.
Your Exchange 2007 user can't access cloud user's free/busy
Check the availability address space to make sure that it has the correct settings. This might be a misconfiguration of the AvailabilityAddressSpace. Check that ProxyURL value on AvailabilityAddressSpace configuration matches the InternalURL of the Exchange 2010/2013 CAS Web Service virtual directory. To do this, follow these steps:
- On the on-premises server, run the following commands in Exchange Management Shell:
- If the ProxyURL and InternalURL values do not match, run the following commands:
- If the
ProxyURL
andInternalURL
values do match, make sure that you can access the URL from the Exchange 2007 CAS server. To do this, move toProxyURL
of theAvailabilityAddressSpace
from CAS 2007. Authenticate with the Exchange 2007 source mailbox credential. The expected result is as follows:
Note
The InternalURL of the Exchange 2010/2013 CAS Web Service virtual directory should differ from Exchange 2007 CAS Web Service virtual directory.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Contact support.
Exchange 2010/2013 user cannot see cloud user's free/busy
Sign in to an on-premises user's mailbox and then try to view the Free/Busy for another on-premises user. This test is to verify that you do not have any issues with availability information retrieval within your on-premises environment.
Were you able to see the Free/busy information?
- If yes, see On-premises user cannot see cloud user's Free/busy.
- If no, see On-premises Free/busy is not working for 2010/2013.
On-premises user cannot see cloud user's Free/busy
Determine what error message you are receiving from OWA.
Busy Season For Machu Picchu
- Use the affected user's account to log on to the on-premises OWA.
- Create a new meeting request, and then add the on-premises user to the meeting.
- When the Hash marks are returned rest the pointer over them to display the error message. Note the error code number in the error message.
Select the appropriate error message in the following list to help narrow the troubleshooting steps that you must follow:
- The attendee's server couldn't be found. For more information, please contact your helpdesk. (Error Code: 5039).
- The attendee's server couldn't be contacted. (Error Code: 5016).
- You don't have permission to see free/busy information for this attendee. (Error code 5037).
Exchange 2010/2013 user cannot see cloud user's free/busy (Error Code 5039)
Busy For My Work
If you must have web proxy settings in your environment, verify that the on-premises Exchange 2010 and Exchange 2013 servers are set to use it.
Busy Forms
On the on-premises Exchange 2010 and Exchange 2013 server(s), run the following command in the Exchange Management Shell:
In most environments the results will be blank. However, if you have an outgoing proxy in your on-premises environment you may have to configure the correct proxy settings.
To resolve this issue, run the following command, where the address and port number
http://192.168.5.56:8080
is replaced with your server address and port number:Did this solve your issue?
Busy To Do For Mac And Cheese
- If yes, congratulations, your issue is resolved!
- If no, see Exchange 2010/2013 user cannot see cloud user's free/busy.
Exchange 2010/2013 user cannot see cloud user's free/busy (if issue not resolved)
Make sure that the time set on your server is not inaccurate by more than 5 minutes. If the server time is more than 5-minutes difference from real time, the communications with the federation gateway become invalid. This causes free/busy to fail.
For information about how to fix server time issues, see How to configure an authoritative time server in Windows Server.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Contact support.
Exchange 2010/2013 user cannot see cloud user's free/busy (Error Code 5016)
Determine whether the correct target address is specified on the MEU on-premises. Every Cloud Mailbox will have a corresponding on-premises object. This object must have the correct remote routing address (also known as the target address) specified. The remote routing address should contain a domain name similar to
TenantName.Mail.OnMicrosoft.com
.To verify that the remote routing address is set, follow these steps:
- On the Exchange 2010 server or Exchange 2013 server, run the following command in the Exchange Management Shell:where username is the name of the cloud user that you are trying to see free/busy information for.
- Verify that the address contains
TenantName.Mail.OnMicrosoft.com
Note
If you did not use the Hybrid configuration wizard, the domain name should reflect the remote routing domain that you have selected.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Exchange 2010/2013 user cannot see cloud user's free/busy.
Exchange 2010/2013 user cannot see cloud user's free/busy (Error code 5037)
Verify that the Org Relationship settings are configured correctly to enable Free/busy for the users.
For Online Settings
Connect to Exchange Online by using Windows PowerShell. For more information about how to do this, see Connect Windows PowerShell to the Service.
In Windows PowerShell, run the following command:
The output should resemble the following:
- TargetApplicatioURI:
AppURL.Contoso.com
- TargetAutodiscoverURI:
https://autodiscover.contoso.com/autodiscover/autodiscover.svc/wssecurity
- DomainNames: {
Contoso.com
} - FreeBusyAccessEnabled: True
- FreeBusyAccessLevel: LimitedDetails
If a value must be changed, use the
set-OrganizationRelationship
cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.For On-Premises settings
From the Exchange 2010/2013 CAS, run the following command in Exchange Management Shell:
The output should resemble the following:
- TargetApplicatioURI:
outlook.com
- TargetAutodiscoverURI:
https://podxxx.outlook.com/autodiscover/autodiscover.svc/wssecurity
- DomainNames: {
xxxx.mail.onmicrosoft.com
,contoso.com
} - FreeBusyAccessEnabled: True
- FreeBusyAccessLevel: LimitedDetails
If a value must be changed, use the
set-OrganizationRelationship
cmdlet to fix the property. For more information about syntax and options to do this, see Set-OrganizationRelationship.Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Exchange 2010/2013 user cannot see cloud user's free/busy.
Exchange 2010/2013 user cannot see cloud user's free/busy (if issue isn't solved)
Verify that a token can be created that has test-federation trust.
From the on-premises environment, verify that you can retrieve a delegation token that will be used for Free/busy authorization. To do this, follow these steps:
Busy To Do For Mac Os
- Open the Exchange Management Shell from the on-premises Exchange 2010 or 2013 server.
- Run the command
Test-FederationTrust -UserIdentity [email protected] -verbose
where User is the on-premises user who has issues viewing the cloud user's free/busy information. - The output should show success for every test. If there is a failure, use the Hybrid Configuration Wizard again to try to reset the federation trust.
Did this solve your issue?
- If yes, congratulations, your issue is resolved!
- If no, see Exchange 2010/2013 user cannot see cloud user's free/busy.
Busy For A While
On-premises Free/busy is not working for 2010/2013
This guide is used to troubleshoot Hybrid free/busy issues. Based on you answers, you have on-premises issues. For information about how to troubleshoot common on-premises free/busy issues, see Troubleshooting Free/Busy Information for Outlook 2007.
Contact support
Sorry, we cannot resolve an unidentified issue by using this guide. For more help to resolve this issue, go to Microsoft Support.
Other useful resources:
Tools and resources
The following are some additional tools and resources for diagnosing issues with Hybrid Free/busy:
Is this information helpful?
- If yes, congratulations, your issue is resolved!
- If no, sorry, we cannot resolve this issue by using this guide.