CLR Profiler is not working with managed service

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Raghu - 26 Nov 2003 16:28 GMT

I am trying to profile a managed window service and I am not having any
luck.

Here is what I am doing:
1) Click on file menu and choose Profile Service.
2) Profile Service dialog appears
3) Enter the name of the managed service. Click OK.
4) Managed service is stopped and started again. (Note that the configured
identity for the service is not local system and I can not change it to
local system because of database permissions.)
5) Once the service starts up, I get modeless dialog box called "Waiting For
Connection". It stays like that for ever.
6) On main form, only Start Application is enabled.

I am at a loss. Any help is appreciated.

Thanks.
Raghu/..

Reply to this Message

Peter Sollich [MSFT] - 02 Dec 2003 14:45 GMT

Hi Raghu,

usually this is caused by the profiled process not having
sufficient privilege, hence the advice about running
ASP.NET under local system. You said you can't run your
service as local system, but can you run as a higher
privilege account? Like your own account?

Also make sure you have a recent version of CLRProfiler -
we fixed a few bugs with similar symptoms in the version
we published in October.

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

>-----Original Message-----
>I am trying to profile a managed window service and I am not having any
[quoted text clipped - 17 lines]
>
>.

Reply to this Message

Raghu - 02 Dec 2003 17:42 GMT

Thanks for the response.

1) The service is running with user identity that is part of local admin
group.
2) How can I get the latest CLRProfiler that has bug fixes?

Thanks again.
Raghu/..

> Hi Raghu,
>
[quoted text clipped - 41 lines]
> >
> >.

Reply to this Message

Peter Sollich [MSFT] - 03 Dec 2003 14:26 GMT

Hi Raghu,

The download location for the latest version is:

http://www.microsoft.com/downloads/details.aspx?
FamilyId=86CE6052-D7F4-4AEB-9B7A-
94635BEEBDDA&displaylang=en

There's also a link to it on
http://www.gotdotnet.com/team/clr/about_clr_performance.as
px

When we publish a newer version, we'll also update the
link on the gotdot page, so it maybe useful to bookmark.

Your problem sounds like it's not a privilege problem
after all - local admin group should be good enough.

When you attempt to profile, is the service actually
starting up or is it hanging? If it's hanging, it could
be a problem we recently fixed, so it's definitely
worthwhile trying the latest version.

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

>-----Original Message-----
>Thanks for the response.
[quoted text clipped - 53 lines]
>
>.

Reply to this Message

Raghu - 03 Dec 2003 18:12 GMT

This is where I loaded from previously and today again. The version of
CLRProfiler.Exe (actual binary) is 1.0.1395.16737. This binary is still
dated 10/27/03 9:17 AM.

When I start profiling the service, it stops and starts the window
application. The console window shows this. However the console window waits
for a while and disappears before the service is fully started. Then
"Waiting For Connection" pops and stays there forever.

I tried to make it work with another managed window service that is running
as local system. Same result here too.

How long should the "Wait For Connection" screen should show up? It says
waiting for service to start common language runtime? How could not the CLR
not loaded by this time (or alteast when service starts up)?

Thanks.
Raghu/..

> Hi Raghu,
>
[quoted text clipped - 95 lines]
> >
> >.

Reply to this Message

Peter Sollich [MSFT] - 04 Dec 2003 15:34 GMT

Hi Raghu,

The "Waiting for Connection" should normally only stay up
for a short time - it should go away when the CLR is
loaded. You could try to check whether the CLR is being
loaded by attaching a debugger (say windbg or similar)
and checking whether you see "mscorwks.dll"
or "mscorsvr.dll" being loaded in the process. You could
also check whether you see "profilerOBJ.dll" being loaded.

It's possible that your service is getting profiled, but
fails to connect to the profiler UI (CLRProfiler.exe). In
that case a "pipe.log" file would get generated in the
current directory of your service. Search for that
filename to verify.

You can cause your service to be profiled manually by
setting environment variables in the registry. Which
variables need to be set where is documented in the
manual that comes with the download. You can then load
the resulting log file into CLRProfiler (File/Open Log
File...).

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

>-----Original Message-----
>This is where I loaded from previously and today again. The version of
[quoted text clipped - 25 lines]
>>
>> There's also a link to it on

http://www.gotdotnet.com/team/clr/about_clr_performance.as

>> px
>>
[quoted text clipped - 87 lines]
>
>.

Reply to this Message

CLR Profiler is not working with managed service

Free Magazines