Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote procedure call failed 1

Status
Not open for further replies.

grabrail

Technical User
Aug 15, 2001
269
GB
I have a strange problem

Windows 2000 Exchange server, running ok, pno problems.

When I use computer management from another machine, i.e. the DC. I can connect to Exchange server but when I try and expand event viewer I get the error:

Unable to connect to x.x.x.x the error was:
The remote procedure call failed and did not execute.

There is an error in the event log, event 594 with the following information:

A Kerberos Error Message was received:
on logon session InitializeSecurityContext
Client Time:
Server Time:
Error Code: 8:56:5.0000 4/24/2006 (null) 0x7
Extended Error: KDC_ERR_S_PRINCIPAL_UNKNOWN
Client Realm:
Client Name:
Server Realm: LDR.COM
Server Name: krbtgt/LDR.COM
Target Name: HOST/x.x.x.x@LDR.COM
Error Text:
File:
Line:
Error Data is in record data.


I have found information on what this means .i.e. server not found in kerberos database, but I can tfind any information on how to fix it.

Can anybody help.

Cheers
J
 
Delete the Kerberos ticket on the Exchange server and it will be recreated.

There is a resource kit utility for deleting them called Kerbtray.

I hope you find this post helpful.

Regards,

Mark
 
Mark

Thanks for the reply. I have deleted the tickets from the Exchange server now, at what point do they get recreated?

 
OK now the tickiet is recreated, I Still get the error:

Unable to connect to x.x.x.x the error was:
The remote procedure call failed and did not execute.

This happens whether I use ip address or name to connect to.

However I can connect from this machine back to the other no problem and view the event logs.

Any more ideas
 
OK, then it sounds like you have a security issue.

First off verify there are no firewalls blocking you. next check the permissions in the local policy for who can access the computer via the network.

You may need to reaply the security templates using the MMC snap-in.

I hope you find this post helpful.

Regards,

Mark
 
Hi

I have now resolved the issue, I ran a Netdiag on the server and it failed to get the local system information.

Whilst investigating this issue I found out that the rmeote registry service needs to be started, I checked this and it was indeed started.

However I gave the service a restart and hey presto, all was fine.

Thanks for all your help

J
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top