Any hints how to us the right commandline for WEM, if using the VUEMAppCmd.exe to start the Published Application with that commandline "C:\Program Files (x86)\SAP\FrontEnd\SAPgui\saplgpad.exe" /LSXML_File=\”\\Server\share$\SAP\SAPUILandscape.xml\” . The commandline is wrong, no Session logon is performed.

I assume the Command line works manually without VUEMAppCMD part? I never tried it with passing a xml file after this launch of the exe like you posted. Testing without the VUEM part does it open the app right? There are times I revert back to a cmd file that includes it all. With your powershell skill set definitely could try that and reference it all at once.

thx. not tested without VUEMAppCMD. But external call to a cmd or posh script, I will try that one

Looks like your escapes are blowing it out. Try wrapping the entire command line, including the exe and the args in “” without escape sequences, just a single string as if you were launching from cli

the app launch works if a previous application is started, but not if it's the first one

Hey @Matthias Schlimm, sorry I missed this from a couple of months ago, but this is what happens when the path to the executable and command line arguments combined are greater than 203 characters for a published application. It starts a new session and logs off immediately, but will launch okay if there is an existing session. So if you cannot reduce this length, you need to use a batch file or PowerShell script instead. It's been a bug/limitation for years.