Program not starting

[Bjarne Nielsen]

Hi all

I have developed a program, that runs under .NET framework 2.0. On my own
computer and all the other computers in my company, things run smoothly.

My problem is, that I have installed it at one of our customers, and when I
try to start the program, nothing happens. The program pops up in the job
list, but disappears after about half a second. Nothing visible shows on
the screen.

When I inspect the error log (or whatever it is called in the English
version of Windows), there is an error ".NET Runtime 2.0 Error Reporting
Type : Error " with an error code of 1000.

The problem and computer is at our customer far away, so I have limited
possibilities to try out things on site.

Any suggestions?

Cheers
Bjarne Nielsen

[Nicholas Paldino [.NET/C# MVP]]

Bjarne,

Are you sure that the .NET framework 2.0 is installed on the machine you
are trying to run this program on?

If it is, do you have any logging in your program to catch unhandled
exceptions which could provide some more information?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bjarne Nielsen" <bn******@post11.tele.dkwrote in message
news:26****************************@40tude.net...

Hi all

I have developed a program, that runs under .NET framework 2.0. On my own
computer and all the other computers in my company, things run smoothly.

My problem is, that I have installed it at one of our customers, and when
I
try to start the program, nothing happens. The program pops up in the job
list, but disappears after about half a second. Nothing visible shows on
the screen.

When I inspect the error log (or whatever it is called in the English
version of Windows), there is an error ".NET Runtime 2.0 Error Reporting
Type : Error " with an error code of 1000.

The problem and computer is at our customer far away, so I have limited
possibilities to try out things on site.

Any suggestions?

Cheers
Bjarne Nielsen

[Bjarne Nielsen]

On Fri, 24 Aug 2007 10:02:59 -0400, Nicholas Paldino [.NET/C# MVP] wrote:

Bjarne,

Are you sure that the .NET framework 2.0 is installed on the machine you
are trying to run this program on?

If it is, do you have any logging in your program to catch unhandled
exceptions which could provide some more information?

Thanks for your suggestions

I am sure that .NET framework 2.0 (and 3.0) is installed on the machine.
The OS is WinXP with SP2, as is my own.

I don't get any logging information, so I suspect that the program is
terminated before I get any chance to log anything unexpected. Not that I
do log much in the release version (if any), but I could do that, or give
them a debug version, if that would help. Anyway, I suppose an unhandled
exception would at least give you a dialog box, telling about the unhandled
exception, but I don't even get that.

Cheers
Bjarne Nielsen

[Nicholas Paldino [.NET/C# MVP]]

Is there any code on startup that you are executing which could be doing
this? Anything in the constructor of your forms? Are you using any COM
objects which you might not have registered?

More information is needed, and I'd advise you to put some logging in
there to find out if your program is even starting up at all.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bjarne Nielsen" <bn******@post11.tele.dkwrote in message
news:9q*****************************@40tude.net...

On Fri, 24 Aug 2007 10:02:59 -0400, Nicholas Paldino [.NET/C# MVP] wrote:

>Bjarne,

Are you sure that the .NET framework 2.0 is installed on the machine
you
are trying to run this program on?

If it is, do you have any logging in your program to catch unhandled
exceptions which could provide some more information?

Thanks for your suggestions

I am sure that .NET framework 2.0 (and 3.0) is installed on the machine.
The OS is WinXP with SP2, as is my own.

I don't get any logging information, so I suspect that the program is
terminated before I get any chance to log anything unexpected. Not that I
do log much in the release version (if any), but I could do that, or give
them a debug version, if that would help. Anyway, I suppose an unhandled
exception would at least give you a dialog box, telling about the
unhandled
exception, but I don't even get that.

Cheers
Bjarne Nielsen

[Alun Harford]

Bjarne Nielsen wrote:

On Fri, 24 Aug 2007 10:02:59 -0400, Nicholas Paldino [.NET/C# MVP] wrote:

>Bjarne,

Are you sure that the .NET framework 2.0 is installed on the machine you
are trying to run this program on?

If it is, do you have any logging in your program to catch unhandled
exceptions which could provide some more information?

Thanks for your suggestions

I am sure that .NET framework 2.0 (and 3.0) is installed on the machine.
The OS is WinXP with SP2, as is my own.

I don't get any logging information, so I suspect that the program is
terminated before I get any chance to log anything unexpected. Not that I
do log much in the release version (if any), but I could do that, or give
them a debug version, if that would help. Anyway, I suppose an unhandled
exception would at least give you a dialog box, telling about the unhandled
exception, but I don't even get that.

Yes, that should happen.
Are you using Application.Exit() or Environment.Exit() around anywhere
in your code?

Alun Harford

[Marc Gravell]

I have seen similar behavior on a machine that had got its .NET
knickers in a twist. The process would appear and then die. No errors;
no event-log; no fusion log; just no "Main()", even if I reduced it to
"hello world".

I gave up; it was cheaper for us to swap-out the machine (or more
accurately, provide a second machine for the purpose, since the first
had some financial apps installed that would have been a nuicance to
transfer).

Like in your situation, a long drawn out "OK, so that attempt didn't
work; lets try reinstalling these 17 core components (like .NET)" just
wasn't practical.

Marc