The attempt to ping the MAPI Mail Store endpoint endpoint failed

_{Tuesday, August 12, 2014 10:10 AM | 1 vote}

Hi,

We have just moved from Exchange 2010 to 2013 (completely new organisation/ad, there were lots of problems with the old one). All roles are performed by a single server (budgets). Everything went perfectly however Outlook cannot connect, creating a new profile finds the settings via Autodiscover (via 3rd party cert) but then the following error occurs:

(There were images before, but apparently I am not allowed to post any images so apologies for the typing out)

The action could not be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

The check name doesn't work and the account cannot be created (and from what I have read Exchange 2013 doesn't support non-autoconfigure connections anymore).

Before I enabled Outlook anywhere any Outlook connections would just constantly ask for credentials, however I can't go back now it seems. Does Exchange 2013 only support RPC via HTTP connections for Outlook? That is something new if true.

Then I checked https://testconnectivity.microsoft.com/ and the following is displayed:

Attempting to ping the MAPI Mail Store enpoint with identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx@domain.com:6000

The attempt to ping the endpoint failed

The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

Cue some intensive Googling (sorry Binging?) and several suggestions were found to resolve the issue from various threads here and blog posts:

• Add IP  SERVER to the hosts and lmhosts.sam files
• Disable IPv6
• edit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy\ValidPorts to everything I could think of: 
• NETBOIS:593;NETBOIS:49152-65535;FQDN:49152-65535;localhost:49152-65535;Outlook anywhere FQDN:49152-65535;
• Telnet into port 6001, 6002 and 6004 from the server. This throws an interesting result:
• Port 6001: ncacn_http/1.0 (which seems fine)
• Port 6002: can't connect
• Port 6004: can't connect

This looks to be my issue, but I can't see why it's not connecting and I don't know how to check any further. The other thing is the Remote Connection Analyser is looking for port 6001 and it can't connect.

Any help is much appreciated, I think I have tried everything I can think of and have reached the end of my intelligence.

-macole1

_{Wednesday, August 13, 2014 4:56 AM | 1 vote}

Hi

You can set the authentication to basic for outlook anywhere and the prompts should stop.

I would advise enabling IPv6 again.

Do a reboot and lets start again?

_{Wednesday, August 13, 2014 8:35 AM}

Hi,

Many thanks for the reply.

I have always assumed that exchange works best without IPv6, has this now changed? (on Googling it looks like it has, so I have renabled it).

The authentication prompts were only straight after the migration, before I had added the Outlook Anywhere FQDN to the ECP.

Still the same error as before:

Attempting to ping the MAPI Mail Store endpoint with identity: xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx@xxxx.xxxx:6001.

-macole1

_{Wednesday, August 13, 2014 9:40 AM}

Hi macole1,

1. For the question, "Does Exchange 2013 only support RPC via HTTP connections for Outlook?".

Exchange 2013 use RPC over HTTP connect to Outlook internally and externally.

And Exchange 2013 SP1 can use MAPI over HTTP connect to Outlook 2013.

So, I suggest enable Outlook Anywhere if you have disabled it.

2. I suggest try to logon the user's mailbox via OWA. If OWA works well, please see following KB:

Outlook: Unable to perform a Check Name or connect to an Exchange mailbox

http://support.microsoft.com/kb/2264398/en-us

3. Also find a similar thread for your reference:

Exchange Outlook Anywhere does not work!

http://social.technet.microsoft.com/Forums/exchange/en-US/be2e134b-9334-47ca-90cc-2c5ac19a6c43/exchange-outlook-anywhere-does-not-work?forum=exchange2010

Thanks

Mavis

Mavis Huang
TechNet Community Support

_{Wednesday, August 13, 2014 9:49 AM}

Hi,

Many thanks for the reply.

OWA works fine, however the link you sent is a reg hack for the local machine (that doesn't work incidentally) and not a full solution. My understanding is that if the RCA doesn't work then it's a server side issue.

I have read that thread and every similar one (feels like it anyway) and the suggestions haven't worked. Hmm...

-macole111

_{Tuesday, August 19, 2014 3:26 AM}

Hi macole1,

Thanks for your update.

Since OWA works well, it means the issue relates on Outlook client side or Connection between Outlook and Exchange server.

Please enalbe IPv6 and Outlook Anywhere if you have disabled them.

Then I notice that the port 6002 and 6004 can't be connected.

The error "The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process" caused by following conditions:

1. Failures in DNS name resolution

2. Missing or invalid ValidPorts key in the registry of the Internet-facing CAS server

3. Exchange services not listening on the required endpoints

4. Firewalls blocking the required ports

Please check the Firewall and find out which services block the port 6002 and 6004.

Thanks

Mavis

Mavis Huang
TechNet Community Support

_{Tuesday, August 19, 2014 10:55 AM}

Hi Mavis,

Many thanks for the reply. You are thinking along similar lines to me. I have re-enabled IPv6, I never worked out how to turn off Outlook Anywhere.

1. DNS is working correctly, I can telnet into port 6001 using the FQDN and localhost

2. My VaildPorts key is as follows: I think it is okay.

COMPUTERNAME:593;COMPUTERNAME:49152-65535;FQDN:49152-65535;localhost:49152-65535;OUTLOOKANYWHEREADDRESS:49152-65535;

3. This is where I was thinking the error comes from, however I can't find any information on how to test this.

netstat -a shows:

Active Connections

**  Proto  Local Address          Foreign Address        State PID**

TCP    0.0.0.0:6001           BOSTON:0               LISTENING       13764
  TCP    0.0.0.0:6005           BOSTON:0               LISTENING       356
  TCP    0.0.0.0:6006           BOSTON:0               LISTENING       760

 TCP    [::]:6001              BOSTON:0               LISTENING       13764
  TCP    [::]:6005              BOSTON:0               LISTENING       356
  TCP    [::]:6006              BOSTON:0               LISTENING       760

So it's not even listening on 6002 or 6004.

These are what the PID are. Looks like only 6001 is related.

PID    Process

13764  Microsoft.Exchange.RpcClientAccess.Service.exe
356    wininit.exe
760    svchost.exe

4. I tried turning off Windows firewall (the only firewall) to test it and it made no difference therefore it was re-enabled. As all the roles are on the same server I assume that would make no difference.

Do you have any ideas why there would be no service at 6002 or 6004? This looks to be the root of the issue.

Many thanks for your help so far.

-macole1

_{Thursday, August 21, 2014 3:14 AM}

Hi,

Thanks for your update.

I found a related blog for your reference:

How does Outlook Anywhere work (and not work)?

http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx  

Thanks

Mavis

Mavis Huang
TechNet Community Support

_{Tuesday, June 9, 2015 12:03 AM}

Were you able to fix it? I have the same issue, and I have tried to fix it for days now.

Juan C. Dulanto

_{Thursday, January 7, 2016 11:02 PM}

Has this ever been solved? I have similar issue for 3 weeks now, been working with Microsoft Office365 Support team who are as lost as I am

_{Sunday, November 20, 2016 9:50 PM}

Well, this is an old thread but it was at the top of my search results, so this is a solution for further visitors like me. I had the same problem (although only with port 6002). In the end I figured out that a completely unrelated service was also trying to listen on port 6002, and usually it was the faster to start after a reboot so that's why the Address book service (that's the one listening on port 6002) was starting and immediately stopping. Reconfiguring that other rogue service to a different port solved all my issues.