Folks -

Has anyone been able to start a managed windows service through CLRProfiler
and actually get it to profile?

I've gone through the sparse posts that exist out there and my situation is
the same. I get the "Waiting For Connection" box. I verified that the
service is being started using Process Explorer but "profilerOBJ.dll" is not
getting loaded. Any suggestions?

Do I need to resort to modifying the registry?

Thanks.
ice

Hello Ice,

Usually this type of problem is caused by windows
security interfering with the communication between the
profiled application and the profiler. What account is
your service running under? Can you try to run it under
local system? Failing that, can you run it as a normal
executable for the purpose of profiling?

This posting is provided "AS IS" with no warranties, and
confers no rights.

Please do not send e-mail directly to this alias. This
alias is for newsgroup purposes only.

Thanks
Peter
[quoted text, click to view]