Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

.NET App will only run on terminal server under administrator login 1

Status
Not open for further replies.

Davenz

Programmer
Joined
Sep 13, 2002
Messages
34
Location
NZ
Hi

I've written an application in VB.NET and have deployed to a terminal server. The application will only runs under the administrator login.

If I login as a normal user nothing happens. just an hourglass for a few seconds and then nothing!

The application was installed in install mode using the "add/remove programs" in control panel and I have also tried it manually using "change user /install".

I then tried making the "hello word" app and this does not run either. I have access to two totally seperate terminal servers and the app behaves the same on both.

HELP

I have tried filemon and regmon but cannot see anything obvious (or don't know how to read it!)

Is there some other strange quirk with terminal server and .net apps?

Please help

Dave
 
not sure how security works over a term server (although if you find a fix to this, please post it as I have an term server install next week!). But you could try changing the .Net security on the user accounts that are trying to access it. you can find those controls at:

control panel\administrative tools\.Net Wizards


-Rick

----------------------
 
Thanks for you reply Rick

I've tried running the wizard under the normal user mode and it won't start either!!
If I try to run the .NET Framework 1.1 Configuration tool I get the following error:

Snap-in failed to initialize.

Both still run fine as an administrator

It must be a permissions issue of some sort??

 
Problem solved.

This seems really stupid but I ran windows update to get the lates service pack of the .NET framework, restarted the terminal server (which I thought had already been done but obviously not!!) and the problem dissapeared!

Dave
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top