Custom Launcher Errors

Common errors when creating custom launchers:

The process (process name) was not found

The application has not been installed on the machine. If the application was installed, the program folder will need to be added to the path.

The stub received bad data (1783)

The process is set to launch as the credentials of the secret but the username or domain is not correct on the secret or the client machine cannot find the user or domain credentials specified.

Error(740): The requested operation requires elevation

When using "Run process as Secret credentials," even though the credentials have admin privileges, the process cannot be run with elevated privileges from the command prompt using runas. Instead, configure the process launcher as follows (substituting your .exe for program.exe):

  • Process Name: cmd.exe
  • Process Arguments: /C start /B program.exe /wait

This launch configuration is not supported by the Secret Server OS X launcher

This error appears on macOS when the launcher receives a configuration it cannot run. Check the Mac Settings section of the launcher for one of the following causes:

  • The Process Name is a command-line tool, a binary, or a shell script, such as /opt/homebrew/bin/sshpass, or it is the executable inside an application bundle, such as /Applications/Google Chrome.app/Contents/MacOS/Google Chrome. On macOS, the Process launcher type launches application bundles only. Enter the path to the .app bundle instead, for example /Applications/SecureCRT.app. To run a command-line tool, a binary, or a shell script, change the launcher type to Batch file and upload a shell script.

  • The launcher has no Mac Process Name and no Mac Batch file. Windows Settings are not used on macOS, so a launcher configured only for Windows fails on a Mac.

  • The launcher is a Process or Batch file launcher intended to open an SSH session in the macOS Terminal. Use the Proxied SSH process launcher described in Launching SSH Sessions with Mac-Native SSH Client in the Verify Privilege Vault Remote documentation instead.

See Mac Settings in Creating Custom Launchers for the settings that apply on macOS and a worked Batch file example.