Service Virtualization

Expand all | Collapse all

Getting error while creating second VSE (VSE2)

Jump to Best Answer
  • 1.  Getting error while creating second VSE (VSE2)

    Posted 05-28-2018 12:16 PM

    Hi,

     

    I'm creating second VSE (VSE2) on the server machine. Followed the below steps, 

     

    However while trying to start the service for the new VSE2 created (step 6), I'm getting the error "Error2: The system cannot find the file specified".

     

    Step 5 was success, but still getting an error.

     

    How To Run Multiple VSE Services on a Single Server - DevTest Solutions - 10.3 - CA Technologies Documentation 

     

    Follow these steps:

    1. Copy VirtualServiceEnvironmentService.exe to VirtualServiceEnvironmentService2.exe.
      This file is in the LISA_HOME\bin directory (for example, C:\Programs Files\CA\DevTest).
    2. Create a new vmoptions file named VirtualServiceEnvironmentService2.vmoptions and put the following properties in the file.
      -Dlisa.vseName=name of the new VSE, to distinguish it from others on the same computer.
      -Dlisa.net.8.port=port for the new VSE; must use a different port than 2013.
      -DLISA_LOG=vse2.log (to distinguish between the VSE log files).
    3. Add the VirtualServiceEnvironmentService2.vmoptions file to the LISA_HOME\bin directory.
    4. Repeat for each additional VSE service.
    5. To define the service, use the following command.

      sc create "DevTest VSE2" binpath= "D:\CA\DevTest\$LISA_HOME\bin\VirtualServiceEnvironmentService2.exe"

    6. Stop and start the DevTest components.

     

    Thanks,

    John



  • 2.  Re: Getting error while creating second VSE (VSE2)

     
    Posted 05-29-2018 03:37 PM

    Hello John,

     

    Could you provide the exact command you used in step 5?

     

    Thanks

    Heloisa



  • 3.  Re: Getting error while creating second VSE (VSE2)
    Best Answer

    Posted 05-29-2018 04:18 PM

    Hi Heloisa,

    I restarted the server and it worked this time. Thank you for the response.

     

    Thanks,

    John