Getting Error deploying VSM file to VSE. Registry Monitor shows MIA VSE.

Products

• Service Virtualization

Issue/Introduction

Environment

All Supported DevTest releases.

Cause

Hostname was not mapped to IP address.

From Registry Monitor the Virtual Environs tab was showing MIA VSE.

 

Resolution

The VSE was up and running, but the Workstation could not see it.

Added -Dlisa.vseName=ssl://SVRTHOST:2013/VSE in Workstation.vmoptions file, restarted Workstation, but still could not see the VSE.

Tried with -Dlisa.vseName=ssl://10.10.10.10:2013/VSE in Workstation.vmoptions file, restarted Workstation, but still could not see the VSE.

Did a ping from the Workstation to the hostname, SVRTHOST, of where the VSE is running and could not find it.
Did a ping from the Workstation to the IP address, 10.10.10.10, of where the VSE is running and could find it.

On the VSE machine, added this line to the C:\Windows\System32\drivers\etc\hosts file:
10.10.10.10   SVRTHOST  SVRTHOST.XXX.XXX.com

Restarted the VSE, restarted the Workstation, but still could not see the VSE.

On the Workstation machine, added this line to the C:\Windows\System32\drivers\etc\hosts file:
10.10.10.10   SVRTHOST  SVRTHOST.XXX.XXX.com

Restarted the Workstation, and now could see the VSE and was able to deploy with no errors.

Needed to map the hostnames to IP address.