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

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

book

Article ID: 251696

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Environment

All Supported DevTest releases.

Cause

Hostname was not mapped to IP address.

 

 

Resolution

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

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

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

Did a ping from the Workstation to the hostname, VSEHostName, of where the VSE is running and could not find it.
Did a ping from the Workstation to the IP address, IPAddress, 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:
IPAddress VSEHostName  VSEHostName.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:
IPAddress   VSEHostName  VSEHostNameXXX.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.