Re: Certain applications in Terminal Services fail with Auto Launc

Here is what the problem was.

when I used %systemdrive% it would dissapear when I changed the path to use
C:\blah\blah\blah it started working. Longhorn by default populates the path
with systemdirve and this worked for all the other apps however with this one
it did not. Thanks for the help

"Vera Noest [MVP]" wrote:

Just for troubleshooting purposes: does it work when you create a
command file with the same syntax as you put into the starting
application in the rdp client, and then make that command file the
starting app?

I would also enable verbose logging of the user environment:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

And you could download Process Monitor (former FileMon and RegMon
combined) from
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/p
rocessmonitor.mspx
Run it as administrator on the server (when no user is connected),
start a TS session as a normal user and try to run the application.

Process Monitor will show you all "access denied" or "file not
found" errors that occur, which might show you what goes wrong.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VmVyc2lvbjc=?= <Version7@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 19 apr 2007 in
microsoft.public.windows.terminal_services:

I have set the working Directory on our 2003 servers however on
Longhorn when you publish an App it does not look like it asks
for a working Directory. Either way we get the same results on
both systems.

"Vera Noest [MVP]" wrote:

Did you set the working directory as well?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VmVyc2lvbjc=?= <Version7@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 18 apr 2007 in
microsoft.public.windows.terminal_services:

When I install the Axapta client in Terminal services the
program works fine if you log into a full desktop session on
the TS with your users who has been properly added to the
remote desktop group. If you edit your RDP and have the
program auto launch using the Start a Program under Programs
Tab I would use the following syntax which is the same as the
one being used on the TS desktop client.
"C:\Program Files\Navision\Axapta Client\Bin\ax32.exe"
"-regconfig=C:\Program Files\Navision\AX30PTST.xpo"

This begins to work loading the Axapta client however all of
a suddent if dissapears after laoding the Axapta screen and
goes away. I have seen this occur before with out
applications when trying to auto lauch them via the programs
tab. Is this security problem? How do you fix this problem
where the application does not stay up after an auto launch.
Thanks



This same problem occurs in both 2003 R2 TS as well as
Longhorn TS

.

Loading