Installed C# app only works as Administrator on Terminal Server

  • Thread starter Thread starter Tim Nelson
  • Start date Start date
T

Tim Nelson

I created a simple C# .Net application to prove I can deploy it on a
Win2k server running terminal services. I installed the 1.1 .Net
Framework and installed the application (using a VS Setup app) on the
machine. It runs perfectly when I log in as Administrator but generates
an exception when I run it as any other user. Do I need a reboot or
something after installing the framework? Do I need to tweak something
in the .Net framework settings? All the application is doing is opening
a message box :-( Please help the terminal services impaired :-)
Thanks.
 
Tim said:
I created a simple C# .Net application to prove I can deploy it on a
Win2k server running terminal services. I installed the 1.1 .Net
Framework and installed the application (using a VS Setup app) on the
machine. It runs perfectly when I log in as Administrator but generates
an exception when I run it as any other user. Do I need a reboot or
something after installing the framework? Do I need to tweak something
in the .Net framework settings? All the application is doing is opening
a message box :-( Please help the terminal services impaired :-)
Thanks.
If anyone cares... a reboot of the NT server fixed the issue. Not sure
why since the .Net Framework install didn't ask me to reboot. Must be a
terminal services user mode must not recognized changes like the console
user.
 
Hi!

Tim said:
If anyone cares... a reboot of the NT server fixed the issue. Not sure
why since the .Net Framework install didn't ask me to reboot. Must be a
terminal services user mode must not recognized changes like the console
user.

Sorry I didn't answer to your original post, but somehow I managed not to
see it at all...

We experienced the same problem some time ago; when we installed a .NET
application on Win2000 Server, it displayed a somewhat obscure message box
and did nothing else when starting the app vis Citrix. After rebooting,
everything was fine.
On another server, we tried installing the framework and rebooted the server
before launching the application, and everything went fine.

Maybe the .NET framework installer should ask for a reboot after it has
finished, at least on W2K server...
 
Back
Top