Welcome to ISAserver.org

RPC over HTTP 500 internal error

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> RPC over HTTP 500 internal error

Page: [1]

Message

<< Older Topic Newer Topic >>

RPC over HTTP 500 internal error - 13.Jan.2008 8:13:32 AM

nambija

Posts: 10
Joined: 1.May2007
Status: offline

Can anybody help with the following before I toss the server in the pool, here is my set up.

1)Got BE FE and 2 DCs both of which both are GCs
2) configured external NIC with basic and Internal with FBA as per the Good Doctor's article - http://www.isaserver.org/tutorials/2004pubowamobile.html and OWA works like a treat.
3) SSL 123 cert installed on FE server and exported to ISA server, cert name is owa.domain.com
4) Can logon to OWA and works great no errors.
5) Done all of the RPC settings on the FE server, 593, 6001,6002, 6004.
6) Got split DNS, on the ISA server got a host file owa.domain.com to point the FE server.
7) the To tab in the ISA rule points NOT to the server but the Cert name owa.domain.com which then uses the host file to resolve to the FE server.

Question Time.
When I load up Outlook with RPC i get the usual logon box, if I type my password wrong, it comes back and asks me to do it again. Also in the ISA server, this errror comes up as 401 Unauthorized. So i know that it is speaking to the DCs. However when i type in correct passsword the ISA server comes back with 500 Internal Server Error

many thanks
N

Post #: 1

Featured Links*

RE: RPC over HTTP 500 internal error - 15.Jan.2008 11:40:10 AM

nambija

Posts: 10
Joined: 1.May2007
Status: offline

Ok, here is an update, since this site has helped me so many times - payback.
Some steps to check to see if things are working

1) make user RPC over HTTP is installed on your FE server
2) test this by using the two links do both as the first URL works but sometimes the second one does not and this is where you proplem can be.
https://owa.mydomain.com/rpc

logon three times and you get 401.2 and 401.3 depending on what sp exchange you are runing

https://owa.mydomain.com/rpc/rpcproxy.dll

again logon 3 times and you get a blank page

test to see if your backend exchange server is listening on ports 6001/2 and 4.
many ways to do this netstat -anb is this fast. Take note the store must be listening on 6001 and the others on 6002&4.

A good tool it portqueryUI.

TCP    0.0.0.0:6001           0.0.0.0:0              LISTENING       4652
[store.exe]
TCP    0.0.0.0:6002           0.0.0.0:0              LISTENING       3336
[mad.exe]
TCP    0.0.0.0:6004           0.0.0.0:0              LISTENING       3336
[mad.exe]

Make sure you have set your GCs to listen on the port 6004 regardless of front/backend or single server.

Make sure your proxy service is loaded on the proxy server, you will only see an event registered when you make the first RPC call such as https://owa.mydomain.com/rpc. If there is an error modify the registry on the proxy server and change HKLM/Software/microsoft/rpc/rpcproxy.dll valid ports.

Take greate care when you modify this as a small wrong ; : in the wrong place the proxy service will not load.

For HTTP over RPC make sure that it is working internal first. outlook /rpcdiag to see what protocol it is using. If https is avaiable it will work, if not then it will fall back to IP.

Any more tips please add - will update later on.

Later N

(in reply to nambija)

Post #: 2