David
Wed Jan 21 22:59:13 CST 2004
Hmm... I've used that same documentation before and it worked for me, except
I used a file share (FrontPage is used to transfer files and make remote IIS
metabase changes, neither of which matter for debugging).
Debugger Users is necessary so that the remote identity can attach a
debugger on the necessary processes (though making the users Admininstrators
on the Server will do the same).
Make sure the server has Kernel Debugging turned off (though I think the
debugger will detect that and give a different error message).
My suspicion is that the remote identity is somehow not being treated as the
user but rather "guest", which doesn't have any such rights and fail.
Otherwise, I really don't know.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Calpha" <nunya-@nunya.com> wrote in message
news:caIPb.14808$xu6.10450@fe02.usenetserver.com...
Yes.
I've tackled a number of diff't issues thanks to the decent documentation,
but I've still been unable to get debugging working.
Basically---
Server has the Remote Components installed as per the docs.
Developers belong to VS Developers & Debugger Users. I've gone ahead and
put them in Admin now too, just to see if I can get it working.
FP Extensions are correctly configured. VS.Net IDE is set to connect to the
server via FP, not a file share.
The Site in question has it's own application created via IIS, with execute
set to scripts only.
web.config debug=true, customErrors = "off"
that's about all I can think of----
Most of what I followed came from the .Net 2003 install disk from Remote
Components setup & the Associated Readme/s. I did find a blog on msdn that
listed a bit of diff't directions for getting this accomplished (remote
debugging) but I've yet to follow those directions. It'd be nice to have a
link to that but I think I lost it w/ my last format of the server.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:u8$6nyJ4DHA.3576@TK2MSFTNGP11.phx.gbl...
> Did you read the VS.Net documentation on how to set up Remote Debugging?
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Calpha" <nunya-@nunya.com> wrote in message
> news:PKzPb.12226$xu6.1039@fe02.usenetserver.com...
> I have followed every readme/walkthrough I can find, and still no go.
>
> Trying to get Remote Debugging working for VS.Net 2003.
>
> Developer is a member of admin group on machine, fp extensions installed &
> working & configured. Project is opened via front page. Yet, still when
> trying to debug, get this message:
>
>
http://calpha.org/debugerror.gif
>
> TIA for any help. Been trying to get this owrking for a month now.
>
>
>
>
