This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 73%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWJ%3C/text%3E%3C/svg%3E)
Afternoon,
I am migrating Onsite Exchange 2010 server mailboxes to Onsite Exchange 2016 server mailboxes. Everything SEEMS to work fine. I have moved about 10 mailboxes with no issue. The email clients automatically associate the mailbox to the correct exchange server without manual assistance. I have noticed the following behavior. I can send and receive external as well as internal email messages. I can also send and receive calendar invites between the two servers. The calendar events are updated correctly when accepted, rejected or when scheduling a new time. I can even write appointments directly to calendars between both servers.
The issue occurs when trying to use scheduling Assistant. I receive the following:
No Information. No Free/Busy information could be retrieved.
The recipient's server could not be contacted. Contact Administrator.
I have rebooted the exchange 2016 server and it did not correct the problem. I have tried using OWA as well as Outlook client with the same results.
Any assistance would be greatly appreciated.
Thank you very much.
Wendell Jones
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi @Wendell Jones ,
To narrow down the issue, I wonder if the meeting sender and recipient are on the same Mailbox server?
Please have a check whether the correct permissions are set on the Calendar folder. You could set up by right clicking on the Calendar folder and choosing properties.
Could you please recreate the mail profiles for that users on exchange2016 and restart the Microsoft Exchange Mailbox Assistants service on the exchange server to see if it has any changed.
Moreover, please have a check that both servers have firewalls enabled and that there are any third-party software.
Thank you for your reply. I have checked the permissions on the calendars and they were already set as you directed. Free/Busy time is set by default to read. When you direct me to recreate the mail profile, I believe you meant on an outlook client. So I did that. I then stopped and restarted the MSE Mailbox Assistant service. That made no difference. I still get the error that the server cannot be contacted using the scheduling assistant.
I turned off the firewall just to see if that was causing the communication issue and it made no difference.
All other calendar features appear to be working EXCEPT with scheduling assistant. Shared Calendar feature works just fine in both directions. Is there something else I should check?
I appreciate your assistance with this issue.
Wendell Jones
Hi @Wendell Jones ,
Does this issue have any updates?
If it has been resolved, please click "Accept as answer" to mark useful post or share your solution, your action would benefit others who have similar issues.
If you have any questions or need further assistance, please feel free to post back. Thanks!
Hi @Wendell Jones ,
The possible cause is that after the mailbox move is complete, the Exchange Server 2016 continues to proxy the EWS request to Exchange Server 2010 .
Please refer to the resolution in the following link to restart the Autodiscover Application Pool and the Exchange Web Services Application Pool and see if it works.
Can't see Free/Busy info after a mailbox moves to Exchange 2013 or 2016 - Exchange | Microsoft Learn
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello Aholic Liang-MSFT,
Thank you for your reply. I have run the commands on the Exchange 2016 server,. I then restarted my outlook client and the problem still persists. I DID check the HTTPPROXY\EWS log and found that "WebExceptionStatus=ProtocolError;ResponseStatusCode=500" for the user I was testing. So it seems we are on the right track, but the solution did not work. Is there a different solution that could be looked into? In the meanwhile, I will leave the request for scheduling assistant running to see if it ever goes through like in the example from the article. Hopefully the logs will not grow too large.
I appreciate your assistance.
Wendell Jones
Hi,
Please recreate the mail profile again and have a check that virtual directory points correctly to Exchange 2016.
If not ,please refer to this guide to set up the virtual directory.
Hi,
It has been a few days and I am checking in to see how things are going on with this issue. Does this issue have any updates? please feel free to post back. Thanks!