Unable to resolve exceptions. .NET environment or codes?

[Guest]

Am using VB in VS.NET 2003 (Framework 1.1) I am getting a CLR debugging
services "application has generated an exception that could not be handled"
error after deploying the apps and trying to run it on the client PC (XP Pro
SP2 with .NET framework 1.1 sp1). My application does not load. The error
msg has a process id and thread id that both change each time I try to run it.

I thought the problem might be my codes so I added try..catch..endtry
exception handling to the codes - that did not help. The application runs
well on at least 1 client PC, which makes me think the problem is with the
environment.

Can anyone help, please?

 

[Keith Patrick]

Try putting the try/catch block in the Main method. I've had issues before
not being able to catch an offender (was a permission or WPF error, IIRC),
and I ultimately was able to catch it at the entry point only.

 

[Guest]

Thanks Keith! I just tried that but the results are the same. It looks like
this.

Try
Dim popup As New WelcomeScreen
popup.ShowDialog()
Catch ex As Exception
MessageBox.Show(ex.ToString, "Error in Form1_Load()",
MessageBoxButtons.OK, MessageBoxIcon.Exclamation)
End Try

Any other ideas?

 

[Lloyd Dupont]

Is .NET installed on the machine?

 

[Guest]

Thanks Lloyd. Yes, .NET is installed. Like only 1 other machine on which
the application runs, this PC has the 1.03705 framework plus its 1.0 hotfix.
It also has the 1.1 framework plus its 1.1 hotfix. I even added the 2.0
framework, but the results are all the same.

Should I have something else installed other than the .NET framework?

 

[David Levine]

Try adding an unhandled exception handler and logging the exception to the
event log.

 

[Guest]

Thanks David! I did not get any results with the unhandled exception
handler. However, I applied your suggestion of using the event log and by
adding a logerror() writer at various sections of my code I pinpointed the
problem source.

My error handlers weren't firing because the problem is in VB's
InitializeComponent(), which runs BEFORE my codes in Main(). I was able to
track the error message by inserting a Try...EndTry in the
InitializeComponent() section.

I've found that crystal reports is the culprit. I got a
System.Runtime.InteropServices.COMException (0x80040154): COM object with
CLSID {#####} is either not valid or not registered. at
CrystalDecisions.CrystalReports.Engine.ReportDocument....

This error comes up when the Windows Form Designer executes the following
line:
Me.rptOMData1 = New Travel_Tracker.rptOMData

Doesn't Visual Studio 2003 add references to and packages the .NET objects
for Crystal Reports?

I'm thinking that I might need to add a reference to the COM object for
Crystal Reports Viewer Control 9 or something similar. Any other ideas?

Thanks so much!