Deployment to Virtual Hosted Servers fail with Virtual Deployment Failed error - Virtual deployment error 95

Version 1



    This document provides a solution for patch deployment failures to virtual hosted server.




    You attempt to scan and deploy patches to hosted virtual servers.  The scan completes but the the deployment ends with Virtual Deployment Failed in the Shavlik Protect Operations Monitor.



    Identifying the issue in the logs


    This document is specific to the 'Virtual deployment error 95' which can be verified in the ST.Protect.Managed.UserName@DomainName.log: (logging level should be set to 'All' in Tools > Options > Logging)

    The logs are located in this folder:  C:\ProgramData\LANDESK\Shavlik Protect\Logs


    HostedVirtualDeployment.cs:256|Virtual deployment error 95

    PatchDeploy.cs:411|ServerName failed - VirtualDeploymentFailed Exception of type 'ST.Deployment.Protect.ProtectDeploymentException' was thrown.


    Additional verification can be found in the ST.ServiceHost.managed.log, the Error 503 is referring to the web call to the host server failing.


    VimClient.cs:189|System.Net.WebException: The remote server returned an error: (503) Server Unavailable.

       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

       at System.Net.HttpWebRequest.GetRequestStream()

       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

       at VimApi_60.VimService.RetrieveServiceContent(ManagedObjectReference _this)

       at VMware.Vim.ServiceInstance.RetrieveServiceContent()

       at VMware.Vim.VimClientImpl.Connect()

       at ST.Virtual.Vim.VimClient.Connect()


    Test The Connection


    Perform the following to test the connection to the host server:


    1. Download Psexec at
    2. Open a new Command Prompt Window.
    3. Change directories where psexec.exe is located.
    4. Run the command: psexec.exe -i -s "C:\Program Files\Internet Explorer\iexplore.exe"
    5. A new Internet Explorer (IE) window will pop up. IE will be running as Local System which is key for this test.
    6. Type the URL to your vCenter (VM host) into the address bar of this new IE window.



    A successful connection would display the Getting Started page for VMware vSphere.  Connection warnings are OK as long as you can ignore them or make exceptions to get to this screen.




    Connection failures of this type indicate the Protect server, specifically the System Account, is unable to connect through a firewall or proxy to the host server.  The error 503 in the logs indicate the website is unavailable or the connection is being blocked.




    Customers have corrected this by adding exceptions for the vCenter URL to their firewall or proxy or allowing the System Account access through the proxy or firewall.  The fix for this will vary due to the customer environment configurations.


    Affected Product(s)


    Shavlik Protect 9.x