C# And Terminal Services

[TPoise!]

Using: .NET 1.1, Visual Studio 2003, C#, Microsoft Windows 2000
Server (SP4 and all latest windows updates), Terminal Server running
in application mode.


I have a C# application that I've deployed to our terminal server for
remote users to use. However, normal users (simple domain users) can
not run the application. After double clicking on the icon, an
hourglass appears as if its loading then it goes back to the normal
cursor. After investigating the issue, I saw that is causing an
exception that shows up in the server's event logs. Here is what I
get:

The application, , generated an application error The error occurred
on 05/1/2004 @ 17:41:59.990 The exception generated was c00000fd at
address 791B50C3 (Ordinal71)

Later in the detailed portion of the event, it shows that c00000fd is
a "Stack Overflow". I am not doing any recursive function calls or
anything like that. My application is multithreaded and accesses a
database. I even took out all the thread function calls and it still
would not work (gives same error).

The weird thing about this is if I give that user administrative
access, it'll work fine (over terminal services). Or, if I login with
a normal user's account from the console, it'll work fine. However, I
can not get it to work with a normal user over terminal services.
The application runs fine on Windows XP Professional as well. At this
point I don't believe it is a .NET or C# or an issue with my
application.


My question is, are there any options for me? Will Windows Server
2003 (or a 64-bit edition) fix my problem? Is there a way I can
expand the stack size (or other resources) for a terminal services
user? Is there a way I can compile my application differently that
uses less stack space?


Thanks, any and all help will be appreciated. I can be emailed
directly at tim .AT. outdoordecor.com

 

[Willy Denoyette [MVP]]

As it looks like it's happening very early at start-up (even before a form
is shown?), I would try to remove large portions of the application until it
works on TS.

W2K3 and increasing stack space are no options IMO.

Willy.

 

[N.K]

Can you post more details..

Are you telling App will work fine for
1 - Termainal Service user on Terminal Service
2 - Normal users on Workstations

BUT NOT FOR
1 - Terminal users on Workstations..



Are you accessing any registry information? Suggest to post some code
in startup routine which you suspect to be cause of this error.

 

[Timmothy Posey]

Thanks for replying. I've removed the large portion of the startup code
(it ran threads that loaded info from SQL Server), and still get the
same error. And no, it does not access the registry or anything like
that. Right now, it should only display the form with the controls, and
it does no startup code.


To clarify further, it works in the following situations:

1) The user has admin privileges and uses terminal services
2) The user has normal privileges and is logged in from the physical
console.
3) The user has normal privileges and is logged in using another
workstation on the network (the workstation is WinXP Pro)

It does not work when:

1) The user has normal user privileges and uses terminal services.


I am using Microsoft's built-in RDP (Remote Desktop Protocol) Client
version 5.1 that is included with Windows XP Pro.

The only reason why I was exploring the Windows Server 2003 option was
because we can upgrade to it relatively cheaply.


Thanks guys,

 

[Guest]

Ti

We had a similar problem with a vb.net app - the application would not even start up - I wrote a new app which was just a form and that had the same problem

the server had not been rebooted since the clr was installed

Long story short - Rebooted the server and everything was fine

Dave