Thanks for your post. We've not seen this message for a while from what I can tell. Are you definitely on the latest version?

If so, can you first try profiling your application on another machine, just to eliminate something being corrupt on the first box?

If that doesn't help, then it's likely that the line level option is hitting a security problem or similar, so trying with the profiler running elevated (right click - run as administrator) is a good first step, as is turning off your antivirus temporarily.

If the problem persists then we'll most likely need to know more about your code and any 3rd party assemblies you may be using. You can contact us directly by mailing support@red-gate.com quoting F0069401 in the subject.

I am experiencing the exact same issue. I tested with ANTS Profiler v4.last v5.last et v7.last, on two different machines, behavior is exactly the same.

My project is WinForm based, .Net 2.0, built using VS 20102, I am under Win XP.

What is really strange is that last time I profiled the same application (a few weeks ago on the same installation) I had no issue at all with my v5.last (which is my regular version). The source code was modified since then, of course, but we didn't add new library or made serious architecture modifications.

More precisely, the code where the exception now happen every time has not been changed for ages, and apart from using generics, I don't see anything particular here. I am pretty sure the call stack was the same last time I successfully profiled.

I tried to thing of what may have changed in my configuration, but I would tend to say nothing but automatic Windows Update stuff.

Could it be that an update to .Net, for instance, causes this issue?

Thanks in advance for your help, I need a way to profile my application with line details...

I guess the first thing is to look through your list of recent windows updates that were applied to see if anything looks relevant (security fixes, updates to .NET)
I believe it's possible to uninstall updates but that's all a bit trial-and-error unless there aren't many in between now and when it last worked...

Well, of course that's the thing to do... I just hoped you'll have some good idea to save me from this time consuming task

Anyway, I found the nasty update: it is named: KB2742596 and it's the before last .NET Framework 2.0 Service Pack 2 critical update. I installed it around January 18, 2013.

To figure this out I first removed the 2 last updates of this kind (the last one was installed this week): everything went right (not even had to rebuild my solution): no exception during profiling. I reinstalled KB2742596: crash.

So, now at least I can work, but I have the feeling that this situation is not very stable: should I refuse any critical update from now on? Doesn't sound good.

Apologies - I was out of the office on Friday, however some of our dev team have attempted to reproduce the problem by testing on machines with/without the applicable patch. Although it seems to be causing problems for other people (unrelated to our profilers) such as here.

I'm guessing that the problem is down to a combination of that patch and your particular application- are you able to supply us your app or alternatively something simple that demonstrates the same problem?

Josh- If you don't have the relevant windows update, you may well be experiencing a different issue. There's a whole host of potential causes for an application crashing. Assuming you've checked over all the options here it's likely to be an application-specific problem and we'd really need some sort of reproduction here to investigate further.