Вот что я нашел самое толковое по этой ошибке. Текст правда на англ. если непонятно, спрашивайте.
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.
Make sure that DCOM is configured properly on the MTS server and the client machine. Follow these steps:
Run Dcomcnfg.exe.
Select the Default Property tab.
Select the Enable Distributed COM on this computer check box.
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.
From the Default Impersonation drop-down list box, select Impersonate. MTS requires Identify or Impersonate for this setting.
For testing, change the package authentication to match the DCOMCNFG settings on the MTS Server by using the following steps:
Run Transaction Server Explorer.
Right-click the Package that is being used for testing.
Select Properties from the drop-down menu.
Select the Security tab.
Clear the Enable authorization checking check box.
Click OK.
Try using the component used for testing again. If the RPC error still occurs proceed with next step.
Use the information in the following Microsoft Knowledge Base Exchange article to test the RPC communication:
167260
(
http://support.microsoft.com/kb/167260/EN-US/ )
XCLN: How to Use RPCPing to Test RPC Communication
For more information please refer to following MS articles:
HOWTO: Troubleshoot RPC Errors
http://support.microsoft.com/kb/197814How IT Works-Troubleshooting RPC Errors
http://technet.microsoft.com/en-us/maga ... works.aspx
Вход
FAQ
Поиск
