none
Office 2010 - Free/Busy not showing for other users in Outlook Calendar

    Question

  • Outlook 2010 Beta not showing anyone's (except my own) Free/Busy time in Calendar for existing or new appointments. Worked fine with Outlook 2007 client.
    Wednesday, December 09, 2009 1:43 PM

All replies

  • I have the same issue.  I'm using the latest beta on Win7 Business x64 with hosted Exchange from Microsoft Online Services.

    Jeff
    Thursday, December 10, 2009 8:21 PM
  • Hi,

    I have the same problem, I'm using Office 2010 Beta and I can't see the Freebusy information for the all user's with Outlook 2007.

    so do u have some solution for this problem ?

    Thk's
    Thursday, December 10, 2009 9:12 PM
  • I've had the same problem since I installed Office 2010 Beta. This wasn't a problem with the CTP. I have Outlook 2010 Beta connected to Exchange 2007. The odd thing is, when I connect via a VPN connection from home, it works fine. But when I'm connected to the network from the office, it doesn't work.

    Eric

    Friday, December 11, 2009 10:51 PM
  • This is not a problem when connected to Exchange 2003, but now that the company has upgraded to Exchange 2007, I am experiencing the same problem.  Hopefully this info. helps to narrow down possible causes.
    Tuesday, February 23, 2010 5:59 PM
  • What build of Outlook 2010 are you using?  Check File | Help and you'll see it after "Version:" on the right side.
    -B-
    http://www.officeforlawyers.com
    Author: The Lawyer's Guide to Microsoft Outlook
    Tuesday, February 23, 2010 6:11 PM
  • Try to CTRL+Click the Outlook icon on the system tray, choose "Test E-mail Autoconfiguration", uncheck the two that have "guesssmart" in the name and run the test.  What do you get?

    -B-
    http://www.officeforlawyers.com
    Author: The Lawyer's Guide to Microsoft Outlook
    Thursday, March 04, 2010 6:38 PM
  • I have the same issue, using Office 2010 Beta. Version 14.0.4536.1000 (32 bit) (I hope I didn't make any typo's as I cannot copy that text)

    We are using exchange.

    The result pane states: Autoconfiguration has started, this may take up to a minute. Autoconfiguration was unable to determine your settings. Again I was unable to copy paste....

    The log about the auto discovery states: AutoDiscover to https://ourinternaldomain/autodiscover/autodiscover.xml  starting

    next:

    AutoDiscover request completed with http status code 503

    AutoDiscover to https://ourinternaldomain/autodiscover/autodiscover.xml  failed (0x80004005)

    the log ends with Srv record lookup for nab.com.au failed (0x8004010F)

    Cheers, Stephan

     

    Monday, March 29, 2010 12:33 AM
  • I also have the same problem.  And I am located on Redmond campus as a biz partner.  If you need to see a local repro, I can show  you guys.
    Wednesday, April 07, 2010 9:22 PM
  • Hmmm....sounds like it might be a DNS problem.  Have you checked your domain's DNS servers to make sure they're working properly?
    -B-
    http://www.officeforlawyers.com
    Author: The Lawyer's Guide to Microsoft Outlook
    • Proposed as answer by Raf_1971 Wednesday, October 31, 2012 12:52 AM
    Wednesday, April 07, 2010 10:40 PM
  • Well exchange works fine, so I am not sure. Since I am not in my company's office and must access via VPN, I thought that may contribute to the problem. But recently others in our corporate office have also started using Office 2010 Beta and experience the same issue.  They normally used 2007 and that for sure does not have this problem in their environment.

    Wednesday, April 07, 2010 11:16 PM
  • Well exchange works fine, so I am not sure. Since I am not in my company's office and must access via VPN, I thought that may contribute to the problem. But recently others in our corporate office have also started using Office 2010 Beta and experience the same issue.  They normally used 2007 and that for sure does not have this problem in their environment.


    Are you connecting via Outlook Anywhere or just a straight MAPI connection across the VPN?  Are you able to browse to that autodiscover.XML file in IE?
    -B-
    http://www.officeforlawyers.com
    Author: The Lawyer's Guide to Microsoft Outlook
    Thursday, April 08, 2010 12:04 AM
  • For sure the Outlook Anywhere "check-mark" is not checked in the exchange mail account properties.

    Not sure how to check if it is straight MAPI, I am guessing default exchange is running MAPI?

    As for autodiscover.xml, I tried to access the https://ourinternaldomain/autodiscover/autodiscover.xml (replacing the ourinternaldomain with exchange server netbios or IP), but I was not able to resolve the address...

     

    Any other suggestions would be greatly appreciated. I got some internal executives pinging me for a solutions already...

     

     

    Monday, April 12, 2010 6:13 PM
  • Like another poster in this thread, I did not have this problem with Outlook 2010 and Exchange 2003, but now that we have migrated to Exchange 2007 I am no longer able to see free/busy time.  Other communication with the server seems to be working just fine.  I'm running Outlook 2010 v14.0.4760.1000 (64-bit) on Windows 7 Ultimate (64-bit).  Any ideas?
    Wednesday, June 02, 2010 3:47 PM
  • Ok, the answer seems to be much the same as has been described in this thread already.  My PC is not part of the domain, so the autodiscover url was being inferred by Outlook instead of being pulled from Active Directory.  The issue i was having is that our internal DNS is not resolving the correctly inferred autodiscover url.  I verified this by pulling my PC off our network, and plugging in an air card.  Once I did that, i was able to successfully use the "Test E-mail autoconfiguration" tool, where previously this was crapping out trying to resolve the domain.

     

    The solution: either add my PC to the domain, or get the DNS issues resolved.

    Wednesday, June 02, 2010 7:59 PM
  • We had the same problem:

    Free/Busy caused Outlook 2010 cras (calendars, Mouse-Over on Domain-User-Name in Outlook). Out-of-Office feature in Outlook 2010 din't work

    After installing the following updates on our Exchange Server, the problem has been solved:

     

    - MS .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x64

    - Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0 x64 (KB963707)

    - Update Rollup 10 for Exchange Server 2007 Service Pack 1 (KB981407)

    Wednesday, July 14, 2010 6:40 AM
  • Override the DNS with the hostfile.  I just added the wrong autodiscover hostname to my windows hostfile with the IP address of our exchange server and trusted the selfsigned certificate that was offered.  Free-busy works like a charm.

     

    Thursday, September 22, 2011 5:24 PM
  • make sure the users haven't got "use cached exhange mode" ticked in the mailbox properties. this causes free/busy data to show as "busy" blocks only.
    Regards Ian
    Friday, January 06, 2012 10:07 AM
  • make sure the users haven't got "use cached exhange mode" ticked in the mailbox properties. this causes free/busy data to show as "busy" blocks only.
    Regards Ian
    Friday, January 06, 2012 10:08 AM
  • We have finally fixed out Out of Office issues.

    In the end it was nothing to do with exchange or outlook.

    It was our proxy server the was causing the issues.

    Once we added our domain to the "bypass authentication for domains" out of office free/busy time works great

    Friday, January 20, 2012 11:00 AM
  • I found the root cause of the problem,

    I would like to explain that the issue occurs because when you adding delegate to a mailbox. It only grant the delegate has permission to access the room mailbox calendar folder. However, when Outlook trying to access the forwarded meeting request, it also need to access another hidden folder called Free/Busy Data. However, due to the permission issue, we could not access the folder and encounter the error. After granting delegate to have full mailbox access permission to the room mailbox, we will not encounter the error any more.

    The Fix:

    1. Managing Exchange 2010 with Remote PowerShell

    $cred = Get-Credential

    $s = New-PSSession -ConfigurationName Microsoft.Exchange –ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic-AllowRedirection

    $importresults = Import-PSSession $s

     

    2. Command to grant delegate to have full access permission to the room mailbox

    Add-MailboxPermission -Identity "Room" -User username -AccessRights FullAccess

    Meeting Room1

     

    Add-mailboxpermission “Meeting Room1” –AccessRights FullAccess –User User username@microsoft.com

    Friday, January 27, 2012 3:26 AM
  • Hmmm....sounds like it might be a DNS problem.  Have you checked your domain's DNS servers to make sure they're working properly?
    -B-
    http://www.officeforlawyers.com
    Author: The Lawyer's Guide to Microsoft Outlook

    Hi,

    In my case it was fixed configuring autodiscover.domain.com to my exchange server in DNS and all is working fine now. Thanks

    Wednesday, October 31, 2012 12:53 AM