Article ID: 941146 - Last Review: December 9, 2011 - Revision: 6.0

Error message when an Exchange Server 2007 user or an Exchange Server 2010 user tries to log on to OWA

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

  • Symptom 1

    When a Microsoft Exchange Server 2007 user tries to log on to Microsoft Office Outlook Web Access (OWA), the user receives the following error message:
    A problem occurred while trying to use your mailbox. Please contact technical support for your organization.

    If the user clicks the Show details button in this error message, the following call stack information is shown:
    RequestUrl: https://<user's OWA link>:443/owa/lang.owaUser host address: <user’s IP address>ExceptionException type: Microsoft.Exchange.Data.Storage.StoragePermanentExceptionException message: There was a problem accessing Active Directory.Call stackMicrosoft.Exchange.Data.Storage.ExchangePrincipal.Save() Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)Inner ExceptionException type: Microsoft.Exchange.Data.Directory.InvalidADObjectOperationExceptionException message: Property Languages cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0). Call stackMicrosoft.Exchange.Data.Directory.PropertyBag.set_Item(PropertyDefinition key, Object value) Microsoft.Exchange.Data.Directory.ADObject.set_Item(PropertyDefinition propertyDefinition, Object value) Microsoft.Exchange.Data.Directory.ADObject.StampCachedCaculatedProperties(Boolean retireCachedValue) Microsoft.Exchange.Data.Directory.ADObject.ValidateWrite(List`1 errors) Microsoft.Exchange.Data.Directory.Recipient.ADRecipient.ValidateWrite(List`1 errors) Microsoft.Exchange.Data.Directory.Recipient.ADUser.ValidateWrite(List`1 errors) Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties) Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()
  • Symptom 2

    When a Microsoft Exchange Server 2010 user tries to log on to Microsoft Outlook Web App (OWA), the user receives the following error message:
    An unexpected error occurred and your request couldn't be handled.
    If the user clicks the Show details button in this error message, the following call stack information is shown:
    RequestUrl: https://<user's OWA link>:443/owa/lang.owaUser host address: <user’s IP address>User: <user name>EX Address: /o=<name of the domain>/ou=Exchange Administrative Group (<OU>)/cn=Recipients/cn=<user name>SMTP Address: <SMTP address>OWA version: <version number>ExceptionException type: System.InvalidOperationExceptionException message: Property Languages can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (0.16.36493.455).Call stackMicrosoft.Exchange.Data.MultiValuedProperty`1.Clear() Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save() Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.OwaModule.OnPostAuthorizeRequest(Object sender, EventArgs e) System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Back to the top

CAUSE

This problem can occur when the msExchVersion attribute is configured incorrectly for the user object in Active Directory Domain Services (AD DS).

Note The msExchVersion attribute may not be configured correctly if you create the user's mailbox by using Active Directory Users and Computers Microsoft Management Console (MMC) snap-in instead of using the Exchange Management Console.
Back to the top

RESOLUTION

If you are not familiar with Microsoft Exchange management, please contact your local systems administrator to help fix the problem.

To verify this problem, you can check the msExchVersion attribute by using the Exchange Management Shell. To do this, run the following command in the Exchange Management Shell prompt:
Get-Mailbox <User_Name>| format-list ExchangeVersion

Note Exchange Server 2007 and Exchange Server 2010 both use the msExchVersion attribute to determine the version of Exchange Server with which user objects are associated. If the version value is less than 0.1, Exchange Server 2007 or Exchange Server 2010 considers the user object as Read-only.

To resolve this problem, an Exchange administrator must run the following command in the Exchange Management Shell prompt:
Set-Mailbox <User_Name> -ApplyMandatoryProperties
Notes
  • To fix the problem on an Exchange Server 2007 mailbox, an Exchange administrator must run the Set-Mailbox command in the Exchange Management Shell 2007.
  • To fix the problem on an Exchange Server 2010 mailbox, an Exchange administrator must run the command in the Exchange Management Shell 2010.
Back to the top

MORE INFORMATION

For information about an error that can occur after you create or migrate mailboxes on a server that is running Exchange Server 2007, see the following article in the Microsoft Knowledge Base:
949527  (http://support.microsoft.com/kb/949527/en-us/ ) Some users cannot access Exchange Server 2007 Outlook Web Access after you create new mailboxes or migrate existing mailboxes
For more information about the Set-Mailbox command in Exchange Server 2007, visit the following Microsoft website:
General information about the Set-Mailbox command in Exchange Server 2007 (http://technet.microsoft.com/en-us/library/bb123981(EXCHG.80).aspx)
For more information about the Set-Mailbox command in Exchange Server 2010, visit the following Microsoft website:
General information about the Set-Mailbox command in Exchange Server 2010 (http://technet.microsoft.com/en-us/library/bb123981.aspx)
For more information about the Exchange Management Shell, visit the following Microsoft website:
General information about the Exchange Management Shell (http://technet.microsoft.com/en-us/library/bb123778(EXCHG.80).aspx)
Back to the top
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
Back to the top
Keywords: 
kbtshoot kbprb kbsurveynew kbexpertiseinter kbfix KB941146
Back to the top