In my system, I have a number of applications that are invoked from the Windows Task Scheduler, i.e. they run unattended to do background processing.

I've found a few event log entries that I assume originated from one of these background tasks and I'm completely stuck as to how to diagnose the problem so I can fix it.

The messages are Error events, in the Application Event log, and they all have a format like this:

EventType clr20r3, P1 ezbqemtc5yn4bdrib0gep04ruhzx3qgp, P2 1.0.0.0, P3 47993265, P4 sd.llblgen.pro.ormsupportclasses.net20, P5 2.5.0.0, P6 471cca15, P7 11bf, P8 8f, P9 5s11pi0dzbt3ygdcdkat1jwohxctyitc, P10 NIL. 

(Some of the numbers are different in different events).

The error source is .NET 2.0 Runtime Error, Event ID is 5000.

I'm surprised to see these because I make extensive use of try-catch exception handling, and log everything using log4net. Having said that, I'm in the process of double-checking all my code for possibilities that exceptions don't get handled correctly.

I only post this here because sd.llblgen.pro.ormsupportclasses.net20 appears in the event text. Maybe it's not an LLBLGen-related problem at all.

Please, can anyone give me any advice as to how to start tracking down the cause of these event messages ?

Thanks in advance Mike

It might be that these events are logged because of the fact that an exception was thrown due to missing .config settings, which are swallowed. However, I don't think they should appear in the event log. For example on our development/test boxes no events are logged.

Which version of the runtime lib etc. are you using?

Hi Frans, and thanks for your response.

I'm using LLBLGen v2.5 Final (October 25 2007) Targeting SQL Server 2000 on a Windows 2000 Server box (yep, still....)

Runtime libraries are: SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll v2.5.0.0, File Version 2.5.07.0906 SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll v2.5.0.0, File Version 2.5.07.1019

I found some more .NET 2.0 Runtime Error events referencing libraries other than LLBLGen today, e.g....

EventType clr20r3, P1 {my assembly name here}, P2 1.0.0.0, P3 4797e181, P4 system.data, P5 2.0.0.0, P6 4333aea2, P7 25c3, P8 29, P9 system.data.sqlclient.sql, P10 NIL. 

... however it was logged at exactly the same time as this one:

EventType clr20r3, P1 10f2t1tv5ipuc1zwzp4cphpddhiywlyb, P2 1.0.0.0, P3 47a79e45, P4 sd.llblgen.pro.ormsupportclasses.net20, P5 2.5.0.0, P6 471cca15, P7 11c0, P8 8e, P9 5s11pi0dzbt3ygdcdkat1jwohxctyitc, P10 NIL. 

I'm still not convinced it's an LLBLGen problem... but if any clever person can help me I'd be very grateful

Thanks, Mike

Just to filter out the possibilities, would you please use the latest runtime library version available <01232008>, thanks.

There's a new version ?!

I will download and install it. Thanks for the heads-up. I guess it will be a few days before I can confirm whether the log messages are still appearing or not.

I'll post back here next week.

Thanks

I'll just close the thread now, and it will be re-opened automatically if a message is posted.