Quantcast
Channel: LANDESK User Community : Popular Discussions - Software Distribution
Viewing all articles
Browse latest Browse all 2282

Issue with Portal Manager on Client Machine "CreateProcess failed to launch executable"

$
0
0

Hi,

 

I have run into this issue a number of time and I am wondering if there is a quick way to clear the client side task history.

 

I have published a number of Applications via the LaunchPad Link Manager.

 

The idea is that if the user does NOT have the application installed, it will be pushed out as a distribution task.

 

If the user DOES have the application installed. It will just launch the application.

 

The problem I am running into is that occasionally, for whatever reason, when an application is launched via Portal Manager and is NOT installed, it generated the error "CreateProcess failed to launch executable; contact your network administrator"

Now, I know the Distribution package works because if I try immediately after on another machine, it installed without issue. It may be that the machine drops connectivity momentarily but for whatever reason it fails with this error. It seems to me like the install fails, but the Portal Manager believes it installed correctly so next time the application is launched, it actually tries to execute rather than install.

 

I don't have a problem with this, because I know that if I could just retry the task, it would install correctly. The problem is that I cannot retry the task, If i try to launch the task again, it generates the same error message immediately. It does not try to reprocess the task. So, what I would like to know is, is there a way to clear the task history on the client so that it will try and install again?

 

I have seen a number of threads which mention scripts to clear database history but I am hoping that there is an easier way to clear the history than that?

 

Thanks

Alex


Viewing all articles
Browse latest Browse all 2282

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>