What exactly does the commnd line argument do. I can't really see it from the snapshot. If it's calling some type of update I would expect it to fail.
As I posted in the original post, the command line arguments are:
-Djava.ext.dirs=lib;lib\web -jar UpdateClient.jar
It is just some Java stuff needed to run the program.
BTW, I have had this successfully running via the LaunchPad before I upgraded to 9.0 SP2, which goofed up a number of distribution tasks for me. LANDesk support provided a patch that fixed that, but now I need to rebuild some Launchpad tasks that are throwing this error. Unfortunately, the rebuilt tasks are presenting the same error!
If it worked before my guess is you modified the link. If you do this it breaks the task and you have to recreate it from scratch.
No modifications, but I did upgrade to 9.0 SP2, maybe that did it. I will try to re-create the task. I would have done that before, but the SP2 upgrade messed up the distribution task for this particular Launchpad link, so I could not delete the task, or the link. That is all finally sorted.
I have completely rebuilt the link, and I still get the shortcut.runner error. In the shortcut (C:\documents and settings\all users\application data\landesk\management suite\launchpad\) there is "CreateShortcut.LDMS9.1782.74.74" listed in the target.
Hmm - I would recommend opening this as a support ticket with LANDesk support at this point.
I would probably suggest / be tempted to run a black box to see if there's anything else we can learn on why this link in particular decides to fail / die ... it sounds like this direct approach may be easier.
My guess is that it's something environmental/related to this link in particular that isn't going to be really identifiable on a forum.
It may be useful to then - later - update this thread with any resolution, but in order to progress this I would suggest a more direct form of contact / troubleshooting .
(NOTE that this would ideally require for us to remote into your environment, so that we can have a look at a few other things as well).
- Paul Hoffmann
LANDesk EMEA Technical Lead
Yeah, I figured as much... I opened a case yesterday. I will come back and update with what I find. Thanks for the help thus far!
Is there a reason why you are specifying a full path in the target and using a different "start in"? I think that is the problem.
It should look like this
you should have
Javaw.exe in the target
<your args> in the comman line arguments
That should work.
My settings for the shortcut are correct. This was working perfectly until our upgrade to SP2 of 9.0.
If you look at the first screenshot, you see that what is being generated for the shrotcut is a linkrunner error and not what was specified in the LaunchPad task.
There are basically 3 reasons for this error.
- Shortcut is orphaned (user no longer targeted)
- user not authorized to access application
- shortcut not found in database or contains invalid data
Can you attach your shortcut.runner.log and the shortcuts associated SDClientTask.*.XML file from C:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\landesk\files\
I am having the same issue I believe. From what I can see it is directly related to tying a distribution package to the link. If I remove the distribution package and make it just an executable, it will launch properly. Please let me know if there is anything else you need.
Who is the owner of this distribution package? I see this in the XML
<Group>'Administrators' packagesHorizon Clinicals</Group>
Do you have a special character or something in the owners name? What happens if you change the package owner to Public User and recreate the link in Link Managment?
I have created a Team called Administrators. LANDesk put the quotes around it. I have deleted the Package, Schedule and Link. I recreated the Package under Public and then recreated everything else. I still get the same error. If I take the Package out of the equation and just make it an executable, the link will launch.