Event log Error: Failed to CoCreate profiler
Bruce Allen
Posts: 14
I am unable to run a complete performance profile on my asp.net app.
System:
WinXP SP2
ANTS 2.60
http://localhost/MeasuresWebUI
The app starts ok, but after logon and a couple of postbacks the app slows to a crawl and I start getting "Failed to CoCreate profiler" errors in the event log. I do get some profiling data before the problem starts, but nothing after. Sometimes, but not always, the app completely hangs and never returns from a postback.
I have read other posts and have already tried the following:
reregistered the core dll
run the service as a local administrator
reinstall ANTS, completely removing the previous installation folder
Thank you for any help you can provide
System:
WinXP SP2
ANTS 2.60
http://localhost/MeasuresWebUI
The app starts ok, but after logon and a couple of postbacks the app slows to a crawl and I start getting "Failed to CoCreate profiler" errors in the event log. I do get some profiling data before the problem starts, but nothing after. Sometimes, but not always, the app completely hangs and never returns from a postback.
I have read other posts and have already tried the following:
reregistered the core dll
run the service as a local administrator
reinstall ANTS, completely removing the previous installation folder
Thank you for any help you can provide
Comments
could you update to ANTS Profiler 2.7 please? You can achieve this by using the file menu Help->Check for updates
Do let us know if this makes any difference?
Best regards,
Tom Harris
Red Gate Software
Bruce
This is interesting... normally a failure to co-create profiler would prevent you from getting any results. Maybe you're trying to profile two applications at the same time?
given that the profiler starts profiling correctly, the 'failed to co-create profiler' errors probably reflect new processes that are being created (these will not be profiled as we only profile 1 process during each session). I'm not sure what would cause the app to run so slowly though. Could you try profiling a release build, or delete the pdb files?
Thanks,
Tom Harris
Red Gate Software
Does it have anything to do with the amount of methods being profiled? Maybe you are running too low on physical memory?
Bruce
Does your web application call any 'serviced components' (COM+) on the webserver? Maybe these are where the error is occurring?
Bruce
You can give it a try, but more than likely you won't have corelog.txt because the component is not loading in order to create its log.
Have we ruled out rights issues? Can you profile when you are logged in as administrator?
Bruce
Bruce
Bruce
Can you please try upgrading to version 2.7 of ANTS Profiler? This may help. Otherwise, you can try enabling logging, by creating a logs folder inside the ANTS Profiler folder. After restarting the ANTS Profiler Service, you will get some log files in the folder. Hopefully there will be a corelog_xxx.txt created before the Profiling crashes...
Bruce
Please email it to support@red-gate.com. Thanks!
According to your core log, a named pipe for ANTS Profiler cannot be started on your computer. The core component sets up a named pipe at \\.\ANTSProfiler, and for some reason, your computer is not allowing this. Have you checked your system log for any errors relating to named pipes?
Bruce
Thanks for that. The only evidence I can find in there is a bunch of application errors from aspnet_wp.exe. Can you please check the system log, as opposed, to the application log, for any errors relating to the system not being able to create a named pipe?
http://www.microsoft.com/technet/sysint ... lorer.mspx