Googling reveals that presence of pnp.exe *might* be a symptom of ZOTOB.O. (http://www.securitystronghold.com/gates/zotob.o.html). Also, the IOException may provide a clue as to the location of the error.
As for the runtime, assemblies compiled against .NET 3.5 still run against the .NET 2.0 runtime. In fact, there *is no* runtime for v. 3.5. The next version of the runtime is 4.0 (VS 2010, .NET 4.0). So, the error reporting is normal. On Sep 30, 8:52 am, "Jeff Steinkamp \(N7YG\)" <[email protected]> wrote: > ?I have a piece of software that is being used by about 300 folks. I've got > a couple that are reporting getting a system exception report that is outside > of the program similar to the following: > > Event Type: Error > Event Source: .NET Runtime 2.0 Error Reporting > Event Category: None > Event ID: 5000 > Date: 9/28/2010 > Time: 9:12:50 PM > User: N/A > Computer: FINGERROCK7 > Description: > EventType clr20r3, P1 pnp.exe, P2 4.4.1.7, P3 4c9fde04, P4 system, P5 > 2.0.0.0, P6 4ba85929, P7 2913, P8 ef, P9 system.io.ioexception, P10 NIL. > > For more information, see Help and Support Center > athttp://go.microsoft.com/fwlink/events.asp. > > I've got a boat load of error catching along with a catch all for unhandled > exceptions, but for some reason this one is not bubbling up though the > program and instead is being generated at the system. > > Anyone got a idea on how to go about trapping this error or figure out where > it is coming from? > > The Event Source says Runtime 2.0 and P5 seems to indicate .NET 2.0, but this > thing is suppose to be complied against .NET 3.5, or at least I though it > was. Am I missing something here? > > Jeff K. Steinkamp N7YG > Tucson, AZ > SCUD Missile Coordinates: > N032-13-55.02 W110-55-52.79 > Registered Linux User: 420428 > ------------------------------------------------------ > > Druids do it in the woods
