Re: Debugging failed do to permissions
- From: "Gerrit H" <g.h@xxxxxx>
- Date: Wed, 24 Aug 2005 11:11:12 +0200
Tnx. for the response.
Interesting article, but the URLScan / IISLockdown cannot be the cause since
it is not installed. Even than, why can another developer debug from the
same machine under a different user account?
"Rakesh Rajan" <rakeshrajan {at} mvps {dot} org> wrote in message
news:91E2D9C2-174E-43F1-B1C6-95764E3BA72F@xxxxxxxxxxxxxxxx
> Hi,
>
> Could you check whether the entries in the "Secure IIS" section in:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/HTWorkStat.asp
>
> is what causes the issue?
>
> --
> HTH,
> Rakesh Rajan
> MVP, MCSD
> http://www.msmvps.com/rakeshrajan/
>
>
>
> "Gerrit H" wrote:
>
>> Situation: Windows 2003, .NET, developing server.
>>
>> When I try to debug the webapp, I get the message: 'Unable to start
>> debugging on the web server. You do not have permissions to debug the
>> server. Verify that you are a member of the debugger users group on the
>> server'.
>>
>> According to the computer management I am member of not only the debugger
>> group, but also the administrators. Thing is that is did work a couple of
>> weeks ago.
>>
>> I can manually attach the debugger to the w3wp.exe process and start the
>> debugging manually, but that is irritating doing that all the time.
>>
>> A 2nd developer with the same rights can 'normally' start the debug
>> proces.
>> So it appears that there something has gone wrong with my user account.
>>
>> Anyone any input?
>>
>>
>>
.
- References:
- Debugging failed do to permissions
- From: Gerrit H
- RE: Debugging failed do to permissions
- From: Rakesh Rajan
- Debugging failed do to permissions
- Prev by Date: Re: regex backreference
- Next by Date: AccessViolationException in 3rd party dll
- Previous by thread: RE: Debugging failed do to permissions
- Next by thread: ThreadPool - does it work with Serviced Components?
- Index(es):
Relevant Pages
|
|
