VMware vCenter Site Recovery Manager IP Customization during Test Failover or Failover operations fails with the error: 1073741819 (Windows ACCESS VIOLATION)
search cancel

VMware vCenter Site Recovery Manager IP Customization during Test Failover or Failover operations fails with the error: 1073741819 (Windows ACCESS VIOLATION)

book

Article ID: 343309

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction


Symptoms:
  • During Test Failover or Failover operation, IP customization on Windows virtual machines fails.
  • You see the error:

    non-zero exit code 1073741819

  • McAfee VSE 8.8 is running on the guest operating systems of the virtual machines that are being recovered and having IP customized through Site Recovery Manager (SRM).
  • The vmware-dr.log file located at \ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\ on the SRM Server displays these entries:

--> "Starting IP customization on Windows ..."

--> Microsoft (R) Windows Script Host Version 5.8
--> Copyright (C) Microsoft Corporation. All rights reserved.
-->
--> MAC Address: xx:xx:xx:xx:xx:xx
--> Reset level:
--> Enum script:
--> IP Address:
--> Subnet prefix length:
--> Subnet Address:
--> Gateway:
--> Gateway Metric:
--> DNS IPv6 server:
--> DNS IPv4 server:
--> WINS server: DELETEALL
--> DNS domain:
--> Customizing Network connection 'Local Area Connection 2' (xx:xx:xx:xx:xx:xx) - Interface Index: -1 GUID: {30E4A7F4-7927-450C-8C13-4E7C3A6C0308}
-->
--> netsh interface ip delete wins name="Local Area Connection 2" all
-->
-->
--> Exit code: 0
--> Logging in C:/Windows/TEMP/vmware-imc/guestcust.log
--> Exit code: 0
--> Logging in C:/Windows/TEMP/vmware-imc/guestcust.log
--> Exit code: 0
--> Microsoft (R) Windows Script Host Version 5.8
--> Copyright (C) Microsoft Corporation. All rights reserved.
-->
--> MAC Address: xx:xx:xx:xx:xx:xx
--> Reset level:
--> Enum script:
--> IP Address:
--> Subnet prefix length:
--> Subnet Address:
--> Gateway:
--> Gateway Metric:
--> DNS IPv6 server:
--> DNS IPv4 server: xx.xx.xx.xx
--> WINS server:
--> DNS domain:
--> Customizing Network connection 'Local Area Connection 2' (xx:xx:xx:xx:xx:xx) - Interface Index: -1 GUID: {30E4A7F4-7927-450C-8C13-4E7C3A6C0308}
-->
--> netsh interface ipv4 add dns "Local Area Connection 2" xx.xx.xx.xx
--> The object is already in the list.
-->
-->
-->
--> Error code returned by command : 1
--> (Ignoring Error)
--> Exit code: 0
--> Microsoft (R) Windows Script Host Version 5.8
--> Copyright (C) Microsoft Corporation. All rights reserved.
-->
--> MAC Address: xx:xx:xx:xx:xx:xx
--> Reset level:
--> Enum script:
--> IP Address:
--> Subnet prefix length:
--> Subnet Address:
--> Gateway:
--> Gateway Metric:
--> DNS IPv6 server:
--> DNS IPv4 server: xx.xx.xx.xx
--> WINS server:
--> DNS domain:
--> Customizing Network connection 'Local Area Connection 2' (xx:xx:xx:xx:xx:xx) - Interface Index: -1 GUID: {30E4A7F4-7927-450C-8C13-4E7C3A6C0308}
-->
--> netsh interface ipv4 add dns "Local Area Connection 2" xx.xx.xx.xx
--> The object is already in the list.
-->
-->
-->
--> Error code returned by command : 1
--> (Ignoring Error)
--> Exit code: 0
-->
--> Pinging 127.0.0.1 with 32 bytes of data:
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
--> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
-->
--> Ping statistics for 127.0.0.1:
--> Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
--> Approximate round trip times in milli-seconds:
--> Minimum = 0ms, Maximum = 0ms, Average = 0ms
--> Exit code: 0
--> Microsoft (R) Windows Script Host Version 5.8
--> Copyright (C) Microsoft Corporation. All rights reserved.
-->
--> MAC Address: xx:xx:xx:xx:xx:xx
--> Reset level: SINGLENIC
--> Enum script: "C:\Windows\TEMP\vmware-SYSTEM\enumIPv6.bat"
--> IP Address:
--> Subnet prefix length:
--> Subnet Address:
--> Gateway:
--> Gateway Metric:
--> DNS IPv6 server:
--> DNS IPv4 server:
--> WINS server:
--> DNS domain:
--> Customizing Network connection 'Local Area Connection 2' (xx:xx:xx:xx:xx:xx) - Interface Index: 12 GUID: {30E4A7F4-7927-450C-8C13-4E7C3A6C0308}
-->
-->
--> --- Enumerating IPv6 addresses to be removed ---
--> "C:\Windows\TEMP\vmware-SYSTEM\enumIPv6.bat" address "Local Area Connection 2"
-->
-->
--> --- Enumerating IPv6 Gateways to be removed ---
--> "C:\Windows\TEMP\vmware-SYSTEM\enumIPv6.bat" gateway 12
-->
--> netsh interface ipv6 delete dns "Local Area Connection 2" all
-->
--> There are no Domain Name Servers (DNS) configured on this computer.
-->
-->
--> Exit code: -1073741819
--> ",
--> returnValue = -1073741819,
--> },
--> msg = "",
--> }
---



Environment

VMware vCenter Site Recovery Manager 5.1.x
VMware vCenter Site Recovery Manager 5.5.x
VMware vCenter Site Recovery Manager 5.0.x

Cause

This issue occurs when the non-zero exit code 1073741819 is returned by the cscript.exe interpreter that is referenced in the last stages in the automatic IP customization batch script that SRM creates and runs on the recovered Windows virtual machine. This error code is defined by Windows as Access Violation error.

The actual cause is attributed to McAfee Anti virus 8.8 running on the Windows virtual machines that intermittently creates a hook on the script engine (cscript.exe) and does not release it in time.

Resolution

This is not a VMware issue.

To work around this issue, use one of these workaround suggested by Symantec:

Workaround 1

Enable ScriptScan in the VirusScan Console:

  • Navigate to Start > Programs > McAfee > VirusScan Console.
  • Right-click On-Access Scanner and select Properties.
  • Under General Settings, click ScriptScan tab.
  • Select Enable ScriptScan.
  • Click Apply and OK.


Workaround 2

Un-register SCRIPTSN.dll:
  • Click Start > Run, type cmd, and click OK. The command prompt opens
  • Type the appropriate command and press Enter:
    • 32 bit computers:

      cd c:\Program Files\Common Files\McAfee\SystemCore

    • 64 bit computers:

      cd c:\Program Files (x86)\Common Files\McAfee\SystemCore
      cd c:\Program Files\Common Files\McAfee\SystemCore

  • To completely disable the SCRIPTSN.dll, type this command and press Enter:

    regsvr32.exe /u SCRIPTSN.dll

For permanent fix, upgrade McAfee VSE 8.8 on the one Windows virtual machines to 8.8 patch-1 version.

For more details on this issue, see these articles from Symantec and McAfee:
Note: The preceding links were correct as of July 30, 2014. If you find these links are broken, provide feedback and a VMware employee will update the link.