Profile analyzer

Question

If anyone could point me in the right direction it would be great .... I downloaded the Exchange Profile Analyzer in order to get some stats on the Exchange server.  We are running Exchange 2007 SP1 (no rollups).  I've checked the permissions too many times - the account I'm using has full send as / receive as rights to all the mailboxes. The account also has Exchange View Only Admins.
The problem is that everytime I run the Profile Analyzer, I get an error
"cannot access any of the following links
https://mailbox server/exchange
http://mailbox server:80/exchange
It was my understanding that these virtual directories are only used for Exchange 2003 compatibility. We are running only Exchange 2007 servers. The MS documentation on this tool is poor at best and provides no help. No help from google either.
TIA.

Answer 1

Taken from http://msexchangeteam.com/archive/2005/12/27/416524.aspx.  Try the suggestions and note that at the end there's a contact address at Microsoft if no-one else replies here and it all gets too much! 
Oh, and by the way, don't forget that permissions changes can get cached for a few hours - hopefully you've taken this into account.  If not, try restarting the Information Store or rebooting, etc.
Good luck.
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 five cases. 
      1. The account that runs EPA does not have full mailbox access on the user's mailbox. This can be verified through Exchange System Manager. Please see the EPA documentation for details on how to configure and verify permissions.  If the account does have full mailbox access rights, then try using Internet Explorer to access the user's mailbox with OWA. If you are not able to access the mailbox with OWA, EPA will not be able to access it either. 
      2. The authentication methods configured on the virtual directory do not include Integrated Windows Authentication which is the only method EPA supports. 
      3. There are restrictions set up on the Exchange Server that restrict TCP/IP traffic in some way so that HTTP or HTTPS traffic from the machine you are running EPA on is blocked. You can work around this by running EPA on a machine that has the ability to connect with the back-end Exchange Server (such as an Exchange front-end server).
      4. When SSL is required on the server and the name on the SSL certificate does not match the name that EPA is using to access the server, EPA will fail due to SSL certificate validation errors.  We will have a fix for this in next Web Release. 
      5. When OWA Forms-Based Authentication is enabled on the HTTP virtual server, EPA will fail since the DAV requests submitted by EPA will get "440 Login Timeout" error. This is similar to http://support.microsoft.com/default.aspx?scid=kb;en-us;817379 . We plan to provide better feedback for this case in the next web release version.
If these troubleshooting suggestions don't solve your EPA problems, please contact epafb AT microsoft DOT com for further investigation