cancel
Showing results for 
Search instead for 
Did you mean: 

PulseLauncher.exe Connection Error

Highlighted
New Contributor

PulseLauncher.exe Connection Error

I'm using the PulseLauncher.exe command line program to automate and facilitate VPN connections for users of a WPF desktop application. I have written a utility to connect to the VPN using the .NET Framework's System.Diagnostics.Start class. The system correctly connects to the tunnel but everytime that it is ran to open a new connection, a pop up error is displayed stating, "Failed to download the application. Please sign in and try again. If the problem continues, please contact your system administrator."

 

This error is the same as reported here, but for the PulseLauncher. Additionally someone mentioned that the issue should have been fixed in version 8.1R4.1. The PulseLauncher version that I am running is 9.0.3.1599 which is the same as the Pulse Secure desktop client that I have installed on my machine.

3 REPLIES 3
New Contributor

Re: PulseLauncher.exe Connection Error

Closing all applications and restarting the computer caused the error to go away. After further testing it was determined that the error began occurring again after the "-stop" argument was sent to the ProgramLauncher.exe command line program.

Moderator
Moderator

Re: PulseLauncher.exe Connection Error

"Failed to download the application. Please sign in and try again. If the problem continues, please contact your system administrator" error message will be triggered by the Setup Client application.


I know that the setup client will check for lot of things like available updates, manifest download etc. If any one of the calls fail, it show the 'failed to download the application' message.

 

What is the Pulse Client and VPN server version? What events do you see on the debuglog.log file after successful connection? [C:\Programdata\Pulse Secure\Logging]

Moderator

Re: PulseLauncher.exe Connection Error

i would recommend opening a case with our support team for tracking down the incompatibility. i have not heard of anyone trying to do this prior to now; it could be there is a special command needed