none
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

    Monday, August 27, 2012 7:23 PM

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

    https://bmc-sdn-vm.hosted.jivesoftware.com/communities/community/bmcdn/service_assurance/performance_management?view=discussions&start=0



    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.

    - .... .- -. -.- ... --..-- ... .- -. - --- ... ....

    Monday, August 27, 2012 7:36 PM
    Moderator
  • 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/
        (http://www.microsoft.com/)
        NOTE: DCOM is not included in the released version of Windows 95.
      • Make sure that DCOM is configured properly on the MTS server and the client machine. Follow these steps:

        1. Run Dcomcnfg.exe.
        2. Select the Default Property tab.
        3. Select the Enable Distributed COM on this computer check box.
        4. 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.
        5. 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:

        1. Run Transaction Server Explorer.
        2. Right-click the Package that is being used for testing.
        3. Select Properties from the drop-down menu.
        4. Select the Security tab.
        5. Clear the Enable authorization checking check box.
        6. 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.aspx


    Lawrence

    TechNet Community Support

    Tuesday, August 28, 2012 7:42 AM
    Moderator

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

    https://bmc-sdn-vm.hosted.jivesoftware.com/communities/community/bmcdn/service_assurance/performance_management?view=discussions&start=0



    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.

    - .... .- -. -.- ... --..-- ... .- -. - --- ... ....

    Monday, August 27, 2012 7:36 PM
    Moderator
  • 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/
        (http://www.microsoft.com/)
        NOTE: DCOM is not included in the released version of Windows 95.
      • Make sure that DCOM is configured properly on the MTS server and the client machine. Follow these steps:

        1. Run Dcomcnfg.exe.
        2. Select the Default Property tab.
        3. Select the Enable Distributed COM on this computer check box.
        4. 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.
        5. 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:

        1. Run Transaction Server Explorer.
        2. Right-click the Package that is being used for testing.
        3. Select Properties from the drop-down menu.
        4. Select the Security tab.
        5. Clear the Enable authorization checking check box.
        6. 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.aspx


    Lawrence

    TechNet Community Support

    Tuesday, August 28, 2012 7:42 AM
    Moderator