Link to home
Start Free TrialLog in
Avatar of g_johnson
g_johnsonFlag for United States of America

asked on

.Net C# application failing on Server2000 terminal server

I have a C# .Net application written for the .Net 2.0 framework.  We are attempting to run it on a Server 2000 terminal server.  Before the form load event, we are getting the Windows warning that the program has stopped working -- send to Microsoft, etc.

Since this happens before the form load event, I don't know how to troubleshoot it.  I suppose it's failing to load a class or some such thing, but don't know how to find out for sure.  The error is definitely of the nature "file not found"

The .Net 2.0 framework has been installed on the server.

Any ideas how to troubleshoot.
ASKER CERTIFIED SOLUTION
Avatar of kaufmed
kaufmed
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of meraydin2
meraydin2

Does the problem still exist if you logon to Terminal Server with administrative rights?
Put a breakpoint on the Form's constructor and look around then.
Avatar of g_johnson

ASKER

kaufmed:  I'm going to try your suggestion today
meraydin2:  Yes, we are on with administrative rights
anyoneis:  I wish I could!  :)  It works fine in my development environment and I have no way (currently) to debug on the machine where it is failing -- thanks for the suggestion, though.
Nothing in the event logs on the server?
Are there any other .NET apps running in this environment?
If not, try a console app - hello world.
>>  It works fine in my development environment and I have no way (currently) to debug on the machine where it is failing

If it is a matter of not having (not being permitted) VS installed on the machine in which the app is failing, have you considered remote debugging?

http://msdn.microsoft.com/en-us/library/bt727f1t%28VS.71%29.aspx
http://www.microsoft.com/downloads/details.aspx?familyid=440EC902-3260-4CDC-B11A-6A9070A2AAAB&displaylang=en
I put this on another machine of mine and it failed, and since that machine at VS2005 installed I was able to do some level of debugging.  I believe this is going to turn out to be the Crystal runtime components not loading.  I am keeping this question open until I know for sure.