Users Guide

Troubleshooting
VMware vCenter Server uses the SRA to display a detailed error message each time a recovery step fails.
The SRA also creates a log file called sra.log that shows each SRM event and each CLI command that occurs on the ME4
Series storage systems. Examining the error messages and this log file will often provide enough information to rectify errors.
For additional assistance, contact VMware for support.
Table 1. SRA error messages and suggested actions
Message
number
Message Suggested action
1002 VMware Site Recovery Manager version 6.5 was not found
on this system.
Install VMware SRM 6.5 or later and then rerun the
SRA installation procedure.
1003 XML output to “{file}” failed: {error} Ensure that the specified file location exists, has
adequate free space, and is writable.
1004 Install option is not supported on this system See the SRA installation instructions.
1005 A native version of Perl must be used when invoking this
option.
Ensure that you are using the Perl.exe version
installed with the VMware SRM software.
1006 Timed out waiting for volume {volume} to appear on the
storage system {arrayname} at {file}:{line}.
Verify that the specified volume has been created
on the storage system and retry the operation.
1007 Storage system '{systemName}' is not licensed for use
with this SRA.
Contact your storage system vendor to verify that
this system is supported and to request replication
and SRA license keys.
1008 No WWN found for volume “{primary}”. Verify that the specified volume is configured for
replication.
1009 discoverDevices: Could not determine WWN for temporary
snapshot “{serialNumber}” ({name}).
Check to see whether the specified snapshot was
left over from a previous test and can be deleted.
1010 Cannot find recovery point for temporary snapshot
“{serialNumber}” ({name}).
Check to see whether the specified snapshot was
left over from a previous test and can be deleted.
1011 discoverDevices: could not find WWN for promoted volume
“{secondaryName}” ({secondary}).
Check the status of the specified volume and the
health of the storage system and then retry the
operation.
1013 No valid sync point exists for {volume}. In MESM, use the Snapshots table to verify that the
specified volume has been completely replicated
from the protected site. For more information, see
the Administrator’s Guide.
1014 Could not export a snapshot for volume {vol}. A snapshot previously created by the SRA already
exists for the specified volume. Only one exported
snapshot is allowed per replication destination
volume. Delete the existing snapshot and retry this
operation.
1018 unknown or missing PeerId parameter '{PeerId}' in
{command} request.
Ensure that each storage system reports the name
of its replication peer(s) correctly, and that the
storage system names have not changed since SRM
was configured. If the storage system name has
been changed, delete and recreate remote system
entries on each storage system as necessary. If the
problem continues after restarting SRM, recreate
the storage system pair configuration in SRM.
3
10 Troubleshooting