Error on NT server.

[Funnyhat]

Greetings,

I have a customer who gets this error sometimes...

"The RPC Server is unavaliable"

What is the issue and what can be done to fix this? I'm not sure the NT server it is on but the domain is fxportal.org

Sincerely,

Mark

[Brangwyn]

The most common cause for this error I have seen is the server is in the middle of a reboot. it sometimes will occur becuase the "server" service is not started/running.

You might need/want to submit a trouble ticket if the problem didn't just go away after a few minutes.

[edit]does look like the website is running ok now[/edit]

[Funnyhat]

No it happens way to often to be a reboot... unless the servers reboot every hour lol... I also had it happen on another server the domain is bayousingles.com same thing... went to the page and got the error... refreshed the page and it worked...

Mark

[Brangwyn]

Are you sure your not getting the error page from a cache then ? I've had that happen several times before, there was nothing wrong with the site at all but I simply had the "RPC Unavailable" page stuck in a cache somewhere (either my browser or an upstream proxy)

[Funnyhat]

I don't think it is a cache issue... because it does not happen on other pages as well... I have not seen it happen on HTML pages but ASP pages... What is RPC anyway?

[thecomputerpro]

I too saw this for the first time today but only for about a minute or so.

RPC = Remote Procedure Call. Typically used to determine server services running on a machine and how to comunicate with those services.

I am am unclear why we would see this in an IIS environment if indeed the sites files are on the same server.

[Brangwyn]

I am am unclear why we would see this in an IIS environment if indeed the sites files are on the same server.

As I said this can be regularly seen in IIS particularly when the server is in the middle of shutting down or resarting IIS.

I most definately have had this same problem though and tracked it down to a proxy caching the page incorrectly, blew the proxy cache away and things were back to normal.