Search

.NET Frameworks 3.5 SP1 and 2.0 SP2 incompatible with Exchange Server 2007 SP1 by Neil Flanagan

Closed
as Fixed Help for as Fixed

6
1
Sign in
to vote
Type: Bug
ID: 363175
Opened: 8/23/2008 11:47:43 AM
Access Restriction: Public
2
Workaround(s)
7
User(s) can reproduce this bug
There is a full discussion of this, without resolution, at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3760137&SiteID=17
After .NET Framework 3.5 service pack 1 is installed on Exchange Server 2007, Out of Office Assistant stops working for Outlook 2007 and Entourage, Test-OutlookWebServices crashes and Scheduling Assistant crashes on Outlook 2007 clients
Details (expand)
Product Language
English

Version

.NET Framework 3.5 Service Pack 1
Operating System
Windows Server 2003
Operating System Language
English (US)
Steps to Reproduce
.NET Framework 3.5 SP1 successfully installed on two Exchange Server 2007 SP1 (with Rollup 3) on Windows Server 2003 R2 SP2 x64 and one Exchange on Windows Server 2008, all previously fully functional. All Outlook 2007 and Entourage 2008 clients affected.
Actual Results
Outlook 2007 Out of Office Assistant reports "Your Out of Office settings cannot be displayed, because the server is currently unavailable".
Test-OutlookWebServices crashes after contacting autodiscover with ""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". Event log: ""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."
Typing an alias into the "All Attendees" list in the Scheduling Assistant causes an access violation in Outlook 2007.
Expected Results
Everything worked until .NET Framework 3.5 SP1 was installed.
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Dhanashri on 6/18/2009 at 12:34 PM
I faced the same issue which remained consistent even after I uninstalled .NET 3.5 SP1.
So when I installed all the three files in the required sequence, the GetUserAvailabilityResponseType started working as expected.
Please see the Knowledge Base Article KB959209 for more information.

Please download and install all 3 updates available in the section titled Files in This Download. These updates should be installed in the following sequence: [ http://www.microsoft.com/downloads/details.aspx?FamilyID=98E83614-C30A-4B75-9E05-0A9C3FBDD20D&displaylang=en&displaylang=en ]

1.    Install the update for the .NET Framework 2.0 Service Pack 2 - Windows6.0-KB958481-x64.msu
2.    Install the update for the .NET Framework 3.0 Service Pack 2 - Windows6.0-KB958483-x64.msu
3.    Install the update for the .NET Framework 3.5 Service Pack 1 - NDP35SP1-KB958484-x64.exe

Hope it helps!
-Dhanashri
Posted by Microsoft on 2/9/2009 at 6:30 PM
Hello-

Thank you for reporting this issue. This is a known product bug that shipped .NET 3.5 SP1.

However, we have provided multiple different ways for you to obtain this fix:
-KB article is located here: http://support.microsoft.com/kb/952883

- The fix has been shipped in the .NET 3.5 app-compat update. If you have Windows Update enabled, this fix will be automatically downloaded. If you can download straight from the following location: http://support.microsoft.com/kb/959209

- This will be fixed in Vista SP2 and onwards

I appologize for any inconvenience this has caused you. Please let me know if you have any additional concerns.

Thanks,

Erica Mohler
Microsoft Program Manager
Posted by jstawski2 on 10/28/2008 at 9:56 PM
I've had the same issue. After installing .NET 3.5 SP 1 I was not able to query Free/Busy time through Exchange Web Service. The FreeBusyResponseArray of the response was null. I wasn't able to query it through outlook 2007 either. I did a full uninstall of .NET 3.5 SP 1 by uninstalling 3.5 SP 1, 3.0 SP 2, and 2.0 SP 2 and then reinstalling 3.5 (without SP 1) and everything went back to normal.

Here's a thread about the problem:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=4059692&SiteID=17&mode=1
Posted by Microsoft on 8/25/2008 at 1:55 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
Sign in to post a workaround.
Posted by jstawski2 on 10/28/2008 at 9:57 PM
As of this writing fully uninstall .NET Framework 3.5 SP 1. Here's a link on how to do so: http://blogs.msdn.com/astebner/archive/2008/08/01/8803442.aspx
Posted by David Chadwick on 11/23/2008 at 2:53 AM
Hotfix for this issue can be found here:

http://support.microsoft.com/default.aspx/kb/958934