The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
IP Customization fails during a failover or test failover of a recovery plan in vCenter Site Recovery Manager (2021083)
- IP Customization fails for some or all 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.
- In the
vmware-dr.loglog file on the SRM server, you see entries similar to:
[00632 error 'Recovery' ctxID=27dcf3a7] [recovery-plan-3198.ipCust-protected-vm-3133-IPCustomization] Guest command on VM: [vim.VirtualMachine:vm-232] failed with exit code: 1
[02956 trivia 'Recovery' ctxID=27dcf3a7]<msg>Cannot complete customization, possibly due to a scripting runtime error or invalid script parameters (Error code: 1). IP settings may have been partially applied.</msg>
- The virtual machine is powered off and the network interface is set to disconnected.
- The recovery plan or test recovery plan completes with errors.
WindowsThis issue occurs in Windows virtual machines if the default system variable for the
%TEMP%or temporary folder within the guest operating system on the SRM server is changed from the default value and the new folder does not exist.
Note: The default folder specified in
%TEMP%in Microsoft Windows is
When you change the default value of
%TEMP%, the guest operating system does not check if the folder exists. For example, if you change the default value of
C:\temp, you do not see an error if
C:\tempdoes not exist.
During Windows guest customization, SRM needs to write to the folder specified in
%TEMP%. If this folder does not exist, guest customization fails.
LinuxThis issue occurs in Linux virtual machines when the
/tmpdirectory is mounted with the
noexecoption for security reasons.
During Linux guest customization, SRM needs to execute a file stored in
/tmp. If this file cannot be executed, guest customization fails.
WindowsTo resolve the issue in a Windows virtual machine:
Ensure that the new directory for
%TEMP%exists and can be written to.
%TEMP%variable is case sensitive. If it is set to
C:\Windows\TEMP, but the real path is
C:\Windows\Temp, guest customization will fail.
LinuxTo resolve the issue in a Linux virtual machine:
Allow files in the
/tmpdirectory to be executed by removing the
noexecoption. This option can be removed by editing the /etc/fstab (as root) using 'vi' editor.
To work around this issue without changing the security options on the
- In the Linux virtual machine, open the VMware Tools configuration file (
/etc/init.d/vmware-tools) using a text editor.
- Add this line:
In this example, a new
vmtmpwas created. SRM will use this temp directory when applying guest customization.
Note: To specify an alternative temporary directory in RHEL7-based guests, add the following entry to the [Service] section of the systemd unit file for the service (usually in /usr/lib/systemd/system):
- Restart the VMware Tools service using this command:
# /etc/init.d/vmware-tools restart
This forces a reload of the VMware Tools configuration file.
/etc/init.d/vmware-toolsfile will be reset to default when VMware Tools is upgraded.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.