>This can happen with profilers.
>
[quoted text clipped - 16 lines]
>
>.
Hi Websparc,
CLRProfiler is telling ASP.NET that it is being profiled
by setting certain environment variables in the registry.
Normally it deletes these when you're done profiling, but
if it crashes or you kill it before that, these values
stay in there. This seems to be the problem here.
To delete these registry settings, bring up regedit.
Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
In there are subkeys for IISADMIN and W3SVC. For both of
these, if there's a registry value "Environment", delete
it.
When you get the new download (there's a link to it on
http://gotdotnet.com/team/clr/about_clr_performance.aspx),
it comes with a manual that documents these environment
variables.
Anyway, deleting these values should fix the problem.
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-----
>When you say environment variables you mean clearing them
[quoted text clipped - 44 lines]
>>
>.
Hi Peter,
Thanks for your reply. I've read that part of document
which mentions clearing the environment variables. I've
done that. So anyways i take your points in mind and
appriciate your help.
Websparc
>-----Original Message-----
>Hi Websparc,
[quoted text clipped - 89 lines]
>>
>.
David Browne - 21 Nov 2003 21:02 GMT
> Hi Websparc,
>
[quoted text clipped - 12 lines]
> these, if there's a registry value "Environment", delete
> it.
Ahh. So that's how it turns on profiling for ASP without forcing a reboot.
IIS is coded to add those values to its environment on startup.
I always wondered.
David