Event log Error: Failed to CoCreate profiler

Bruce Allen

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

Tom Harris

Hi there,

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 Allen

I installed 2.7 and attempted to profile again. Nothing changed. The behavior is exactly the same as described in my original post. Again, I tried running the service as a member of local administrators and that did not help either.

Bruce

Brian Donahue

Hi 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?

Tom Harris

Hi there,

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

Bruce Allen

I tried profiling a release build with no pdb files and nothing changed. I had another developer in the office profile his app and the same thing happened. The strange thing is that it does not always happen at the same place. Usually the login page loads just fine, and after a couple of postbacks the errors begin. But sometimes it's on Page A and sometimes it's on page B, and it might be different on the next run. Our code is not starting any new processes.

Brian Donahue

Hello,

Does it have anything to do with the amount of methods being profiled? Maybe you are running too low on physical memory?

Bruce Allen

No, I have 2 gigs and I'm only using about 1.25 gigs

Bruce

Brian Donahue

Hi Bruce,

Does your web application call any 'serviced components' (COM+) on the webserver? Maybe these are where the error is occurring?

Bruce Allen

Nope, no serviced components

Bruce Allen

So what's the next step. This issue is still unresolved. Would you like some logs?

Bruce

Brian Donahue

Hi 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 Allen

I am a member of the local administrators group, so it's always running as an admin. The service is also running as me, so I don't think it's a security problem.

Bruce

Brian Donahue

Silly idea but may work... can you temporarily make the ASPNET user a member of the local computer's administrators group and see if you can profile then?

Bruce Allen

To my surprise, I found that ASPNET was already a member of local administrators.

Bruce

Brian Donahue

Then ASPNET is the user that the code is running as, I assume. This computer is not also a domain controller, is it? If so, are you using mandatory or roaming profiles, and is the server also a terminal server or are you otherwise remoting into the server?

Bruce Allen

Machine is neither a domain controller or a terminal server. Just plain old Win XP Pro, SP2.

Bruce

Brian Donahue

Hello 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 Allen

Per previous instructions, I have already upgraded to 2.7. I did enable logging and I have corelog file. I don't see a way to upload it in the forum. What would you like me to do with it?

Bruce

Brian Donahue

Hi Bruce,

Please email it to support@red-gate.com. Thanks!

Bruce Allen

file sent

Brian Donahue

How about changing the account logon for the ANTS Profiler Service in the services control panel from LocalSystem to a named account with admin rights?

Bruce Allen

already tried that. no improvement.

Brian Donahue

Hi Bruce,

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 Allen

I don't see any errors like that in the event log. I have sent you my Application Event log for your inspection.

Bruce

Brian Donahue

Hi 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?

Brian Donahue

Can you try using sysinternals Process Explorer to see if there is already an open named pipe called \\.\ANTSProfiler?
http://www.microsoft.com/technet/sysint ... lorer.mspx