RPC\WMI issues with Rapid Recovery software

Question

Hello guru's!

I've just installed Rapid recovery and added in our vSphere cluster without any issues. Our Hyper-V cluster is giving me some grief though. First it was WMI errors, but changing some permissions and restarting services seemed to fix that issue. However, now the Rapid Recovery core is giving me an RPC error.

**What am I doing?**Attempting to use the GUI to add the Hyper-V cluster VIA "Protect Multiple Machines". The wizard finds the cluster, displays the VM's available for backup on the cluster, I select the repository, and hit finish. It takes about 1 min, then comes back with the following error. I am using the VIP FQDN for the cluster when attempting to protect the cluster.
https://answers-afd.microsoft.com/static/images/image-not-found.jpg
**What have I tried?**On each of the nodes in the Hyper-V I've checked to make sure the RPC services are running, and I did do a restart on each of them. I also modified the permissions of a couple of the namespaces in WMI Control properties, adding the domain admin credentials of the account I'm using in Rapid recovery, e.g. *\root\virtualization\v2 and \root\CIMV2*

I also ran winmgmt /verifyrepository on each node in the cluster and they were all consistent.

For testing, the FW is completely disabled.

WMI services have been verified to be running, and I did restart them just to be sure.

I ran setspn -L to verify there were no duplicate SPN's, it reported correctly.

The exact error I'm getting is as follows;

The "Remote Procedure Call (RPC)" service is not running on the local machine. This error could be caused by one of the following:RPC service is downPRC service failed after initialization. WMI query: select * from Msvm_ComputerSystem where InstallDate !=Null -namespace root\virtiualization\v2

I ran this manually on one of the nodes, and it returns results;

PS C:\Windows\system32> Get-WmiObject -Namespace "root\virtualization\v2" -Query "SELECT * FROM Msvm_ComputerSystem WHERE InstallDate != NULL"

__GENUS                                  : 2

__CLASS                                  : Msvm_ComputerSystem

__SUPERCLASS                             : CIM_ComputerSystem

__DYNASTY                                : CIM_ManagedElement

__RELPATH                                : Msvm_ComputerSystem.CreationClassName="Msvm_ComputerSystem",Name="REDACTED"

__PROPERTY_COUNT                         : 46

__DERIVATION                             : {CIM_ComputerSystem, CIM_System, CIM_EnabledLogicalElement, CIM_LogicalElement...}

__SERVER                                 : REDACTED

__NAMESPACE                              : root\virtualization\v2

__PATH                                   : \REDACTED\root\virtualization\v2:Msvm_ComputerSystem.CreationClassName="Msvm_ComputerSystem",Name="BADEA15A-D1C8-4EB4-B7BF-65AB

                                           E84B7B64"

AvailableRequestedStates                 : 

Caption                                  : Virtual Machine

CommunicationStatus                      : 

CreationClassName                        : Msvm_ComputerSystem

Dedicated                                : 

Description                              : Microsoft Virtual Machine

DetailedStatus                           : 

ElementName                              : NUNYA

EnabledDefault                           : 2

EnabledState                             : 2

EnhancedSessionModeState                 : 3

FailedOverReplicationType                : 0

HealthState                              : 5

HwThreadsPerCoreRealized                 : 2

IdentifyingDescriptions                  : 

InstallDate                              : 20240821121601.817960-000

InstanceID                               : 

LastApplicationConsistentReplicationTime : 16010101000000.000000-000

LastReplicationTime                      : 16010101000000.000000-000

LastReplicationType                      : 0

LastSuccessfulBackupTime                 : 

Name                                     : REDACTED

NameFormat                               : 

NumberOfNumaNodes                        : 1

OnTimeInMilliseconds                     : 423520683

OperatingStatus                          : 

OperationalStatus                        : {2}

OtherDedicatedDescriptions               : 

OtherEnabledState                        : 

OtherIdentifyingInfo                     : 

PowerManagementCapabilities              : 

PrimaryOwnerContact                      : 

PrimaryOwnerName                         : 

PrimaryStatus                            : 

ProcessID                                : 11452

ReplicationHealth                        : 0

ReplicationMode                          : 0

ReplicationState                         : 0

RequestedState                           : 5

ResetCapability                          : 1

Roles                                    : 

Status                                   : OK

StatusDescriptions                       : {Operating normally}

TimeOfLastConfigurationChange            : 20240925203129.989849-000

TimeOfLastStateChange                    : 20240925203129.958597-000

TransitioningToState                     : 

PSComputerName                           : REDACTED

PS C:\Windows\system32> 

It seems to successfully run the query locally VIA powershell, but the Rapid recovery core can't seem to run it remotely for some reason.

Banging my head against the wall here, any ideas?

Answer 1

Hello,

You may run PortQry to check if port 135 (RPC) and any dynamic ports used by DCOM are open.

Portqry.exe -n <ServerIP> -e 135

Reference:

RPC error troubleshooting guidance - Windows Client | Microsoft Learn

Troubleshooting a Remote WMI Connection - Win32 apps | Microsoft Learn

Best regards,

Karlie Weng