program shuts down when logged in a remote desktop session but works in logmein

Does it shutdown or crash? (important difference here).

Is it possible that it was updated without using Install mode? (change user /install)

Coralon

It actually allows you to bring up the login screen for the app but once you select the data source or company within the accounting program that's when it just shuts down but doesn't crash. I didn't run the install so you could be on the right track about install mode being done incorrectly. The strange thing is that it works for any user if they are signed in using Logmein but when using Remote Desktop that's when only administrator works.

That makes it sound more like it was upgraded without install mode.

I don't know your Citrix background, so please forgive me if I'm covering known territory -
In RDS, the windows directory gets redirected to the home directory.  If you log in with LogMeIn, it is a 'direct' login that is not subject to the redirection.

I'd run a procmon against it and check the file activity and see if is trying to access something in the wrong directory.

I'd also back the machine up in whatever manner you have available, and reinstall it properly.

Coralon

Hi, i just wanted to make sure i did this correctly since its been a while since i last did it this way when installing a program on terminal server.  I go to add remove programs and select add new program then point to the installation directory where the install exe file is located.  I am logging in as administrator to do this but at what point during the install does it ask me whether i want to install the program for all users or just admin?  Or does it do this automatically since i am installing it thru add remove programs?  Also, i am running the install via remote desktop so will that be a problem or does install have to be run locally on server?  thanks

Hi again, i ran the reinstall using add remove programs and it still shut down as usual so was thinking about the procman you mentioned since one server is working with this app and the other isnt, how would i best go about using procman to compare and isolate where the problem file might be?  Im asking since i really am not familiar with using procman except for just running it but not knowledgeable how to set filters and so forth or how to go about isolating processes.

I actually started scanning using the filter "process name" and the exe which is called e4shell.exe but noticed it didnt bring up anything so i tested notepad.exe just to make sure i was setting procmon correctly and that came up right away once i ran notepad.  I will try it now on the server that is working and see if i get results from running the e4shell.exe.  Also, are you saying that since i ran the install using add remove programs that would not work and i should use the above method of change user /install then change user /execute.  I always used to use the add remove program method but i will try it again using your command line suggestion as well.

If the server isn't in in Terminal Server mode, it doesn't matter, but if it is used as a full-size Terminal Server (versus Remote Admin), it is important to change to install, install the application, change to execute. That makes sure the redirection ("folder virtualization") for users does not take place while installing, and necessary user entries are copied correctly as soon as Terminal Server users are logging in.

thanks for the clarification, i reinstalled the program after using change user /install command and at end of install it requested for server to restart and i did that so once its back up is it ok to use th change user /execute or was i supposed to do it prior to the restart?

If the change command doesn't request you to do a reboot, you do not need to.

After the reboot i tried the program again but no luck.  Will ask  one of the techs onsite to run the install again today but locally since i have been doing it remotely maybe thats still the reason its not working but i doubt it.  Really a strange problem since like i mentioned prior to this update the software was working fine last week and right after they updated it then those remote users had this isssue.  One other thing is that one of the users aside from administrator is able to log in athru remote desktop and can run the app without it shutting down so doesnt make sense.  As i also mentioned, on the other terminal server we have, there is no problem with the program for any users.