.NET CLR2.0 error with CLR1.x profiler

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

TonyB - 18 Sep 2007 19:20 GMT

I'm looking for information to help debug the following message in the System
Event log:

.NET Runtime version 2.0.50727.42 - CLR 2.0 does not support profilers
written for CLR 1.x

What debug tools are helpful in tracking down the source of this error?

Thanks,
Tony

Reply to this Message

Jon Skeet [C# MVP] - 18 Sep 2007 19:30 GMT

> I'm looking for information to help debug the following message in the System
> Event log:
[quoted text clipped - 3 lines]
>
> What debug tools are helpful in tracking down the source of this error?

Well, it sounds like you've been trying to profile a 2.0 application
with a 1.x profiler. Have you been doing any profiling recently?

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Reply to this Message

TonyB - 18 Sep 2007 21:24 GMT

Jon,

I am not running any profiling tools (that I know of). I'm running the VI
Client
from VMWare to access server data from a remote client. I can run the app
and view local config info, but when I try to retrieve config info from the
server
I get the error listed earlier. Are there any debuggers that I can attach to
the app to see what .NET functions are being called. VMWare assures me that
they are not calling .NET 1.1, but there may be an error in the app that
triggers
a profiler. I've also tried uninstalling .NET 1.1 and leaving only 2.0 on
the system
but get the same error.

Thanks,
Tony

> > I'm looking for information to help debug the following message in the System
> > Event log:
[quoted text clipped - 6 lines]
> Well, it sounds like you've been trying to profile a 2.0 application
> with a 1.x profiler. Have you been doing any profiling recently?

Reply to this Message

Jon Skeet [C# MVP] - 19 Sep 2007 07:47 GMT

> I am not running any profiling tools (that I know of). I'm running
> the VI Client from VMWare to access server data from a remote client.
[quoted text clipped - 5 lines]
> a profiler. I've also tried uninstalling .NET 1.1 and leaving only
> 2.0 on the system but get the same error.

Hmm... that does all sound very odd. No, I'm afraid I don't have any
further ideas. Have you googled to see if anyone else is having the
problem?

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Reply to this Message

Rate this thread:

.NET CLR2.0 error with CLR1.x profiler

Free Magazines