MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Exchange Server 2010 troubleshooting notes

Thought I’d share my exchange server troubleshooting notes going forward. Hope it helps

Issue:

Migration Issues with Mailboxes from Exchange 2003 to Exchange 2010.User is unable to Move mailboxes in Exchange 2003 to Exchange 2010

Symptoms

User receives an error message while trying to move the mailbox from exchange 2003 to 2010.The error type is Mapi Exception Network Error.

Cause:

The reason behind this error is that the user has an rpc filter enabled on the ISA 2004

Resolution:

To resolve this, the User must disable the RPC filter on the ISA

Issue:

Unable to open Exchange Management Console (EMC).

User is unable to open the exchange management console and receives an error message while trying to open the EMC.

Error Message

The Following error occurred when getting user inFormation For ‘ExchOrg\Administrator’:

Processing data for a remote command Failed with the Following error message: The Windows Remote Shell cannot process the request; the selector value F064CC5A-7A3C-4AB8-B6D7-ADF56 specified in the request was not Found. For more Information, see the about_Remote_Troubleshooting Help topic.

User may also see an Error Event in the application Event Log, listed as:

Log Name: Application

Source: Application Error

Event ID: 1000

Level: Error

Computer: Name

Description:

Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e03238, faulting module kernel32.dll, version 6.0.6002.18005, time stamp 0x49e041d1, exception code 0xe053534f, fault offset 0x00000000000176fd, process id 0x%9, application start time 0x%10.

Cause :

The reason behind the inability of the EMC to open up may be because the user may be running a Trace instance using Extra (a.etl) with certain tags. The issue shall persist so long as the Extra trace is running

Resolution:

This can be resolved by disabling the trace. To do that, We first need to locate the EnableTraces.Config file from the Root drive and Delete it. This shall set the EMC to open up fine.

Issue:

Unable to connect to Exchange Control Panel on Exchange Server 2010

The user may be unable to access the Exchange control panel on the Exchange Server 2010

Symptoms:

Case 1:

User receives an error message:

“The user name or password that you entered is not valid. Try entering it again.”

Cause:

Such an error occurs when the authentication on the Exchange Control Panel is not properly configured.

Resolution:

Go to the Exchange control panel Virtual directory and disable forms based authentication.

Set basic, windows, and anonymous authentication.

Case 2:

The user is not able to login to the exchange control panel using the Admin account.

Symptoms:

User gets an error while navigating to Mailboxes from Mange Your Organization tab

The error is: ‘The Server Method GetList Failed’

Resolution:

To resolve this, we need to recreate the exchange control panel virtual directory. We use the following:

Remove-ECPVirtualDirectory -Identity “Exchange\ECP (Default Web Site)”

New-ECPVirtualDirectory

Case 3:

The user is unable to login to the exchange control panel with an account which is not an admin account.

Symptoms:

The user receives the following error:

“You don’t have permission to open this page. If you’re a new user or were recently assigned credentials, please wait 15 minutes and try again. If the problem persists, contact your administrator”

Resolution:

This error occurs if the default role assignment policy is not enabled. Check if the default role assignment policy is enabled by

Get-ManagementRoleAssignment -roleassignee “username” | FL

To set default role assignment policy, on the exchange command shell, run:

Set-mailbox “username” -roleAssignmentPolicy “Default Role Assignment Policy”

And finally execute

Get-Mailbox | Set-mailbox -roleAssignmentPolicy “Default Role Assignment Policy”

Issue:

Users with exchange 2010, unable to see the free/busy status of exchange 2003 users within the same organization

Symptoms:

The exchange 2010 CAS servers list a “400 Bad Request” for the availability service with event id 4003 in the application log.

The log can be the following:

Log Name: Application

Source: MSExchange Availability

Date: 5/5/2011 01:06:01 PM

Event ID: 4003

Task Category: Availability Service

Level: Error

Keywords: Classic

User: N/A

Computer: Casserver.server.com

Cause:

The failure in the availability service was due to an issue in naming and addressing of the accounts. If the names and (or) SMTP addresses begin with a # marks, the availability service fails. If in a group of look ups, there are accounts beginning with and without # mark, the availability service fails for all accounts.

The hash mark is not an escape character and hence will result in an error. The only permissible symbols to begin an SMTP address are “.” and “_”.

Resolution:

This issue can be removed obviously by removing the # mark (or whatever symbol used) from the SMTP address and in some cases even from the display name.

Issue:

iPhone connections to exchange requires specification of domain name.

Configure Exchange ActiveSync without a domain name

Symptoms:

Users are unable to log on to the exchange 2010 server by simply entering the username. They are required to enter Domain Name\Username to log on

Resolution:

To resolve this we need to change the default domain in the IIS Manager.

Open IIS Manager and Navigate to Microsoft-Server-ActiveSync Home->IIS->Authentication

Find authentication type and edit the Basic Authentication by right clicking on it and selecting Edit option.

Replace the “Default Domain” option with “\”.

Issue:

Issue with mailbox quota in Exchange 2010. The mailbox quota is not properly functioning.

Symptoms:

Even though mailbox quota has been set, the storagelimitstatus says mailbox disabled.

Resolution:

This issue may occur because the UseDatabaseQuotaDefaults is not set in the mailbox. When there are multiple quotas in the mailbox, we set the value of UseDatabaseQuotaDefaults to false.

This can be done by running the cmdlet

Set-Mailbox “username” -UseDatabaseQuotaDefaults $false

in the exchange command shell.

Issue:

Inability to send emails from Exchange 2010 to 2007

The user is unable to send emails from exchange 2010 to exchange 2007

Symptoms:

The user receives an NDR while trying to send email from exchange 2010 to exchange 2007.

Cause:

This may occur if the public folder hierarchy and content followed in exchange 2007 is not replicated to exchange 2010.

Resolution:

This can be resolved by replication of public folder in exchange 2010.

Ratish Nair

Microsoft MVP | Exchange Server

Team @MSExchangeGuru.com

One Response to “Exchange Server 2010 troubleshooting notes”

  1. Arun Chaudhary Says:

    Nice Article Bro… Keep itup 🙂

Leave a Reply

ad

Categories

Archives