PSEXEC Workflow component.

Last post 04-12-2018, 7:00 AM by CV123. 4 replies.
Sort Posts: Previous Next
  • PSEXEC Workflow component.
    Posted: 04-06-2018, 10:56 AM

    Getting this error on the PSEXEC workflow component not sure why???  the foloowing error is from workflow. both of my command files are working.when run them from the machine.   This Server does not have an agent on it. 


    ERROR: error executing command [cmd.exe] on host [cvcs501], errorCode [0], exitCode [-9], error [failed to launch app (remotely)]


    Tried running a Powershell script and also a batch file on the server and still does not like either of those. 


    All i am trying to do is write to the eventlog on a server from this script. 

  • Re: PSEXEC Workflow component.
    Posted: 04-06-2018, 3:49 PM

    Is the reason you want to use the PSExec activity because the remote client doesn't have the CommVault software installed on it?  Since if the remote client does have the CommVault software installed then you can just use the ExecuteCommand or ExecuteScript activities.

    Can you try executing the paexec.exe command manually from a command promt on the workflow engine client to see if that is working?  The location of this executable is in the <installation path>\WFEngine folder.  Also executing the command manually will allow you to enable debugging to see more information to troubleshoot.

    A couple of reasons why you can get this error is:

    1. If the workflow engine client and remote client or in the same domain, then you'll need to enable useImpersonation option on the PSExec activity input, otherwise you'll need this option off.

    2. You need to disable UAC on the client you need to execute the command on.


  • Re: PSEXEC Workflow component.
    Posted: 04-09-2018, 1:39 PM

    I am able to launch the paexec.exe command from the command prompt of the workflow engine. not sure about the syntax still working that out. 

    The UAC is disabled on the client. 


    We don't want to install the client on clients because we are trying to setup it up without a client install. Cause the Server we are doing this on will not allow us to install the Commvault Client.  

  • Re: PSEXEC Workflow component.
    Posted: 04-09-2018, 6:06 PM

    It looks like you may need to open a ticket so support can check and gather the logs so we can troubleshoot further.


  • Re: PSEXEC Workflow component.
    Posted: 04-12-2018, 7:00 AM

    I hope commvault services should be running on the target client to execute the commands or any activity using workflow. Think we can use proxy kind of servers with commvault installed to execute desired remote commands to target client using workflow.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy