Topic Last Modified: 2010-01-29
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
- From the Operations Console, double-click this alert, and then
click the General tab. Review the description of the alert
that includes the variables specific to your environment.
- From the Operations Console, double-click this alert, and then
click the Alert Context tab. Review the logged events that
meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
61 |
Event Source |
MSExchange OWA |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Outlook Web Access |
Rule Name |
Outlook Web App encountered an error when a user tried to change the Outlook Web App language setting. |
Explanation
This Error event indicates that the user referenced in the event description did not save his or her primary language setting for Microsoft Office Outlook Web App. The setting determines the language the program will use for all items and also the date and time settings displayed in Outlook Web App for the user. This event may occur if one or more of the following conditions are true:
- The mailbox was created by using the Active Directory
Users and Computers snap-in instead of the Exchange Management
Console or Exchange Management Shell.
- The msExchVersion value that is stored in
Active Directory for a user does not match to the
msExchVersion value that is stored on the server where the
user's mailbox is located.
Note: |
---|
Microsoft Exchange Server 2007 mailboxes should not be created through the Exchange Server 2003 extensions to the Active Directory Users and Computers console because this is not supported. If you create an Exchange 2007 mailbox with this tool, it will be identified as a legacy mailbox, even though it resides on an Exchange 2007 server. Use the Set-Mailbox cmdlet with the ApplyMandatoryProperties parameter to modify the mandatory properties of a mailbox in this state to correct the problem and remove the legacyMailbox tag from the mailbox. |
User Action
- To resolve this error, modify the mandatory properties of the
user mailbox specified in the event description. You do this by
running the Set-Mailbox cmdlet with the
ApplyMandatoryProperties switch. For example, in the
Exchange Command Shell, run Set-Mailbox -Identity
<UserAlias> -ApplyMandatoryProperties. For more
information about the Set-Mailbox cmdlet, see
Set-Mailbox.
- Resolve your issue by using self-support options, assisted
support options, and other resources. You can access these
resources from the Exchange Server Solutions Center. From this page,
click Self-Support Options in the navigation pane to use
self-help options. Self-help options include searching the
Microsoft Knowledge Base, posting a question at the Exchange Server
forums, and others. Alternatively, in the navigation pane, you can
click Assisted Support Options to contact a Microsoft
support professional. Because your organization may have a specific
procedure for directly contacting Microsoft Technical Support, be
sure to review your organization's guidelines first.
For More Information
If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.