Application crash on W2K Server / XP client setup

[Valerie Hough]

I have the following configuration:

- W2K Server SP4
- SQL Server 2000
- 3 identical (hw and sw from Dell) XP SP1 clients

My application is a windows form written in C# and built with VS 2003 from
the command line, and runs under .NET v1.1.

My problem is this: I have an executable that runs happily on 2 of the 3
workstations but crashes on the third with a message box from the Common
Language Runtime Debugging Services saying:

Application has generated an exception that could not be handled

Process id = blah blah blah

Click Ok...
Click Cancel...

The executable (and all supporting DLLs) are exactly the same on each
machine.

I have tried putting a MessageBox as the first line of the form's
constructor, but execution appears never to get as far as that.

Does anyone know what the problem might be or
suggest how I might discover what is going on here?

Thanks in advance.
Valerie Hough

P.S.
I had this problem at another client site and when XP was replaced with W2K
on the offending workstation the problem disappeared.

 

[Peter Hutchison]

I have the following configuration:

- W2K Server SP4
- SQL Server 2000
- 3 identical (hw and sw from Dell) XP SP1 clients

My application is a windows form written in C# and built with VS 2003 from
the command line, and runs under .NET v1.1.

My problem is this: I have an executable that runs happily on 2 of the 3
workstations but crashes on the third with a message box from the Common
Language Runtime Debugging Services saying:

Application has generated an exception that could not be handled

Process id = blah blah blah

Click Ok...
Click Cancel...

The executable (and all supporting DLLs) are exactly the same on each
machine.

I have tried putting a MessageBox as the first line of the form's
constructor, but execution appears never to get as far as that.

Does anyone know what the problem might be or
suggest how I might discover what is going on here?

Thanks in advance.
Valerie Hough

P.S.
I had this problem at another client site and when XP was replaced with W2K
on the offending workstation the problem disappeared.

Could be any number of issues:
1. Spyware or viruses
2. Memory issues
3. Disk issues
4. Security issues (check Security level in .NET Framework config)

Peter Hutchison