KS-Soft. Network Management Solutions
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister    ProfileProfile    Log inLog in 

RMA - 301 -The remote procedure call failed

 
Post new topic   Reply to topic    KS-Soft Forum Index -> Configuration, Maintenance, Troubleshooting
View previous topic :: View next topic  
Author Message
btgmike



Joined: 18 Nov 2004
Posts: 1
Location: BTG
PostPosted: Thu Nov 18, 2004 1:49 pm    Post subject: RMA - 301 -The remote procedure call failed Reply with quote
The above error message shows when I run PerfCounter tests on PC's in remote networks.

The tests that are not working are set up on servers on networks with RMA's.
The RMA's are version 2.


On the same networks, there are PerfCounter tests set up on differnet PC's that work fine. The tests reporting this message are set up the same as the working tests.

The services 'Remote Registry' and 'RPC' are started on the remote PCs.

Any ideas?
Back to top
View user's profile Send private message
KS-Soft



Joined: 03 Apr 2002
Posts: 12795
Location: USA
PostPosted: Thu Nov 18, 2004 3:37 pm    Post subject: Reply with quote
What Microsoft says in "HOWTO: Troubleshoot RPC Errors" article
Quote:

Troubleshooting RPC
1. Make sure that the remote procedure call (RPC) services are started on the server computer. You can do this by opening Control Panel, double- clicking Services, and checking to make sure the Remote Procedure Call (RPC) Service and Remote Procedure Call (RPC) Locator services are running and set to start automatically.

2. If the operating system is Windows 95, Distributed Component Object Model (DCOM) must be installed. You can downloaded this file from the following Web site:
http://www.microsoft.com/
NOTE: DCOM is not included in the released version of Windows 95.

3. Make sure that DCOM is configured properly on the MTS server and the client machine. Follow these steps:

a. Run Dcomcnfg.exe.
b. Select the Default Property tab.
c. Select the Enable Distributed COM on this computer check box.
d. From the Default Authentication Level, select None for testing. Normally this should be set to a level that is equal to or higher than the packages authentication level.
e. From the Default Impersonation drop-down list box, select Impersonate. MTS requires Identify or Impersonate for this setting.

4. For testing, change the package authentication to match the DCOMCNFG settings on the MTS Server by using the following steps:

a. Run Transaction Server Explorer.
b. Right-click the Package that is being used for testing.
c. Select Properties from the drop-down menu.
d. Select the Security tab.
e. Clear the Enable authorization checking check box.
f. Click OK.

5. Try using the component used for testing again. If the RPC error still occurs proceed with step 6.
6. Use the information in the following Microsoft Knowledge Base Exchange article to test the RPC communication:
167260 XCLN: How to Use RPCPing to Test RPC Communication

http://support.microsoft.com/default.aspx?scid=kb;en-us;197814
Hope it will be useful in your case

Regards
Alex
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    KS-Soft Forum Index -> Configuration, Maintenance, Troubleshooting All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
KS-Soft Forum Index