Cannot complete customization, possibly due to a scripting runtime error or invalid script parameters (Error code: 1). IP settings may have been partially applied.

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

During a failover or test failover of a recovery plan in vCenter Site Recovery Manager (SRM), you experience these symptoms:

• IP Customization fails for some or all windows virtual machines.
• In the History tab under Recovery Plans, you see the error:
  Error - Cannot complete customization, possibly due to a scripting runtime error or invalid script parameters (Error code: 1). IP settings may have been partially applied.

 

• The following error has been extracted from the recovery plan report:

• In the vmware-dr.log log file of the SRM server, you see entries similar to:

10-02-2025 19:23:18 Begin customization process
--> 10-02-2025 19:23:18 MAC Address: ##.##.##.##.##.##
--> 10-02-2025 19:23:18 Protocol: ipv4
--> 10-02-2025 19:23:18 Command: Set static IP settings
--> 10-02-2025 19:23:18 IP Address: ##.##.##.##
--> 10-02-2025 19:23:18 Subnet Mask: ##.##.##.##
--> 10-02-2025 19:23:18 GatewayMetricList: ##.##.##.##
--> 10-02-2025 19:23:18 DNS Servers Search Order: ##.##.##.##,##.##.##.##
--> 10-02-2025 19:23:18 NetBIOS Mode: 0
--> 10-02-2025 19:23:18 Customizing Network connection 'Ethernet0' (##.##.##.##.##.##) - Interface Index: 6 GUID: {########-####-####-####-##########}
--> 10-02-2025 19:23:18 Deleting all WINS servers configured on NIC with GUID: {########-####-####-####-##########F}
--> 10-02-2025 19:23:18 Running: %SystemRoot%\system32\netsh.EXE interface ipv4 delete server_name "Ethernet0" all
--> 10-02-2025 19:23:19 Setting a static ipv4 address on NIC with GUID: {########-####-####-####-##########}
--> 10-02-2025 19:23:19 Running: %SystemRoot%\system32\netsh.EXE interface ipv4 set address "Ethernet0" static ##.##.##.## ##.##.##.##.
--> 10-02-2025 19:23:20 ERROR: Attempt (1/31) has failed.
--> 10-02-2025 19:23:20 ERROR: Error code '1' returned by command:
--> 10-02-2025 19:23:20 %SystemRoot%\system32\netsh.EXE interface ipv4 set address "Ethernet0" static ##.##.##.## ##.##.##.##.
--> The RPC server is unavailable.

The above highlighted error "The RPC server is unavailable" occurs when SRM attempts to customize IP settings to the network interface card inside the guest OS of the virtual machine.

Environment

• VMware Site Recovery Manager 8.x
• VMware Live Site Recovery 9.x

Cause

The netsh tool in Windows is attempting to configure static IP address for the network interface but is failing. The error message "The RPC server is unavailable" could be caused by some services running inside the guest OS that is blocking or interfering with the connection.

Resolution

1. Following the Microsoft community article, start the DHCP client service within the guest OS after which the IP customization process is expected to succeed.
2. If the issue continues to occur even after starting the service, Please engage Microsoft Vendor for further investigation, as the dependency and behavior are within the guest operating system.