"Marco" <marco@marcoganz.com> wrote in message
news:c2d18c8d.0401130653.49af08dc@posting.google.com...
> Hello Habib,
>
> > If I understand correctly, you are trying to attach to aspnet_wp.exe
with
> > the native debugger, correct? Is this because you want to debug the
> > aspnet_wp.exe process itself or do you have an ASP.NET application that
> > calls into native C++ code and you want to debug that code?
>
> That's it: what I really need is to debug my own ATL server which is
> referenced by a C# web service. Inside VS.NET I enabled "native" and
> "aspnet" debugging in the properties of my C# project but as soon as I
> start it (in debug mode of course) I get following error message:
>
> "Impossibile avviare il debug sul server Web. Non si dispone dei
> privilegi necessari per eseguire il debug dei processi sul server
> Web."
>
> (something like "cannot start debugging on the web sever. You do not
> have privileges to debug the web server process.")
>
> I can properly debug the C# web service by disabling "native"
> debugging inside its properties.
>
> The folders containing the source code for the ATL server are readable
> by Everybody.
>
> I noticed the "Access Denied" message when connecting to the
> aspnet_wp.exe process and I thought the problem could be related.
>
> > Unless you have changed the process model for aspnet_wp.exe, it should
be
> > running under the ASPNET account by default.
>
> My task manager shows one aspnet_wp.exe process running under the
> ASPNET username.
>
> > If this is true, then all you
> > need to make sure is that the user running Visual Studio is a member of:
> >
> > - Administrators
> > - Debugger Users
>
> As I wrote in my original message the user running VS is already
> member of both groups in addition to the "VS Developers" one.
>
> > The Visual Studio Debugger Proxy service is required to allow you to
detach
> > from native processes on Windows NT and 2000. It's not required if
you're
> > debugging on Windows XP and Windows Server 2003.
>
> Noted. I'm indeed running Windows 2000 Advanced Server with the latest
> SP.
>
> Any other suggestion please?
>
> Cheers
>
> -- Marco --
>
> PS: I can correctly debug my ATL server when referenced by a C#
> console application (i.e. no aspnet involved).
>
>
> > HabibH.
> >
> > "Marco" <marco@marcoganz.com> wrote in message
> > news:c2d18c8d.0401120215.6382e97f@posting.google.com...
> > > Hello there,
> > >
> > > As stated in the subject line I'm getting the error
> > >
> > > "Cannot connect to process. Access is denied."
> > >
> > > when trying to connect to the local "aspnet_wp.exe" process from the
> > > "Debug | Process" window in VStudio .NET 2002 (italian version), for
> > > NATIVE projects (CLR ones debug fine).
> > >
> > > My local account is member of the following groups:
> > >
> > > - Administrators
> > > - Debugger Users
> > > - Utenti Debugger
> > > - VS Developers
> > >
> > > The ASPNET account is member of
> > >
> > > - Users
> > > - Debugger Users
> > > - Utenti Debugger
> > > - VS Developers
> > >
> > >
> > > I can properly debug CLR projects and native code outside the
> > > aspnet_wp.exe process.
> > >
> > > I'm running on W2000 Advanced Server with the latest service pack.
> > >
> > > .NET Framework is version 1.1.4322.
> > >
> > > The problem seems to be specific to the "native" debugging inside the
> > > aspnet_wp process and I couldn't find other postings on the subject.
> > >
> > > I've also started the "Visual Studio Debugger Proxy" service.
> > >
> > > Any suggestions?
> > >
> > > Thank you already for your interest.
> > >
> > > -- Marco Ganz --

"Habib Heydarian [MSFT]" <habibh@online.microsoft.com> wrote in message news:<uhjz$he2DHA.308@TK2MSFTNGP11.phx.gbl>...

> Can you add the ASPNET account to the Administrators group and let me know
> whether that works?
>
> HabibH.
>
> "Marco" <marco@marcoganz.com> wrote in message
> news:c2d18c8d.0401130653.49af08dc@posting.google.com...
> > Hello Habib,
> >
> > > If I understand correctly, you are trying to attach to aspnet_wp.exe
> with
> > > the native debugger, correct? Is this because you want to debug the
> > > aspnet_wp.exe process itself or do you have an ASP.NET application that
> > > calls into native C++ code and you want to debug that code?
> >
> > That's it: what I really need is to debug my own ATL server which is
> > referenced by a C# web service. Inside VS.NET I enabled "native" and
> > "aspnet" debugging in the properties of my C# project but as soon as I
> > start it (in debug mode of course) I get following error message:
> >
> > "Impossibile avviare il debug sul server Web. Non si dispone dei
> > privilegi necessari per eseguire il debug dei processi sul server
> > Web."
> >
> > (something like "cannot start debugging on the web sever. You do not
> > have privileges to debug the web server process.")
> >
> > I can properly debug the C# web service by disabling "native"
> > debugging inside its properties.
> >
> > The folders containing the source code for the ATL server are readable
> > by Everybody.
> >
> > I noticed the "Access Denied" message when connecting to the
> > aspnet_wp.exe process and I thought the problem could be related.
> >
> > > Unless you have changed the process model for aspnet_wp.exe, it should
> be
> > > running under the ASPNET account by default.
> >
> > My task manager shows one aspnet_wp.exe process running under the
> > ASPNET username.
> >
> > > If this is true, then all you
> > > need to make sure is that the user running Visual Studio is a member of:
> > >
> > > - Administrators
> > > - Debugger Users
> >
> > As I wrote in my original message the user running VS is already
> > member of both groups in addition to the "VS Developers" one.
> >
> > > The Visual Studio Debugger Proxy service is required to allow you to
> detach
> > > from native processes on Windows NT and 2000. It's not required if
> you're
> > > debugging on Windows XP and Windows Server 2003.
> >
> > Noted. I'm indeed running Windows 2000 Advanced Server with the latest
> > SP.
> >
> > Any other suggestion please?
> >
> > Cheers
> >
> > -- Marco --
> >
> > PS: I can correctly debug my ATL server when referenced by a C#
> > console application (i.e. no aspnet involved).
> >
> >
> > > HabibH.
> > >
> > > "Marco" <marco@marcoganz.com> wrote in message
> > > news:c2d18c8d.0401120215.6382e97f@posting.google.com...
> > > > Hello there,
> > > >
> > > > As stated in the subject line I'm getting the error
> > > >
> > > > "Cannot connect to process. Access is denied."
> > > >
> > > > when trying to connect to the local "aspnet_wp.exe" process from the
> > > > "Debug | Process" window in VStudio .NET 2002 (italian version), for
> > > > NATIVE projects (CLR ones debug fine).
> > > >
> > > > My local account is member of the following groups:
> > > >
> > > > - Administrators
> > > > - Debugger Users
> > > > - Utenti Debugger
> > > > - VS Developers
> > > >
> > > > The ASPNET account is member of
> > > >
> > > > - Users
> > > > - Debugger Users
> > > > - Utenti Debugger
> > > > - VS Developers
> > > >
> > > >
> > > > I can properly debug CLR projects and native code outside the
> > > > aspnet_wp.exe process.
> > > >
> > > > I'm running on W2000 Advanced Server with the latest service pack.
> > > >
> > > > .NET Framework is version 1.1.4322.
> > > >
> > > > The problem seems to be specific to the "native" debugging inside the
> > > > aspnet_wp process and I couldn't find other postings on the subject.
> > > >
> > > > I've also started the "Visual Studio Debugger Proxy" service.
> > > >
> > > > Any suggestions?
> > > >
> > > > Thank you already for your interest.
> > > >