
Frequently Asked Questions
Question: Exchange Server Profile Analyzer reports CompletedWithException. Where can I find the exceptions that occurred during the data collection process?
Answer: Exchange Server Profile Analyzer reports exception information in a log file. The default log file is located at the user's application data path. For example, C:\Documents and Settings\<username>\Application Data\Microsoft\Epa\epalogYYYYMMDD_HHMMSS.log.
Question: Error: Unable to find an available uniform resource identifier (URI) for user ServerName\MDBName\Mailbox x.
Answer: The error is usually reported for two reasons:
1. No HTTP virtual server is running.
2. For each HTTP virtual server or directory on the Exchange server, the Simple Mail Transfer Protocol (SMTP) domain of the virtual server or directory does not match the user's SMTP domains.
Question: Error: User ServerName\MDBName\Mailbox x cannot access any of the following links: http://ServerName/Exchange/.
Answer: The error will come up in the following four cases.
1. The account that runs Exchange Server Profile Analyzer does not have full mailbox access on the user's mailbox. This can be verified through Exchange System Manager (ESM). If the account does have full mailbox permissions, try to use Internet Explorer to access the user's mailbox with Outlook Web Access. If you cannot access the mailbox with Outlook Web Access, Exchange Server Profile Analyzer will also be unable access it.
2. The authentication methods configured on the virtual directory do not include Integrated Windows Authentication which is the only method that is supported by Exchange Server Profile Analyzer.
3. There is TCP/IP traffic restrictions set on the Exchange server so that HTTP or HTTPS traffic is blocked from the computer on which you are running Exchange Server Profile Analyzer. To work around this issue, run Exchange Server Profile Analyzer on a computer that can connect with the back-end Exchange server (such as an Exchange front-end server).
4. When Outlook Web Access forms-based authentication is enabled on the HTTP virtual server, Exchange Server Profile Analyzer will fail. This is because the DAV requests that are submitted by Exchange Server Profile Analyzer will receive a "440 Login Timeout" error. This situation resembles that described in the Microsoft Knowledge Base article 817379, "Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003" at http://go.microsoft.com/fwlink/?linkid=3052&kbid=817379.
Question: I am still seeing "Error: User ServerName\MDBName\Mailbox x cannot access any of the following links: http://ServerName/Exchange/..." even though my user account has sufficient permissions, Integrated Windows Authentication is turned on, and forms-based authentication is not enabled.
Answer: In this case, you want to know the exact error message that is returned for each DAV request that Exchange Server Profile Analyzer submits. To obtain this kind of information, set the log level to Verbose before you run the tool. After you run Exchange Server Profile Analyzer, examine the log file. If you see "Error: The remote server returned an error: (502) Bad Gateway," disable the automatic configuration and proxy setting from Internet Explorer and try to run the tool again.
To disable automatic configuration and proxy settings from Internet Explorer
-
Open Internet Explorer, click Tools, and then click Internet Options.
-
Click the Connections tab, and then click LAN Settings.
-
On the Local Area Network (LAN) Settings dialog box, clear all the check boxes, and then click OK.