Can not get an application to run as a client

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am installing a new facility that was supposed to have all of my own
dedicated equipment as the backbone. Now that I am on site I have the IT guy
for this hall telling me that he does not have room for my machines and wants
me to get one of our applications to run from his thin clients over Windows
2003 terminal server. I set up the app that I needed on the server and I can
get it to connect to my database, but when I log in from the thin client I am
getting JIT debugger messages whenever I click on it and can not get any
further. Do I have to install the software as the remote user in order for
it to register the dlls?

Appreciate the help.
 
Was the Terminal Server in instal mode during installation of the
application? Either by installing from Control Panel - Add/Remove
programs or by typing "change user /install" at the command
prompt? If you just run the application setup.exe from the
installation media, registry changes are not monitored and copied
to the shadow area of the TS.

Are these dlls registered during installation, or during the first
time the application is executed?

186498 - Terminal Server Application Integration Information
http://support.microsoft.com/?kbid=186498
 
The dlls are registered through the installation process. We are using
installshield for al of our installers at this time. I can get the app to
run from the actual terminal server, meaning that if I log on to the server
and not as a client I can get it to connect and everything looks good. When
I log in as a client is when I start getting the JIT Debug errors. The only
time that I have seen this before is if you tried to run the software from a
machine that you only copied the exe to and did not actually run the setup
on, or if .NET 1.1 was not installed. Some of the code is written in .NET.
When I did run the setup.exe, all I did was log on to the TS server and run
it, I did not install it through the cpl\add remove programs as you
suggested. I will try that again tomorrow when I get in there.

Is there something that would prevent the app from being available to all
users by chance?

Craig
 
Yes, if the TS was not in install mode during installation, then
the application is *not* available for any other user than the
user that installed the application, and I would expect it to
behave exactly as you describe.
I would uninstall completely, and then reinstall in install mode.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Back
Top