Article ID: 2328735 - Last Review: September 10, 2010 - Revision: 7.0

"Your Out of Office settings cannot be displayed" when ASP.NET Role Manager is enabled on Exchange Server 2007 or Exchange Server 2010

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

Microsoft Office Outlook 2007 users with mailboxes homed an Exchange Server 2007 or Exchange Server 2010 Mailbox server running on Windows Server 2008 are unable to use the Out of Office Assistant. The following error message occurs in Outlook:

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

Users running Outlook 2003 or earlier versions, or Outlook Web Access (OWA), are able to configure and use the Out of Office Assistant features. Outlook 2007 users do not experience any other issues.

Also, Outlook Anywhere may fail to connect.

Back to the top

CAUSE

Role Management for ASP.NET has been enabled on the Mailbox server. Exchange Server 2007 and Exchange Server 2010 do not support enabling roles for ASP.NET.

Back to the top

RESOLUTION

Using Windows Explorer, navigate to the inetpub\wwwroot folder. In the web.config file, open the file with Notepad and look for the a section that contains the following information:

<?xml version="1.0" encoding="UTF-8"?><configuration>  <system.web>  <roleManager enabled="true" />  </system.web></configuration>

NOTE: It is possible that roleManager may have been enabled elsewhere in the system, instead of or in addition to the above. It may be necessary to check the web.config files for the EWS virtual directory, aspnet, or search the machine.config file for the section above to see if roleManager has been enabled..

If this information is present, back up the existing file by creating a copy with a different name. Then use the steps below:

After backing up the file, while viewing the file with Notepad, change the line containing <roleManager enabled="true" /> to:

<roleManager enabled="false" />
Exit and save the changes to the file.
Click Start, click Run and type services.msc, then click OK.
Right click and click Restart for the IIS Admin service.

Back to the top

MORE INFORMATION

IIS logs (W3SVC) may display errors similar to the following:

2010-08-25 00:15:192.168.0.10 POST /EWS/exchange.asmx ;RC:868e5975-3fe5-48d1-bbbd-3017f1d7a6e;Init>>Conn:0,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/$null/0%,RPC:$null/$null/0%,FC:$null/0,
Hash:36994246,Sub:null/0;SoapAction=GetUserOofSettingsResponse;ADRequests=1;ADLatency=0;
TimeInGetUserOOFSettings=8;End(10.7965ms)>>Conn:1,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/
$null/0%,RPC:$null/$null/0%,FC:$null/0,Hash:36994246,Sub:$null/0; 443 Domain\User 192.168.0.100 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6535;+Pro) 500 0 0 61 


2010-08-25 00:15:192.168.0.10 POST /EWS/exchange.asmx ;RC:5a80d750-16ae-46be-b643-36ba50bb2984;Init>>Conn:0,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/$null/0%,RPC:$null/$null/0%,FC:$null/0,Hash:36994246,Sub:null/0;SoapAction=GetUserOofSettingsResponse;ADRequests=1;ADLatency=0;TimeInGetUserOOFSettings=7;End(8.8335ms)>>Conn:1,AD:$null/$null/0%,CAS:$null/$null/0%,AB:$null/$null/0%,RPC:$null/$null/0%,FC:$null/0,Hash:36994246,Sub:$null/0; 443 Domain\User 192.168.0.100 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6535;+Pro) 500 0 0 292

With diagnostics logging for MSExchange Web Services and MSExchange Common set to Expert, the application log displays the following events:

Event ID: 4999
Source:MSExchange Common
Level: Error

Description:
Watson report about to be sent to dw20.exe for process id: 3472, with parameters: E12IIS, c-RTL-AMD64, 08.01.0240.006, WS, unknown, M.E.S.E.<>c__DisplayClass7.<GetUserOofSettings>b__4, System.InvalidCastException, 8842, 34720. ErrorReportingEnabled: 34721

And:

Event ID: 3
Source:MSExchange Web Services
Level: Error

Description:
An internal server error occurred. The unhandled exception was: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.InvalidCastException: Unable to cast object of type 'System.Web.Security.RolePrincipal' to type 'System.Security.Principal.WindowsPrincipal'.
at Microsoft.Exchange.Services.ExchangeService.<>c__DisplayClass7.<GetUserOofSettings>b__4()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
at Microsoft.Exchange.Diagnostics.ExWatson.SendReportOnUnhandledException(MethodDelegate methodDelegate, IsExceptionInteresting exceptionInteresting, Boolean terminating)
at Microsoft.Exchange.Services.Core.ServiceDiagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate)
at Microsoft.Exchange.Services.ExchangeService.GetUserOofSettings(GetUserOofSettingsRequest GetUserOofSettingsRequest)
--- End of inner exception stack trace ---

If you use IIS Manager to administer IIS on the Windows Server 2008 computer running Exchange Server 2007 or Exchange Server 2010, examine the .NET Roles properties for the default website and the aspnet_client path. You will see the following error:

An error occured while establishing a connection to the server. When connecting to the SQL server 2005, this failure, may be caused by the fact that under the default settings SQL server does not allow remote connections. (Provider: SQL Network Interfaces, error: 26 - Error Locating the server/instance specified

For more information on ASP.NET 3.0 Role Principals, see the following MSDN topic:

Role-Based Security (http://msdn.microsoft.com/en-us/library/52kd59t0(VS.85).aspx)

Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Back to the top