A problem occurred while trying to use your mailbox. Please contact technical support for your organization.
After migrating a user to Exchange 2007, Outlook Web Access or OWA stops working with the error shown.
“A problem occurred while trying to use your mailbox. Please contact technical support for your organization.”
Additionally, you get the following message:
Request
Url: https://<user’s<user’s owa link>:443/owa/lang.owa
User host address: <user’s ip address>
Exception
Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: There was a problem accessing Active Directory.
Call stack
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)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Exception
Exception type:
Microsoft.Exchange.Data.Directory.InvalidADObjectOperationException
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)
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()
This behavior is caused by an attribute – msExchVersion being 0 for the affected user.
Check it using the cmdlet:
Get-Mailbox ratish | format-list ExchangeVersionIf the output is 0.0,
Run this:
Set-Mailbox ratish –ApplyMandatoryProperties
Update from Robert: I had to go under the user in AD and on their Security Tab I went to Advanced and checked the box to ‘inherit’ the container settings. That fixed it. Robert
Ratish Nair
MVP Exchange
Team@ MSExchangeGuru
December 28th, 2011 at 10:02 am
This didn’t work for me. I had to go under the user in AD and on their Security Tab I went to Advanced and checked the box to ‘inherit’ the container settings. That fixed it.
Robert
January 2nd, 2012 at 1:38 pm
Thank you Robert. I have seen this behavior and added your solution in the article.
Thank you again.
Ratish Nair
July 18th, 2015 at 10:25 pm
I have been testing (and re-testing) Exchange 2010 installations, and it’s strange because I see this problem when logging in as Administrator immediately after the installations, but NOT all the time. Sometimes I get the error after the installation and sometimes I don’t get the error after an installation.
In my case, when I get the error, the Get-Mailbox for the Administrator user showed:
ExchangeVersion : 0.10 (14.0.100.0)
I tried what Robert suggested in AD Users and Computers and that has worked every time I’ve tried it so far.
Does anyone know WHY this problem occurs? What causes it?
July 18th, 2015 at 10:29 pm
I just found this:
https://support.microsoft.com/en-us/kb/949527
It seems like this was a bug in Exchange 2007 and apparently must still be a bug in Exchange 2010, though even with the explanation on that page, I still don’t understand why the problem occurs sometimes and not others.
July 19th, 2015 at 1:37 am
Hi Jim,
We shared one of the solution which worked and updated Roberts solution. This issue may occur with more reasons.
If checking inheritance is fixing the issue then our concern should be why inheritance is getting removed. The reason for this behavior is simple permission got removed.
Usually inheritance gets removed for domain admins so the thumb rule is Domain admins group member account should not have a mailbox.