Answered by:
Win32 Error Code 1722 RPC Service is unavailable

Question
-
We have BMC Portal and that portal actually discovers client machines to check their health status via WMI.
Now, When I am searching one of my Windows Server 2003 Server in that portal then I get error :
Unable to connect to WMI Host \\domain.com\computername\root\Default Win32 error code: 1722, computername is not found.
Please suggest and provide help.
MCSE Certified
Answers
-
We have BMC Portal and that portal actually discovers client machines to check their health status via WMI.
Now, When I am searching one of my Windows Server 2003 Server in that portal then I get error :
Unable to connect to WMI Host \\domain.com\computername\root\Default Win32 error code: 1722, computername is not found.
Please suggest and provide help.
MCSE Certified
Please refer similar discussion from BMC community
Getting "Failed to connect to WMI host:" while all parameters are collected ok.
https://bmc-sdn-vm.hosted.jivesoftware.com/communities/message/131618#131618
Also, its better to post this question in BMC community for better help and support
BMC.com > BMC Communities > Product Forums > BMC ProactiveNet > Performance Management
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
- .... .- -. -.- ... --..-- ... .- -. - --- ... ....- Proposed as answer by Mohammed imtiyaz Ali Tuesday, August 28, 2012 5:46 AM
- Marked as answer by Lawrence,Moderator Wednesday, September 5, 2012 2:44 AM
-
Hi,
Error with code 1722 indicates RPC error. You may refer to following steps to troubleshoot RPC errors:
- 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.
- 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.(http://www.microsoft.com/)
- 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/197814
How IT Works-Troubleshooting RPC Errors
http://technet.microsoft.com/en-us/magazine/2007.07.howitworks.aspxLawrence
TechNet Community Support
- Marked as answer by Lawrence,Moderator Wednesday, September 5, 2012 2:44 AM
All replies
-
We have BMC Portal and that portal actually discovers client machines to check their health status via WMI.
Now, When I am searching one of my Windows Server 2003 Server in that portal then I get error :
Unable to connect to WMI Host \\domain.com\computername\root\Default Win32 error code: 1722, computername is not found.
Please suggest and provide help.
MCSE Certified
Please refer similar discussion from BMC community
Getting "Failed to connect to WMI host:" while all parameters are collected ok.
https://bmc-sdn-vm.hosted.jivesoftware.com/communities/message/131618#131618
Also, its better to post this question in BMC community for better help and support
BMC.com > BMC Communities > Product Forums > BMC ProactiveNet > Performance Management
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
- .... .- -. -.- ... --..-- ... .- -. - --- ... ....- Proposed as answer by Mohammed imtiyaz Ali Tuesday, August 28, 2012 5:46 AM
- Marked as answer by Lawrence,Moderator Wednesday, September 5, 2012 2:44 AM
-
Hi,
Error with code 1722 indicates RPC error. You may refer to following steps to troubleshoot RPC errors:
- 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.
- 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.(http://www.microsoft.com/)
- 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/197814
How IT Works-Troubleshooting RPC Errors
http://technet.microsoft.com/en-us/magazine/2007.07.howitworks.aspxLawrence
TechNet Community Support
- Marked as answer by Lawrence,Moderator Wednesday, September 5, 2012 2:44 AM