Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Running the vCenter Site Recovery Manager dns_update script fails with the error: \VMware\VMware was unexpected at this time." (1036097)

Symptoms

  • Cannot run the vCenter Site Recovery Manager (SRM) dns_update script 
  • Running the DNS server update on a windows DNS server during SRM failover fails
  • You see the error:

    verifying input data

    \VMware\VMware was unexpected at this time.
    [2011-03-10 10:2:10 TRIVIA] Result: 65280

Resolution

This issue occurs if the path to the command is misinterpreted by the script when the path has parenthesis (as seen in 64 bit operating systems).

To workaround this issue, you must edit the script dns_update.cmd file.
 
To edit the script dns_update.cmd file:
  1. Open the script dns_update.cmd file using a text editor.
  2. Locate the following line :

    REM -------------------------------------------------------------------------
    REM Setup internal variables
    REM -------------------------------------------------------------------------
    IF DEFINED TOOLSPATH (
    SET PATH=%PATH%;%TOOLSPATH%
    )

  3. Remove the braces enclosing the SET PATH variable. For example:

    REM -------------------------------------------------------------------------
    REM Setup internal variables
    REM -------------------------------------------------------------------------
    IF DEFINED TOOLSPATH SET PATH=%PATH%;%TOOLSPATH%

  4. Run the command again.

For more information, see Adding a DNS Update Step to a Recovery Plan.

Tags

dns-update-script-fails

See Also

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.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: