Monday, March 14, 2011

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

In the mixed mode between Exchange 2003/Exchange 2010 or Exchange 2007, after move an user to the new server or when create a new one from the ADUC, the below error could show up when the user try to access by OWA

A problem occurred while trying to use your mailbox. Please contact technical support for your organization.

An unexpected error occurred and your request couldn't be handled.

In Show datails:


Url: https://<user's<user's owa link>:443/owa/lang.owa

User host address: <user’s ip address>


Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException

Exception message: There was a problem accessing Active Directory.

Call stack


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) 


waContext owaContext, UserContextCookie userContextCookie) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) 


System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Inner Exception

Exception type: 


Exception 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 stack

Microsoft.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) 


This problem can occur when the msExchVersion attribute is not configured correctly on the user object in Active Directory.
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.
In order to verify this problem, you can check the msExchVersion attribute by using the Exchange Management Shell. 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 that user objects are associated with. 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 should run the following command in the Exchange Management Shell prompt:
 Set-Mailbox <User_Name> -ApplyMandatoryProperties

  • To fix the problem on an Exchange Server 2007 mailbox, an Exchange administrator should run the Set-Mailbox command in the Exchange Management Shell 2007.
  • To fix the problem on an Exchange Server 2010 mailbox, an Exchange administrator should run the command in the Exchange Management Shell 2010.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.