Hello. I am trying to profile a service using CLR Profiler. It seems
to work just fine if I start CLR Profiler through the GUI, but the
default value of OMV_PATH=c:/Windows/Temp (where the log files are
written) is on a quite small partition.
I tried using the command line to start CLR Profiler. I used regsrv32
to register ProfilerOBJ.dll as per instructions (in CLRProfiler.doc
distributed with the app) and set all of the ENV variables
appropriately. I started CLR Profiler with the following command:
CLRProfiler -o foo.log -p net start ServiceName
When I executed the above command, a box popped up that said Waiting
for Common Language Runtime. Then a few minutes later an error message
popped up saying:
Debug Assertion Failed
Program:...CLRProfiler.exe
...
Am I doing something wrong in starting it from the command line?
Is there a way to start it through the GUI with other than default
values for the associated ENV variables?
kramer.newsreader@gmail.com - 07 Dec 2005 17:27 GMT
By the way, when I try to reproduce the error, an exception is thrown
rather than an assertion failing.
I get the message:
Additional information: The system cannot find the file specified
at
System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo
startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at CLRProfiler.Form1.startApplicationButton_Click(Object sender,
EventArgs e)
at CLRProfiler.Form1..ctor(String[] arguments)
Can anyone familiar with CLR please tell me whether this is the right
way to profile a service.
Thanks again.