locked
Upgraded Exchange and free busy is no longer working RRS feed

  • Question

  • We upgraded our exchange server to the most resent release with the cumulative update.  It is exchange 2013 on Windows Server 2012 R2.  Most of our end users are now unable to use the Scheduling assistant to see the free/busy of other employees in the company.  The error that we are getting when they pull it up is "No information.  No free/busy information could be retrieved.  your server location could not be determined.  Contact your administrator."  All of the free/busy issues that I am able to find out on the web are pretty old and don't seem to apply.
    Friday, May 18, 2018 9:40 PM

Answers

  • It looks like it is an issue with our Barracuda LB. When we bypass it and go directly to the exchange server the issue does not persist. Thanks for your suggestion though.
    • Marked as answer by Telchar18 Tuesday, May 22, 2018 1:59 PM
    Tuesday, May 22, 2018 1:59 PM

All replies

  • Hi

    Have you checked on OWA to see if free/busy information displays normally?

    Recently, these is a known issue that free/busy shows slashed lines in Scheduling Assistant. Please refer to the details in this link to see whether this is the case for you.

    How do you input the recipient’s account? The attendee’s name should be the same in the GAB. Please try clicking Check Names to see the result.

    Besides, we have to be given the free/busy permission in order to view free/busy information of someone’s calendar. Please check this in Calendar Permissions. Set the default permission to Free/Busy time.


    Any updates, please feel free to tell me.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Perry-Pan Monday, May 21, 2018 2:45 AM
    Monday, May 21, 2018 2:45 AM
  • Hi,

    I'm wondering whether the information above is helpful to you.

    Please feel free to tell me if you have other concern about this issue.

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, May 22, 2018 1:37 AM
  • It looks like it is an issue with our Barracuda LB. When we bypass it and go directly to the exchange server the issue does not persist. Thanks for your suggestion though.
    • Marked as answer by Telchar18 Tuesday, May 22, 2018 1:59 PM
    Tuesday, May 22, 2018 1:59 PM
  • Hi,

    So glad to see that your issue has been solved and thank you for sharing here.

    If you have other concern, please feel free to post here.

    Have a nice day:)

    Regards,

    Perry


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 23, 2018 1:05 AM