"Failed to CoCreate profiler" in log after uninstalling ANTS
Brian Donahue
Posts: 6,590 Bronze 1
Hi Stephane,
I'd say it's more than likely that it has something to do with the profiler core component. This should only be called, however, if ANTS Profiler has enabled profiling for the application.
If the last thing that you had profiled was a web service or web application, can you try stopping and starting IISADMIN using the IISRESET command from the console?
Otherwise, I think it could be that ANTS Profiler has somehow interfered with another vendor's profiler (such as DevPartner's), so it might help to uninstall and reinstall their software.
I'd say it's more than likely that it has something to do with the profiler core component. This should only be called, however, if ANTS Profiler has enabled profiling for the application.
If the last thing that you had profiled was a web service or web application, can you try stopping and starting IISADMIN using the IISRESET command from the console?
Otherwise, I think it could be that ANTS Profiler has somehow interfered with another vendor's profiler (such as DevPartner's), so it might help to uninstall and reinstall their software.
This discussion has been closed.
Comments
Have you tried just installing ANTS Profiler again and uninstalling it?
Maybe the uninstall didn't work correctly. In particular, do you still have the ANTS Profiler service installed? You can check for that in Control Panel->Administrative Tools->Services.
First, try checking the default environment settings using regedit in HKEY_USERS\.Default\Environment to see if COR_PROFILER is set.
Next, check to see if the ASPNET account has its' own environment settings. I don't think it will unless it's logged in interactively. To check this, you'd need the ASPNET account's SID, which you can get by saving the following VB code to a file and running with cscript.exe: Check HKEY_USERS\<SID>\Environment and see if COR_PROFILER appears in there.