"Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
news:WbAXzDv3DHA.1512@cpmsftngxa07.phx.gbl...
> Hi,
> What error message you got when you try to debug? What kind of app are you
> debugging? Can you try to debug a unmanaged VC++ app?
> I just did this test and it works fine for me:
> 1. Server: Win2k Server with VS .NET 2003.
> 2. Client: WinXP
> 3. Started 3 Remote Desktop Connection. Connected with 2 differnet users
> who have admin previledge on the server. Used one user twice.
> 4. Started VS .NET 2003 and tried to debug the same VC++ unmanaged
project.
> 5. I'm able to debug on all TS sessions.
>
> Thanks,
>
> Jiange Sun
>
> Microsoft Developer Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to newsgroups only.
>

"Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
news:WbAXzDv3DHA.1512@cpmsftngxa07.phx.gbl...
> Hi,
> What error message you got when you try to debug? What kind of app are you
> debugging? Can you try to debug a unmanaged VC++ app?
> I just did this test and it works fine for me:
> 1. Server: Win2k Server with VS .NET 2003.
> 2. Client: WinXP
> 3. Started 3 Remote Desktop Connection. Connected with 2 differnet users
> who have admin previledge on the server. Used one user twice.
> 4. Started VS .NET 2003 and tried to debug the same VC++ unmanaged
project.
> 5. I'm able to debug on all TS sessions.
>
> Thanks,
>
> Jiange Sun
>
> Microsoft Developer Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to newsgroups only.
>

"Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
news:9QdpayC4DHA.2488@cpmsftngxa07.phx.gbl...
> Hi Wayne,
>
> The error message itself explaines why you failed to attach a debugger:
>
****************************************************************************
> ********
> Error while trying to run project: Unable to start debugging on the web
> server. A debugger is already attached.
>
****************************************************************************
> ********
>
> As you know, only one debugger can attach a debuggee. You receive above
> error when there is alreay a debugger attached and you try to attach
> another debugger to the debuggee (aspnet_wp.exe in this case).
>
> What's the application protection level for the web applicaitons you're
> trying to debug? You should be able to debug multiple ASP .NET web
> applicaitons simultaneously if you set their application protection level
> to hign(isolated) because each ASP .NET web application will be running in
> it's own aspnet_wp.exe
>
> Thanks,
>
> Jiange Sun
>
> Microsoft Developer Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Please reply to newsgroups only.
>

<bubba@cfwebmasters.com> wrote in message
news:u8q5x7D4DHA.2428@tk2msftngp13.phx.gbl...
> Every web sites on the DEV server is in High (Isolated) application
> protection (I just double checked to make sure). But I should be able to
> debug "web application 1" and the other devhead should be able to debug
"web
> application 2" since they are not suppose to be sharing the same processes
> when in High (Isolated) application protection but for some reason I am
> still getting the error and I can not figure out why. None the
applications
> are not sharing any class file in debug mode (we have a common set of
tools
> (tis.tools.dll) that we use from site to site).
>
> However, this may be an issue ALL of the dev web site must use ports for
> example:
> "web application 1" is http://dev:8001
> "web application 2" is http://dev:8002
> "web application 10" is http://dev:8023
>
> I hope this additional information helps but, to clearly answer your
> question below, Yes ALL web sites (including default) on the DEV server
are
> running in High (Isolated) Application Protection.
>
> Thanks
>
> -Wayne
>
>
>
> "Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
> news:9QdpayC4DHA.2488@cpmsftngxa07.phx.gbl...
> > Hi Wayne,
> >
> > The error message itself explaines why you failed to attach a debugger:
> >
>
****************************************************************************
> > ********
> > Error while trying to run project: Unable to start debugging on the web
> > server. A debugger is already attached.
> >
>
****************************************************************************
> > ********
> >
> > As you know, only one debugger can attach a debuggee. You receive above
> > error when there is alreay a debugger attached and you try to attach
> > another debugger to the debuggee (aspnet_wp.exe in this case).
> >
> > What's the application protection level for the web applicaitons you're
> > trying to debug? You should be able to debug multiple ASP .NET web
> > applicaitons simultaneously if you set their application protection
level
> > to hign(isolated) because each ASP .NET web application will be running
in
> > it's own aspnet_wp.exe
> >
> > Thanks,
> >
> > Jiange Sun
> >
> > Microsoft Developer Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > Please reply to newsgroups only.
> >
>
>

"Habib Heydarian [MSFT]" <habibh@online.microsoft.com> wrote in message
news:OA1MIja4DHA.360@TK2MSFTNGP12.phx.gbl...
> Wayne,
>
> It is a known limitation that you can only debug one web application at a
> time on IIS 5.1 or below. However, if you have IIS 6.0 (which comes with
> Window Server 2003), you can take advantage of the app pools feature and
> setup your web applications so that multiple users can debug different web
> applications at the same time.
>
> HabibH.
>
> <bubba@cfwebmasters.com> wrote in message
> news:u8q5x7D4DHA.2428@tk2msftngp13.phx.gbl...
> > Every web sites on the DEV server is in High (Isolated) application
> > protection (I just double checked to make sure). But I should be able
to
> > debug "web application 1" and the other devhead should be able to debug
> "web
> > application 2" since they are not suppose to be sharing the same
processes
> > when in High (Isolated) application protection but for some reason I am
> > still getting the error and I can not figure out why. None the
> applications
> > are not sharing any class file in debug mode (we have a common set of
> tools
> > (tis.tools.dll) that we use from site to site).
> >
> > However, this may be an issue ALL of the dev web site must use ports for
> > example:
> > "web application 1" is http://dev:8001
> > "web application 2" is http://dev:8002
> > "web application 10" is http://dev:8023
> >
> > I hope this additional information helps but, to clearly answer your
> > question below, Yes ALL web sites (including default) on the DEV server
> are
> > running in High (Isolated) Application Protection.
> >
> > Thanks
> >
> > -Wayne
> >
> >
> >
> > "Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
> > news:9QdpayC4DHA.2488@cpmsftngxa07.phx.gbl...
> > > Hi Wayne,
> > >
> > > The error message itself explaines why you failed to attach a
debugger:
> > >
> >
>
****************************************************************************
> > > ********
> > > Error while trying to run project: Unable to start debugging on the
web
> > > server. A debugger is already attached.
> > >
> >
>
****************************************************************************
> > > ********
> > >
> > > As you know, only one debugger can attach a debuggee. You receive
above
> > > error when there is alreay a debugger attached and you try to attach
> > > another debugger to the debuggee (aspnet_wp.exe in this case).
> > >
> > > What's the application protection level for the web applicaitons
you're
> > > trying to debug? You should be able to debug multiple ASP .NET web
> > > applicaitons simultaneously if you set their application protection
> level
> > > to hign(isolated) because each ASP .NET web application will be
running
> in
> > > it's own aspnet_wp.exe
> > >
> > > Thanks,
> > >
> > > Jiange Sun
> > >
> > > Microsoft Developer Support
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > Please reply to newsgroups only.
> > >
> >
> >
>
>

<bubba@cfwebmasters.com> wrote in message
news:Oi0UN6b4DHA.2132@TK2MSFTNGP10.phx.gbl...
> Well I will tell you this right now IIS 5.1 and Windows 2000 IS ONLY
> SOLUTION we could GET TO ACTUALLY WORK!!!!
>
> We wasted 3 months trying to get IIS 6.0 and Windows 2003 Standard Server
to
> actually debug but it would not, nothing we tried worked. We formatted and
> reinstalled with Windows 2000 IIS 5.1 and it work fine out of the gate.
>
>
>
> If we have to try this upgrade again in order to work around a limitation
> that should not have existed to begin with WE WANT CLEARLY DEFINED STEP BY
> STEP instructions from Microsoft because we have already wasted three
months
> trying to get this to work before I WILL NOT have a repeat performance.
>
>
>
> ONE of the many problems we had was when we installed Visual Studio .NET
> 2003 it said they were KNOWN ISSUE using Windows 2003, what exactly are
this
> issues?
>
>
>
> TWO we could not get a single developer the ability to debug we keep
getting
> RPC errors and the boxes were setting right beside each other on the same
> switch.
>
>
>
> Again this is a totally unacceptable answer. I am not happy with this at
> all, these limitation should be made much clearer or better yet should
have
> had a fix in place before the product was publicly released.
>
>
>
> I want clear instructions on setting up this Windows 2003 solution and I
> want the two issue mentioned above addressed. The solutions needs to work
> with Visual Source Safe and its need to be able to debug TERMINAL SERVICES
> users and well and other Remote Users.
>
>
>
> I am sorry to be so harsh but if you had ANY idea what we have been
through
> and TIME we've wasted getting this work you would understand.
>
>
>
> Wayne
>
>
>
>
>
> "Habib Heydarian [MSFT]" <habibh@online.microsoft.com> wrote in message
> news:OA1MIja4DHA.360@TK2MSFTNGP12.phx.gbl...
> > Wayne,
> >
> > It is a known limitation that you can only debug one web application at
a
> > time on IIS 5.1 or below. However, if you have IIS 6.0 (which comes with
> > Window Server 2003), you can take advantage of the app pools feature and
> > setup your web applications so that multiple users can debug different
web
> > applications at the same time.
> >
> > HabibH.
> >
> > <bubba@cfwebmasters.com> wrote in message
> > news:u8q5x7D4DHA.2428@tk2msftngp13.phx.gbl...
> > > Every web sites on the DEV server is in High (Isolated) application
> > > protection (I just double checked to make sure). But I should be able
> to
> > > debug "web application 1" and the other devhead should be able to
debug
> > "web
> > > application 2" since they are not suppose to be sharing the same
> processes
> > > when in High (Isolated) application protection but for some reason I
am
> > > still getting the error and I can not figure out why. None the
> > applications
> > > are not sharing any class file in debug mode (we have a common set of
> > tools
> > > (tis.tools.dll) that we use from site to site).
> > >
> > > However, this may be an issue ALL of the dev web site must use ports
for
> > > example:
> > > "web application 1" is http://dev:8001
> > > "web application 2" is http://dev:8002
> > > "web application 10" is http://dev:8023
> > >
> > > I hope this additional information helps but, to clearly answer your
> > > question below, Yes ALL web sites (including default) on the DEV
server
> > are
> > > running in High (Isolated) Application Protection.
> > >
> > > Thanks
> > >
> > > -Wayne
> > >
> > >
> > >
> > > "Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
> > > news:9QdpayC4DHA.2488@cpmsftngxa07.phx.gbl...
> > > > Hi Wayne,
> > > >
> > > > The error message itself explaines why you failed to attach a
> debugger:
> > > >
> > >
> >
>
****************************************************************************
> > > > ********
> > > > Error while trying to run project: Unable to start debugging on the
> web
> > > > server. A debugger is already attached.
> > > >
> > >
> >
>
****************************************************************************
> > > > ********
> > > >
> > > > As you know, only one debugger can attach a debuggee. You receive
> above
> > > > error when there is alreay a debugger attached and you try to attach
> > > > another debugger to the debuggee (aspnet_wp.exe in this case).
> > > >
> > > > What's the application protection level for the web applicaitons
> you're
> > > > trying to debug? You should be able to debug multiple ASP .NET web
> > > > applicaitons simultaneously if you set their application protection
> > level
> > > > to hign(isolated) because each ASP .NET web application will be
> running
> > in
> > > > it's own aspnet_wp.exe
> > > >
> > > > Thanks,
> > > >
> > > > Jiange Sun
> > > >
> > > > Microsoft Developer Support
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > Please reply to newsgroups only.
> > > >
> > >
> > >
> >
> >
>
>

"Habib Heydarian [MSFT]" <habibh@online.microsoft.com> wrote in message
news:OcU%23nxe4DHA.1592@TK2MSFTNGP10.phx.gbl...
> Wayne,
>
> I'm sorry to hear about the issues that you're having and with your help,
I
> will try to address these. To start with, I will provide the instructions
on
> how to setup IIS 6.0 to debug multiple ASP.NET web applications some time
> later this afternoon. As for the other issues that you mention below, I am
> not aware of these and I would appreciate it if you could provide more
> details.
>
> HabibH.
>
> <bubba@cfwebmasters.com> wrote in message
> news:Oi0UN6b4DHA.2132@TK2MSFTNGP10.phx.gbl...
> > Well I will tell you this right now IIS 5.1 and Windows 2000 IS ONLY
> > SOLUTION we could GET TO ACTUALLY WORK!!!!
> >
> > We wasted 3 months trying to get IIS 6.0 and Windows 2003 Standard
Server
> to
> > actually debug but it would not, nothing we tried worked. We formatted
and
> > reinstalled with Windows 2000 IIS 5.1 and it work fine out of the gate.
> >
> >
> >
> > If we have to try this upgrade again in order to work around a
limitation
> > that should not have existed to begin with WE WANT CLEARLY DEFINED STEP
BY
> > STEP instructions from Microsoft because we have already wasted three
> months
> > trying to get this to work before I WILL NOT have a repeat performance.
> >
> >
> >
> > ONE of the many problems we had was when we installed Visual Studio .NET
> > 2003 it said they were KNOWN ISSUE using Windows 2003, what exactly are
> this
> > issues?
> >
> >
> >
> > TWO we could not get a single developer the ability to debug we keep
> getting
> > RPC errors and the boxes were setting right beside each other on the
same
> > switch.
> >
> >
> >
> > Again this is a totally unacceptable answer. I am not happy with this
at
> > all, these limitation should be made much clearer or better yet should
> have
> > had a fix in place before the product was publicly released.
> >
> >
> >
> > I want clear instructions on setting up this Windows 2003 solution and I
> > want the two issue mentioned above addressed. The solutions needs to
work
> > with Visual Source Safe and its need to be able to debug TERMINAL
SERVICES
> > users and well and other Remote Users.
> >
> >
> >
> > I am sorry to be so harsh but if you had ANY idea what we have been
> through
> > and TIME we've wasted getting this work you would understand.
> >
> >
> >
> > Wayne
> >
> >
> >
> >
> >
> > "Habib Heydarian [MSFT]" <habibh@online.microsoft.com> wrote in message
> > news:OA1MIja4DHA.360@TK2MSFTNGP12.phx.gbl...
> > > Wayne,
> > >
> > > It is a known limitation that you can only debug one web application
at
> a
> > > time on IIS 5.1 or below. However, if you have IIS 6.0 (which comes
with
> > > Window Server 2003), you can take advantage of the app pools feature
and
> > > setup your web applications so that multiple users can debug different
> web
> > > applications at the same time.
> > >
> > > HabibH.
> > >
> > > <bubba@cfwebmasters.com> wrote in message
> > > news:u8q5x7D4DHA.2428@tk2msftngp13.phx.gbl...
> > > > Every web sites on the DEV server is in High (Isolated) application
> > > > protection (I just double checked to make sure). But I should be
able
> > to
> > > > debug "web application 1" and the other devhead should be able to
> debug
> > > "web
> > > > application 2" since they are not suppose to be sharing the same
> > processes
> > > > when in High (Isolated) application protection but for some reason I
> am
> > > > still getting the error and I can not figure out why. None the
> > > applications
> > > > are not sharing any class file in debug mode (we have a common set
of
> > > tools
> > > > (tis.tools.dll) that we use from site to site).
> > > >
> > > > However, this may be an issue ALL of the dev web site must use ports
> for
> > > > example:
> > > > "web application 1" is http://dev:8001
> > > > "web application 2" is http://dev:8002
> > > > "web application 10" is http://dev:8023
> > > >
> > > > I hope this additional information helps but, to clearly answer your
> > > > question below, Yes ALL web sites (including default) on the DEV
> server
> > > are
> > > > running in High (Isolated) Application Protection.
> > > >
> > > > Thanks
> > > >
> > > > -Wayne
> > > >
> > > >
> > > >
> > > > "Jiange Sun [MSFT]" <jianges@online.microsoft.com> wrote in message
> > > > news:9QdpayC4DHA.2488@cpmsftngxa07.phx.gbl...
> > > > > Hi Wayne,
> > > > >
> > > > > The error message itself explaines why you failed to attach a
> > debugger:
> > > > >
> > > >
> > >
> >
>
****************************************************************************
> > > > > ********
> > > > > Error while trying to run project: Unable to start debugging on
the
> > web
> > > > > server. A debugger is already attached.
> > > > >
> > > >
> > >
> >
>
****************************************************************************
> > > > > ********
> > > > >
> > > > > As you know, only one debugger can attach a debuggee. You receive
> > above
> > > > > error when there is alreay a debugger attached and you try to
attach
> > > > > another debugger to the debuggee (aspnet_wp.exe in this case).
> > > > >
> > > > > What's the application protection level for the web applicaitons
> > you're
> > > > > trying to debug? You should be able to debug multiple ASP .NET web
> > > > > applicaitons simultaneously if you set their application
protection
> > > level
> > > > > to hign(isolated) because each ASP .NET web application will be
> > running
> > > in
> > > > > it's own aspnet_wp.exe
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jiange Sun
> > > > >
> > > > > Microsoft Developer Support
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > Please reply to newsgroups only.
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>