• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5610
  • Last Modified:

Outlook Anywhere: A rundown of the terror: RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime

I installed an exchange 2007 server SP2, on Windows 2008 64bit standard server.  Everything works great, except Outlook Anywhere from the outside (from the inside it works fine)

I did all the steps in all the blogs I could find, compared the configuration to a working config, and it still doenst work.  I got a UCC certificate, with 4 names;

exchange.domain.com (primary)
mail.domain.com
NetBios Name (POST)
Netbiosname.forest.local (Post.la5.local)

when I run:
Test-OutlookWebServices |fl >c:\test.txt

I get this:



Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address Administrator@domain.com.

Id      : 1007
Type    : Information
Message : Testing server POST.la5.local with the published name https://post.la
5.local/EWS/Exchange.asmx & .

Id      : 1019
Type    : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover
 URL on this object is https://POST.la5.local/Autodiscover/Autodiscov
er.xml.

Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://POST.la5.local/Auto
discover/Autodiscover.xml.

Id      : 1016
Type    : Success
Message : [EXCH]-Successfully contacted the AS service at https://post.la5.loca
l/EWS/Exchange.asmx. The elapsed time was 406 milliseconds.

Id      : 1015
Type    : Success
Message : [EXCH]-Successfully contacted the OAB service at https://post.la5.loc
al/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Success
Message : [EXCH]-Successfully contacted the UM service at https://post.la5.loca
l/UnifiedMessaging/Service.asmx. The elapsed time was 0 milliseconds.

Id      : 1016
Type    : Information
Message : [EXPR]-The AS is not configured for this user.

Id      : 1015
Type    : Success
Message : [EXPR]-Successfully contacted the OAB service at . The elapsed time w
as 0 milliseconds.

Id      : 1014
Type    : Information
Message : [EXPR]-The UM is not configured for this user.

Id      : 1017
Type    : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://exchange.domain.com/Rpc. The elapsed time was 0 milliseconds.

Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.

(changed the actual name of domain)

I removed all the certificates except for this new one:

[PS] C:\Users\Administrator.LA5\Desktop>get-exchangecertificate

Thumbprint                                Services   Subject
----------                                --------   -------
1423EF72BCCD9DC52422EF8D4222C1D1ADF28CFA  IP.WS      CN=exchange.domain...

[PS] C:\Users\Administrator.LA5\Desktop>

RPC Ping gives me this:

C:\Users\Boaz>rpcping -t ncacn_http -o RpcProxy=exchange.domain.com -P "
austin.hall,la5,password" -H 1 -F 3 -a connect -u 9 -v 3 -s exchange.domain.com -I
"austin.hall,la5,password" -e 6001
RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006
 RPCPing set Activity ID:  {097fa797-e7a4-47d8-8b33-e8eecd013ad2}
 Exception 1722 (0x000006BA)
 Number of records is: 2
 ProcessID is 6508
 System Time is: 12/30/2009 17:24:50:968
 Generating component is 14
 Status is 0x6BA, 1722
 Detection location is 1398
 Flags is 0
 NumberOfParameters is 2
 Long val: 0x4
 Long val: 0x6ba
 ProcessID is 6508
 System Time is: 12/30/2009 17:24:50:967
 Generating component is 13
 Status is 0x6BA, 1722
 Detection location is 1418
 Flags is 0

When I try to access the RPC like this:

https://exchange.domain.com/rpc/rpcproxy.dll?post.la5.local:6004 
https://exchange.domain.com/rpc/rpcproxy.dll?post.la5.local:6001
https://exchange.domain.com/rpc/rpcproxy.dll?post.la5.local:6002

I get a blank page, which seems to be working, this also works by substituting the external hostname of the server.

I changed the validports from 593 and 49152-65535 which it was, ( I think this is an upgrade that SP2 does, as the ports on the working configuration are the 6001-6002 and 6004)

and when going to https://www.testexchangeconnectivity.com/  and running the test, all passes except the last one:

Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server exchange.domain.com
       Failed to ping Endpoint
        Tell me more about this issue and how to resolve it
       
      Additional Details
       RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime


Anyway, I'm stumped at this point, can one of the experts here help?








0
sbsc
Asked:
sbsc
  • 12
  • 6
1 Solution
 
MesthaCommented:
You shouldn't be making registry changes manually. That isn't required with Exchange 2007.
Therefore I suggest that you start by resetting the system.

Disable Outlook Anywhere in Exchange, then remove the RPC Proxy. In IIS manager delete the two RPC virtual directories, and in an elevated command prompt run IISRESET.

Reinstall the RPC Proxy and then enable Outlook Anywhere again. Wait at least 30 minutes before testing.

It could be the TCP/IP v6 bug, which was supposed to be resolved in a rollup, but I have had to make the changes it needs. However you will need to reset the RPC Proxy to get the registry corrected.

http://technet.microsoft.com/en-us/library/cc671176(EXCHG.80).aspx

Simon.
0
 
sbscAuthor Commented:
ok, Im doing that now, this is lke the 4th time.  I know the uninstall removes the registry settings, but I didnt check if it removes the IIS rpc and rpcwithcert virtual directories.  if not Ill remove them.  I already
disabled IPv6 and modified the hosts file per that bug, but Im not on a rollup, I have SP2 installed, which I think per that validports entry, moved the server towards the 2010 model.

0
 
MesthaCommented:
I have had to make the change on servers with SP2 as well, even though the rollup is supposed to fix it.

Simon.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
sbscAuthor Commented:
nope, still not working, I'm getting this in the event log, is it related?

Microsoft Exchange could not find a certificate that contains the domain name POST.la5.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default POST with a FQDN parameter of POST.la5.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
0
 
MesthaCommented:
That has nothing to do with it.
All that means is that you don't have a UC/SAN certificate with the correct URLs in it. It is connected to transport, not RPC over HTTPS which is a client access function.

Outlook Anywhere either works or it doesn't. There is no half measure.

When you disabled IPv6, how exactly did you do it? If you disabled it as a protocol then it will cause a problem. (That is presuming this is a single server deployment). You have to leave it enabled but follow the procedure in that Technet article.

Simon.

0
 
sbscAuthor Commented:
Yes, this is a single server deployment.

What I did is uncheck it as a protocol under network adapter, and changed the hosts file, taking out the ::1
and adding a line like this:

192.168.128.50  POST POST.LA5.LOCAL

I just tried to reenable it all, and it wasnt working, I just rebooted and will try again.  

0
 
sbscAuthor Commented:
nope, still didnt work.  still this same error:

      Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server exchange.digitalfuture1.com
       Failed to ping Endpoint
        Tell me more about this issue and how to resolve it
       
      Additional Details
        RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime
0
 
sbscAuthor Commented:
Do you think it will help if I made the server an AD DC?
0
 
MesthaCommented:
If you make the machine a domain controller then you will break Exchange.
Running DCPROMO on a machine with Exchange installed is not supported.
If the machine is already a domain controller then it must be a global catalog, and running DCPROMO to remove the functionality is also not supported.

Your hosts file entry is wrong.

It should be

192.168.128.50  POST.LA5.LOCAL
192.168.128.50  POST

Separate lines.

Simon.
0
 
sbscAuthor Commented:
Simon, I installed a new exchange server on a new virtual machine, what is the best way go about it now? should I make the new server just the CAS server and leave the old one as the MBX server etc?  that way I dont have to move all the mailboxes etc.  

now when I open exchange management console, I see both exchange servers in there, and they seem to "share" configuration, i.e in the organization configuration etc.
0
 
sbscAuthor Commented:
well, I Installed a new server, configured it as the CAS, followed exact instructions as per here:

http://blog.sembee.co.uk/archive/2008/05/30/78.aspx

everything went smoothly, then I installed the RPC/Proxy in add features, and enabled outlook anywhere.  

everything still works great, EXCEPT for OA, which gives the same error:

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

Any ideas?!!

0
 
MesthaCommented:
I have only seen that error caused on Windows 2008 by the IPv6 bug, and making the changes in the Technet article have resolved it - despite Microsoft saying that it shouldn't be required.

You should be able to telnet to the port and get a response like this:

ncacn_http/1.0

From memory you should be able to telnet to both localhost on 6004 and the machine's FQDN.

Simon.
0
 
sbscAuthor Commented:
telnetting to all the ports 6001,6002 and 6004 on both machines, all produces the

ncacn_http/1.0

it works fine from within the network, but https://www.testexchangeconnectivity.com/  still fails with the famous RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime

isnt there any way of debugging this?
0
 
sbscAuthor Commented:
Simon, this is beyond annoying.... I saw this one post, saying that he's getting the error on the test site, but it works for him nonetheless.... so I remoted into a PC at my house, and tried setting up OA, and lo and behold.... it works....

so it may have been ok all along, but the site is messed up!!!!
0
 
sbscAuthor Commented:
by the way, I figured it out by the fact i wasnt seeing any activity in the event logs... which seemed wrong.
0
 
MesthaCommented:
Are you sure that it is working remotely?
Verify by holding down CTRL and right clicking on the Outlook icon. Choose Connection Status. It will show you how Outlook is connecting. If it says TCP/IP then it isn't Outlook Anywhere. If it is HTTPS, then it is.

Did you configure the client remotely by hand or did you allow autodiscover to do its thing? It may well be that you have put different information in.

Simon.
0
 
sbscAuthor Commented:
I'm pretty sure it's OA, I'll send a screen shot later.  Should I uninstall the CAS role from the old server?  It's basically serving as a MBX role now, also, which server needs more resources?  MBX or CAS?  Thanks!
0
 
sbscAuthor Commented:
well here it is,,,,, I guess it is working, just the microsoft site is not doing its job or something.  very annoying, but people should know to test it on their own if they get this error....
Untitled.png
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 12
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now