Out of Office Assistant settings cannot be displayed for Outlook 2007 clients RRS feed

  • Question

  • Now here's one I've been battling all day.


    On our Exchange 2007 Out of Office Assistant has died for all Outlook 2007 clients, having been working for over a year. It died after patch night last week. Now only the "Your Out of Office settings cannot be displayed, because the server is currently unavailable" message appears.


    Autodiscover has not been changed, nor DNS, nor any other setting. In fact if you do "test e-mail autoconfiguration" from Outlook 2007 you get the correct result.


    Test-OutlookWebServices, however, crashes. Immediately after event ID 1006, where it successfully contacts the Autodiscover service, I get

    "WARNING: an unexpected error has occurred and debug information is being generated: Object reference not set to an instance of an object. At line:1 char:24 + test-OutlookWebServices <<<< | fl".

    And in the event log appears:

    "EventType e12, P1 c-rtl-amd64, P2 08.01.0240.006, P3 powershell, P4 m.e.management, P5 m.e.m.s.availabilitytest.validate, P6 system.nullreferenceexception, P7 4ab8, P8 08.01.0291.001, P9 NIL, P10 NIL."

    I think that is an ASP.NET error there. Which means it is because I not only installed the security fixes on the Exchange Server, I also installed SP1 for .NET Framework 3.5, which in turn also patched the .NET Framework 2.0 to service-pack 2 level. Looks like .NET Framework 2.0 SP2 and Exchange Server 2007 SP1 may have a problem. Running aspnet_regiis.exe -i has made no difference.


    For now I've had to tell people to use Outlook Web Access to control Out of Office.


    I know this is my own fault for rushing in a new patch and busting a working set-up. Not sure how to get out of this one. Trying to uninstall .NET Framework 2.0 SP2 feels too dangerous.

    Monday, August 18, 2008 5:30 PM

All replies

  • Glad to hear I am not the only one. ( Sorry for not answering... I know a "ME TOO!" doesn't make you feel any better. )


    Monday, August 18, 2008 6:36 PM
  • Clarify: Out Of Office [OOF] is unavailable for all outlook 2007 users?


    1.       Is the “Free / Busy” information working normally?

    2.       Please provide the output of “Get-webservicesvirtualdirectory | Fl”, “Get-exchangecertificate | Fl” and “test e-mail autoconfiguration”

    3.       Enable outlook logging and reproduce issue, post OOF logging

    Steps: Tools->options->others->advanced options->enable logging->restart outlook

    Output location: Start->run->%temp%->”Olkas” folder

    4.       Restart “Default Website” on CAS server

    Collect info:

    1.       The symptom happens after .Net SP2 has been deployed?

    2.       When starting outlook 2007 do we get prompted for credential?


    • Proposed as answer by Noam Greenberg Sunday, January 17, 2010 9:10 AM
    Wednesday, August 20, 2008 1:58 AM

    Yes Man,


    you're not alone too.


    I've got the same error here in Microsoft Exchange Server 2007 Standard SP1 Update Rollup 2


    as can be seen from:








    James Luo, Xiu Zhang, Allen Song and Jason Li


    has done their best to contribute to the thread above and let's see if any of those guided comment works for you.

    so far I still haven't got Autodiscover configured properly.

    hope that helps.



    Wednesday, August 20, 2008 4:29 AM
  • Affected clients are all copies of Outlook 2007, and Entourage on the Mac.


    I've been through all these suggestions and they show nothing wrong. Outlook with logging on even shows Outlook receiving the information for displaying the Out-of-Office dialogue box, including the text of the last messages used for OOF.




    InternalNLBBypassUrl          : https://[servername.domainname]/ews/ex
    Name                          : EWS (Default Web Site)
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    BasicAuthentication           : False
    DigestAuthentication          : False
    WindowsAuthentication         : True
    MetabasePath                  : IIS://[servername.domainname]/W3SVC/1/
    Path                          : C:\Program Files\Microsoft\Exchange Server\Clie
    Server                        : [SERVERNAME]
    InternalUrl                   :
    ExternalUrl                   :
    AdminDisplayName              :
    ExchangeVersion               : 0.1 (8.0.535.0)
    DistinguishedName             : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,
                                    CN=[SERVERNAME],CN=Servers,CN=Exchange Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative Grou
                                    ps,CN=[Organization name],CN=Microsoft Exchange,CN=Ser
    Identity                      : [SERVERNAME]\EWS (Default Web Site)
    Guid                          : c354f81d-7d48-40a0-ab8e-24400997ccfb
    ObjectCategory                : [domainname]/Configuration/Schema/ms-Exch
    ObjectClass                   : {top, msExchVirtualDirectory, msExchWebServices
    WhenChanged                   : 18/08/2008 14:23:47
    WhenCreated                   : 14/06/2007 09:51:22
    OriginatingServer             : [dc.domainname]
    IsValid                       : True


    Test e-mail autoconfiguration:

    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns="
      <Response xmlns="
            <ServerDN>/o=[Organization]/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[SERVERNAME]</ServerDN>
            <MdbDN>/o=[Organization]/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[SERVERNAME]/cn=Microsoft Private MDB</MdbDN>
              <OWAUrl AuthenticationMethod="Basic, Fba">https://[servername.domainname]/owa</OWAUrl>


    Outlook log:

    2008/08/20 08:45:56.723: Request to URL: https://[domainname.servername]/EWS/Exchange.asmx

    2008/08/20 08:45:56.723: Request action: http://schemas.microsoft.com/exchange/services/2006/messages/GetUserOofSettings

    2008/08/20 08:45:56.723: Request XML: <?xml version="1.0"?>

    <q:Envelope xmlns:q="http://schemas.xmlsoap.org/soap/envelope/"><q:Body><ex12m:GetUserOofSettingsRequest xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages"><ex12t:Mailbox xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types"><ex12t:Address>[username@SMTPdomainname]</ex12t:Address><ex12t:RoutingType>SMTP</ex12t:RoutingType></ex12t:Mailbox></ex12m:GetUserOofSettingsRequest></q:Body></q:Envelope>

    2008/08/20 08:45:56.723: Sending request

    2008/08/20 08:45:56.770: Request sent

    2008/08/20 08:45:56.770: Response error code: 00000000

    2008/08/20 08:45:56.770: HTTP status code: 200

    2008/08/20 08:45:56.770: XML response:<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlnsTongue Tiedoap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><tTongue TiederverVersionInfo MajorVersion="8" MinorVersion="1" MajorBuildNumber="291" MinorBuildNumber="1" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" /></soap:Header><soap:Body><GetUserOofSettingsResponse xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"><OofSettings xmlns="http://schemas.microsoft.com/exchange/services/2006/types"><OofState>Disabled</OofState><ExternalAudience>None</ExternalAudience><Duration><StartTime>2008-08-20T07:00:00</StartTime><EndTime>2008-08-21T07:00:00</EndTime></Duration><InternalReply xml:lang="en-gb"><Message>&lt;html xmlnsSurprise="urnTongue Tiedchemas-microsoft-comSurprisefficeSurpriseffice" xmlns:w="urnTongue Tiedchemas-microsoft-comSurpriseffice:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"&gt;

    &lt;meta http-equiv=Content-Type content="text/html; charset=unicode"&gt;
    &lt;meta name=Generator content="Microsoft Word 12 (filtered medium)"&gt;
     /* Font Definitions */
     {font-family:"Cambria Math";
     panose-1:2 4 5 3 5 4 6 3 2 4;}
     panose-1:2 15 5 2 2 2 4 3 2 4;}
     /* Style Definitions */
     p.MsoNormal, li.MsoNormal, div.MsoNormal
    a:link, span.MsoHyperlink
    a:visited, span.MsoHyperlinkFollowed
     colorStick out tongueurple;
     {mso-style-typeStick out tongueersonal-compose;
    @page Section1
     {size:612.0pt 792.0pt;
     margin:72.0pt 72.0pt 72.0pt 72.0pt;}
     {pageTongue Tiedection1;}


    &lt;body lang=EN-GB link=blue vlink=purple&gt;

    &lt;div class=Section1&gt;

    &lt;p class=MsoNormal style='text-autospace:none'&gt;&lt;span style='font-size:12.0pt'&gt;[TEXT OF LAST OUT OF OFFICE MESSAGE]&lt;oStick out tongue&gt;&lt;/oStick out tongue&gt;&lt;/span&gt;&lt;/p&gt;



    </Message></InternalReply><ExternalReply xml:lang="en-gb"><Message>&lt;html xmlnsSurprise="urnTongue Tiedchemas-microsoft-comSurprisefficeSurpriseffice" xmlns:w="urnTongue Tiedchemas-microsoft-comSurpriseffice:word" xmlns:m="
    http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"&gt;

    &lt;meta http-equiv=Content-Type content="text/html; charset=unicode"&gt;
    &lt;meta name=Generator content="Microsoft Word 12 (filtered medium)"&gt;
     /* Font Definitions */
     {font-family:"Cambria Math";
     panose-1:2 4 5 3 5 4 6 3 2 4;}
     panose-1:2 15 5 2 2 2 4 3 2 4;}
     /* Style Definitions */
     p.MsoNormal, li.MsoNormal, div.MsoNormal
    a:link, span.MsoHyperlink
    a:visited, span.MsoHyperlinkFollowed
     colorStick out tongueurple;
     {mso-style-typeStick out tongueersonal-compose;
     font-family:"Times New Roman","serif";}
    @page Section1
     {size:612.0pt 792.0pt;
     margin:72.0pt 72.0pt 72.0pt 72.0pt;}
     {pageTongue Tiedection1;}


    &lt;body lang=EN-GB link=blue vlink=purple&gt;

    &lt;div class=Section1&gt;

    &lt;p class=MsoNormal style='text-autospace:none'&gt;&lt;span style='font-size:12.0pt;
    font-family:"Times New Roman","serif"'&gt;[TEXT OF LAST OUT of OFFICE MESSAGE USED]&lt;oStick out tongue&gt;&lt;/oStick out tongue&gt;&lt;/span&gt;&lt;/p&gt;

    &lt;p class=MsoNormal style='text-autospace:none'&gt;&lt;span style='font-size:12.0pt;
    font-family:"Times New Roman","serif"'&gt;&lt;oStick out tongue&gt;&amp;nbsp;&lt;/oStick out tongue&gt;&lt;/span&gt;&lt;/p&gt;

    &lt;p class=MsoNormal style='text-autospace:none'&gt;&lt;span style='font-size:12.0pt;
    font-family:"Times New Roman","serif"'&gt;[USERNAME]&lt;oStick out tongue&gt;&lt;/oStick out tongue&gt;&lt;/span&gt;&lt;/p&gt;






    Absolutely this was not happening just before .NET 2.0 SP2 went on, and it was happening immediately after: a colleague happened to want to use it then.


    There's no prompt for credentials starting Outlook. Nor have we found anything else broken.


    Wednesday, August 20, 2008 8:01 AM
  • Is the outlook log generated after you reproduce the issue on affected user’s mail profile? Because after compared your log with the fine log in my lab, they’re almost identical. If you cannot open OOF windows, the log would be totally different. Please confirm the source of the log

    Also, try to troubleshooting issue with a test account:

    a.       Create a test account, logon to a test pc with this test account and create mail profile

    b.      Enable logging feature, reproduce issue

    c.       Check OOF again

    Wednesday, August 20, 2008 9:26 AM
  • That log is from an affected user's profile. Outlook itself put up the server unavailable message.


    This isn't a standard misconfigured autodiscover problem. The .NET Framework service pack looks very guilty here.



    Wednesday, August 20, 2008 11:04 AM

  • Another "Me too."

    I will confirm that I installed SQL 2008 on the server about the time this started happening, which of course installs .NET 3.5 SP1. The server is Server 2008 with Exchange Server 2007 SP1 + Update Rollup 3.

    Additionally, I wonder if the original poster ALSO has this issue, and just has not noticed... This can be reproduced on Server 2003, Vista SP1, and Server 2008, with Outlook 2007 RTM/SP1/fully patched...

    1. Select New>Meeting request
    2. Click the Scheduling Assistant button in the Meeting Request
    3. Type an alias in the All Attendees list and press Enter

    Outlook immediately crashes with an Access Violation.

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    OUTLOOK.EXE
      Application Version:    12.0.4518.1014
      Application Timestamp:    4542840f
      Fault Module Name:    OUTLOOK.EXE
      Fault Module Version:    12.0.4518.1014
      Fault Module Timestamp:    4542840f
      Exception Code:    c0000005
      Exception Offset:    0079e26b
      OS Version:    6.0.6001.
      Locale ID:    1033

    I have the exact same crash when running Test-OutlookWebServices as the poster reports, I have the same "Server unavailable" message when trying to view Out Of Office settings.

    I think the same issue also causes the Scheduling Assistant to crash with the Access Violation.

    Friday, August 22, 2008 4:57 PM
  • The answer is, yes I do. Outlook crashes in exactly the same way as you describe.


    Slightly later Outlook build, but:


    Faulting application OUTLOOK.EXE, version 12.0.6316.5000, time stamp 0x4833a470, faulting module OUTLOOK.EXE, version 12.0.6316.5000, time stamp 0x4833a470, exception code 0xc0000005, fault offset 0x003c8bf0, process id 0x520, application start time 0x01c9051852bb5f8b.


    And it's an "access denied" error.


    I guess we now hope the Exchange team and the .NET Framework people are talking to each other, since I don't like the idea of trying to remove a .NET service pack from a live Exchange Server.

    Saturday, August 23, 2008 12:24 PM
  • Excellent! (or, tragic, depending on how you look at it).

    I did try that (uninstalled SQL 2008, .NET 3.5 SP1, and a bunch of other stuff) and it didn't have any effect on the crash.

    The crash symptoms/reproducibility vary depending on the patch level of Outlook 2007. Fully patched is the easiest to crash; you can simply right-click on any email sender's address who is part of the Exchange organization and it will happen, it looks like when it is trying to find the Free/Busy info which it populates the context menu with (i.e. "Free for next 8 hours").

    Yes, I hope someone is following up here? My environment is pretty small but I don't imagine many corporate customers would be happy with downgrading to Outlook 2003 so their users can schedule meetings...
    Monday, August 25, 2008 2:10 PM
  • Hot_Rats4, how did you go about uninstalling .NET Framework 3.5 SP1? As far as I can see it is the SP2 for .NET Framework 2.0, included in 3.5 SP1, which does the damage. On Windows Server 2008 2.0's SP2 is represented as a KB948609 update and not by the .NET Framework 3.5 SP1 entry in Programs and Features (though that has to come off first). My Exchange is still on Windows Server 2003.


    This blog from Aaron Stebner has detailed instructions on how to get back to .NET Framework 3.5 RTM and .NET Framework 2.0 SP1 http://blogs.msdn.com/astebner/archive/2008/08/01/8803442.aspx. I just didn't dare do it.


    Monday, August 25, 2008 4:08 PM

  • I uninstalled from Programs and Features. I didn't put 2 and 2 together regarding the other updates being .NET updates installed as part of the 3.5 Service Pack and they're not removed when running the 3.5 SP uninstall, so thank you for the link... I did not realize the other .NET versions had been updated as prerequisites to 3.5 SP1.

    Now for the good part. I had already removed .NET 3.5 SP1, I just uninstalled KB948610 and then KB948609, rebooted, and did a quick test.

    Outlook 2007 no longer crashes when scheduling meetings, or right-clicking on an email address as noted before. Out of Office Assistant appears to work as well (I get the UI at least, didn't try anything beyond that.)

    I can't tell you what will happen when you try this on Server 2003 but if you have a recent backup it might be worth a shot. Smile

    Monday, August 25, 2008 5:09 PM
  • This posting saved my tail.  2 weeks ago I started getting reports about Out of Office Assistant and Scheduling Assistant not working in Outlook 2K7.  I opened a case with Microsoft's Outlook group a couple of days later.  After about two or three days of jumping through uninstalling-and-reinstalling-apps hoops they escalated it to a senior engineer.  He gathered a bunch of data & said he would get back with me once he finished analyzing it.  A day or two later I came across this posting & requested that they get someone from the Exchange group involved.  I spoke briefly with an Exchange engineer who ruled out Exchange being the problem based on the Email Autoconfiguration Test completing successfully.  So after another day had passed I got tired of waiting for data to be analyzed and I removed and reinstalled .NET framework 3.5 SP1.  Scheduling Assistant started working again in Outlook 2007.  I had to remove & recreate the OWA and ActiveSync virtual directories via the Exchange Management Shell to get Out of Office Assistant and our smartphones working again. 
    Tuesday, August 26, 2008 6:51 PM



    that is sounds promising :-)


    but after you uninstall it, how did you re-create the OWA and Activesynch directories ?


    can you help us please ?



    Wednesday, August 27, 2008 5:14 AM
  • Note: This does NOT fix the Out of Office issue. They are aware of it and working on it. No ETA of a fix.....

    After opening a case with Microsoft, we finally got ahold of some higher engineers. It's basically something to do with the way the Exchange 2007 server is responding to the inquiries for the schedules.

    So, with a registry change on the workstations, we are using the Outlook 2003 calendar. Obviously, we are using a mixed enviroment with Exchange 2003 servers as well. Not sure if this will work with exclusively Exchange 2007 server.



    0 (or missing) = default behavior of using the Availability Service
    1 = Use public folder free/busy information

    Add or change this to a '1'. 

    Tuesday, October 14, 2008 2:57 PM
  • Take heart, Microsoft just sent us a patch that resolved all of our issues. Out of Office is now working, as well as the scheduled meetings. This is without the registry edit from above.

    The patch has not been released to the public yet......
    Tuesday, October 14, 2008 8:19 PM



    May i know how and where to get the patch please ?


    I'm having the issue of


    'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.'



    Friday, October 17, 2008 5:01 AM

    Oh man, glad I found this thread.  I've been tearing my hair out over this issue ever since I installed that !@#$@! rollup.  I've purchase a new certificate, messed with permissions, rebuilt virtual directories etc.


    What's the # of that patch so I can ask for it without having to go through all the uninstalls/reinstalls again?




    Friday, October 17, 2008 4:39 PM

  • To All,

    I've come across to the partial solution to make the "Plan a Meeting" feature to be working.

    here it is:
    "under this registry folder a value called: Read URL : this value is empty put this URL and restart your PC."

    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Calendar\Internet Free/Busy]
    Value Type: String
    Value Name: Read URL
    Value Name: Write URL (Not Confirmed yet Indifferent)
    Value: https://servername.domain.com/ews/services.wsdl

    Value Type: DWORD
    Value Name: UseLegacyFB
    Value: 1
    hope that helps, credit goes to infinity and Waleed from this forum through Googling :-)

    but still it didn't resolve the whole big picture of Autodiscovery error.
    Monday, October 20, 2008 7:31 AM
  • So...Is the issue resolved?I have the same issue with you. 

    Thursday, October 23, 2008 9:08 AM
  • where can i get this patch from...and is there a final release yet?

    Thursday, October 23, 2008 9:11 PM
  • Here's the link to the MS Article.


    When MS sent us the patch, they said it was still in the testing phase.

    • Proposed as answer by helsby Tuesday, November 10, 2009 7:36 PM
    Monday, October 27, 2008 2:53 PM

  • Infinity1971,

    OK, here is the content of that URL you gave to me:


    Hotfix information

    A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
    Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


    You must have the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1 installed to apply this hotfix.

    Restart requirement

    You do not have to restart the computer after you apply this hotfix.

    Hotfix replacement information

    This hotfix does not replace a previously released hotfix.


    but then when you go to that link, all you can see is just:

    How can we assist you?

    Select the option that best fits your need

       View Product Solution Centers
    Start here when your Microsoft product is not working as you expected. Visit the technical product support centers to:
    • Download the latest product updates
    • Look up top product issues, error messages, and troubleshooting tips
    • Find product help from a discussion group or support professional
    • Technical product contact information (telephone numbers, e-mail, and more)
       View Computer Manufacturers contact information
    If your Microsoft product was installed on your computer when you purchased it, the computer manufacturer is your primary source of technical support.
       View Customer Service Solution Centers
    Find information about non-technical customer service issues such as:
    • Careers, community affairs, corporate
    • Product sales and licensing
    • Replacements, refunds, and rebates
    • Customer Service contact information (telephone numbers, e-mail, and more)

    how did you get that file then ?

    Thanks anyway for posting your experience in this matter.
    Tuesday, November 4, 2008 11:37 PM
  • Don't you just love Microsoft sometimes? I would recommend opening up a case with MS and then referencing the KB. I am hesitant on sending you the file as 1) I don't know how legal it is to send the file and 2) the files are fairly large. There are separate ones for the OS (32 or 64 bit).

    Hopefully they will release it to the public soon.....
    Wednesday, November 5, 2008 11:21 PM

  • Infinity,

    you're right, may i know how big is that ?

    it is better off that we wait for that file to be finalized by Microsoft as I'm quite hesitant to install it for my system too.

    by the way, do you know how to uninstall
    ".NET 2.0 SP2 Update for Microsoft Windows (KB948609)" from Windows Server 2003 ?
    Friday, November 7, 2008 6:12 AM
  • Actually, I stand corrected. The files are not very large at all, around 1-2MB each. But, for legal reasons, I would rather you get them from MS.....

    Friday, November 7, 2008 10:45 PM

  • To All,

    Here's the update of the OOF not working in Outlook 2007 http://kbalertz.com/958934/Outlook-crashes-after-install-package-contains-Framework-Framework-Exchange-Client-Access-server.aspx


    To resolve this problem, install the hotfix that is
    described in the following Microsoft Knowledge Base article on the Exchange
    Client Access server:
    952883 (http://kbalertz.com/Feedback.aspx?kbNumber=952883/)
    FIX: The return type or the out argument of an ASMX service method that
    includes a property that has an internal setter may not be serialized
    on a computer that has the .NET Framework installed

    but you won't get the hotfix file when you follow that link above as of now 11-10-2008 :-0 ?????
    Monday, November 10, 2008 10:23 PM
  • This KB has now been superseeded by KB431780. You'll have to ring MS support to get your hands on it.


    Worked for me on Windows 2008 Ent x64 with .Net 3.5 SP1 and Exchange 2007 SP1 Rollup 5


    Thursday, December 4, 2008 11:50 PM

  • is this the one that you've installed before ?


    Title KB431780
    Release Date 9/8/2008
    Size 2.74 MB
    Version Hotfix
    Category Build
    Description "Revert" fix for QFE #431780 (getter/setter, obsolete fix)

    /* Support Engineer */
    • Proposed as answer by Kurt B. Mayer Wednesday, December 24, 2008 2:45 AM
    Monday, December 15, 2008 6:51 AM
  • At last, a fix for the OOF and SA issue has been posted to MS download center!


    As mentioned in previous posts, changes made in .NET FX 3.5 SP1 affect the way Outlook communicates with Exchange.  MS has released a Family Update for .NET FX to address this and other application compatability issues.  The general steps to update are as follows:

        0) Assume .NET FX 3.5 SP1 is already installed.
        1) Apply KB958481 to patch .NET 2.0 SP2.
        2) Apply KB958483 to patch .NET 3.0 SP2.
        3) Apply KB958484 to patch .NET 3.5 SP1.

    Note the incremental order of patches!  On the download center, the Vista/2008 *.msu and *.exe files are listed alphabetically, so be sure to do it in the correct sequence.

    This method worked for 64-bit Windows 2008 SP1 with Exchange 2007 SP1 Update Rollup 5, and Outlook 2007 SP1 on 64-bit Windows Vista SP1.  Using the link above you can get x86 or x64 versions for Windows 2003/XP or Windows 2008/Vista.  I applied these patches on both the client and server systems.  Now OOF and SA work again!

    Happy patching!

    11001010 MCITP-EA
    Wednesday, December 24, 2008 3:37 AM
  •  Take heed folks, the first two require a restart of the server :-)
    Jim Restucci
    Thursday, December 25, 2008 4:31 PM
  • Hi Mancer.

    Do you also install Exchange Server Update Rollup 6 ?

    which one should i do it first ?

    /* Support Engineer */
    Wednesday, March 18, 2009 4:10 AM
  • For those that  have users logging into a child domain .. but accessing a mailbox connected to a resource domain.. there is one workaround...
    You can grant the child domain account full access to the mailbox...  I know.. not the best fix.. but.... all I coudl figure out.. its either that or have the users run outlook as the resource account...

    Here what you see in the outlook log for OOF when a user in a child domain tries to access OOF from their mailbox that is attached to a resource domain...

    S-1-5-21-3258397735-123456789-1234567890-1595, MailboxGuid = S-1-5-21-2133076291-123456789-0987654321-213915 ---&gt; User is not mailbox owner. User =

    If anyone finds a better fix.. please post here !!!!!!!!
    Monday, April 6, 2009 9:14 PM

  • Or I suppose call MS for this :


    But I cant understand why a regression tested fix is not available by now !!!

    Monday, April 6, 2009 9:20 PM

  • Or I suppose call MS for this :


    But I cant understand why a regression tested fix is not available by now !!!


    Hi Steve,

    the hotfix above is for Outlook 2007 Client only it doesn't solve the Server problem I think ?

    /* Windows Infrastructure Support Engineer */
    Monday, June 22, 2009 7:17 AM

  • this is the Autodiscover issue pls check the a record in DNS

    sachin Hodge
    Thursday, June 25, 2009 10:46 AM
  • the server side hotfix is available as i see in sp2 now...
    Wednesday, July 1, 2009 2:29 PM
  • How do you know and where can we get it ?

    so far I've been battling with bad experience too in installing updates and Rollup for Exc. 2k7
    /* Windows Infrastructure Support Engineer */
    Wednesday, July 1, 2009 3:43 PM
  • I opened a support case with MS and trying to fix my not running owa and oab distribution and oof wizard bumped into your article. I found the hotfix but when i requested it the links were dead. So i asked the person helping me where i can get the file. she searched and found that the links are dead because it is part of sp2 which is available at


    and looks like is the same for both srv08 and vista. Obviously it updates the same engine...
    I am really thinking vista and srv08 are not finished yet, maybe i should get back to xp and 2003!
    Friday, July 3, 2009 1:30 PM
  • Hi Alex, the link that you posted is

    Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2 - Five Language Standalone (KB948465) ?

    is that including the fix for Exchange Server 2007 SP1 ?

    thanks for posting by the way.

    /* Windows Infrastructure Support Engineer */
    Friday, July 3, 2009 2:40 PM
  • yes, that is the one, i did not realize you are looking for exchange fixes. The latest i know about exchange is the rollup 8. what is your issue? oof doesnt work while oab sync works and owa works?
    Friday, July 3, 2009 2:42 PM
  • We have the same problem with Entourage on our Mac boxes.  Reading through this entire thing does not provide any solution for us however.  Our Windows clients do NOT have this issue.  OOF works fine for them and so does scheduling meetings. 

    When trying to open the OOF assistant on a mac, we get this error:

    Out of Office is temporarily unavailable because Entourage cannot connect to the server.  Set your Out of Office status after the connection to your Exchange account is restored.

    Now this is while the client is connected to Exchange and sending/receiving email without issue.

    Wednesday, August 12, 2009 12:14 PM

    If you use the address that is configured for Outlook Anywhere, it should resolve this issue.
    Thursday, August 27, 2009 3:28 PM
  • Just an FYI... I was able to resolve my issue by going into IIS and adding the server's IP address to the default website. Let me know if you need some clarification as to why.
    • Proposed as answer by nickadelman Wednesday, May 12, 2010 7:13 PM
    Wednesday, May 12, 2010 7:12 PM
  • Hello where in iis didyou add the ip address


    Wednesday, August 4, 2010 1:35 PM
  • HI.. being reading this old post with great interest as we are now getting the same issue but with Office 2010 and windows 7.

    Is any body else having the same issues?

    Have being searching google for what seems like ages to find a artical about this but all seem to go to the older version of Outlook can any body help


    Friday, January 21, 2011 8:47 AM
  • Hi itopman.............Yes we have also been having the issue. we run xp and win 7 with a range of office 2010 and 2007.
    We are experiencing this only with some users and not others. After searching forums and Microsoft fixes ( that don't seem to work!)  I ran a test Auto config on a working OOF PC and on one that doesn't work, to find the difference. It seems that the problem we are facing  is that Auto discover fails to start on the one with the OOF problem.

    Still investigating as I only ran this test yesterday so slowly uncovering a fix for it. 

    But thought I'd let you know you not alone in 2011 :)

    Friday, May 20, 2011 4:29 AM
  • Add your exchange server IP configuration to your PC's host file.

    1. Go to %systemdrive%:\Windows\System32\drivers\etc\
    2. Open host file with notepad
    3. Add exchange server's IP address


    Local IP address ex01.domain.com


    Public IP Address

    XXX.XXX.X.XXX ex01.domain.com


    4.       Save the host file (Need administrator privileges)

    5.       Reopen Outlook


    • Proposed as answer by DammZ Monday, June 13, 2011 1:04 PM
    Friday, June 10, 2011 7:21 PM
  • I had this problem today with one of our win 7 / Outlook 2010 users. cleanfreebusy didn't help, and he doesn't have the previously mentioned security / dotnet patch installed.

    Adding the exchange server to his hosts file fixed the problem, but this is at best a short-term solution, as you never know when our networking guys will decide to move around IP allocations. That's why we have DNS for goodness sake.

    Any other more permanent solutions to suggest?

    Friday, December 9, 2011 3:43 PM