Thread View: comp.lang.basic.visual.database
6 messages
6 total messages
Started by Ingrid van Vliet
Thu, 25 Oct 2001 08:42
Debugging in VB - IIS 5.0
Author: Ingrid van Vliet
Date: Thu, 25 Oct 2001 08:42
Date: Thu, 25 Oct 2001 08:42
16 lines
2091 bytes
2091 bytes
I have just upgraded my server to WIN2000 and IIS 5.0. After that I can run my components (DLL) in ASP but I can't debug them anymore. The way I used to debug them in NT 4 and IIS 4 : OPen the component in VB, press the start button and set some breakpoints and load my ASP file calling the component. This worked fine. When I try to do the same in WIN2000 and IIS 5.0 I can't even get my asp file to run. I get a http 500 - internal server error. Anyone out there who can help ? Thanks in advance ! Ingrid Netjob
Re: Debugging in VB - IIS 5.0
Author: Trevor Benedict R
Date: Thu, 25 Oct 2001 10:58
Date: Thu, 25 Oct 2001 10:58
41 lines
2893 bytes
2893 bytes
Hi Ingrid, You may have to run DCOMCNFG.Exe and then click on Default Security Tab. In the default access Permissions, click on the Edit Default button, and then click on the Add button and add the IUSR_MachineName account and click on OK. You'll be able to debug you VB Code. There's 2 problems here. 1. Your MSAgents will stop working. 2. When you right click on hyperlink on IE. You cannot open them in a new window. If any of you have a solution for this kindly let me know. After you remove the permission from DCOMcnfg everything will work normally, but the debuggin part. Regards Trevor Benedict R Software Engineer Mascot Malaysia Sdn Bhd "Ingrid van Vliet" <iv.vliet@netjob.dk> wrote in message news:mgQB7.39$lk7.1096@news.get2net.dk... | I have just upgraded my server to WIN2000 and IIS 5.0. After that I can run | my components (DLL) in ASP but I can't debug them anymore. | | The way I used to debug them in NT 4 and IIS 4 : OPen the component in VB, | press the start button and set some breakpoints and load my ASP file calling | the component. This worked fine. | | When I try to do the same in WIN2000 and IIS 5.0 I can't even get my asp | file to run. I get a http 500 - internal server error. | | Anyone out there who can help ? | | Thanks in advance ! | | Ingrid | Netjob | | | |
Re: Debugging in VB - IIS 5.0
Author: Ingrid van Vliet
Date: Thu, 25 Oct 2001 13:23
Date: Thu, 25 Oct 2001 13:23
74 lines
3598 bytes
3598 bytes
Hi Trevor Thanks for your mail !You are right, I can use the debugger when I have changed the default security. And when I do that I get the problems you mention: 1. Your MSAgents will stop working. 2. When you right click on hyperlink on IE. You cannot open them in a new window. If any of you have a solution for this So I am also very interested to hear how to solve that !! Best regards Ingrid Netjob "Trevor Benedict R" <*trevor_benz*@yahoo.com> wrote in message news:OBS7qQUXBHA.2020@tkmsftngp07... > Hi Ingrid, > You may have to run DCOMCNFG.Exe and then click on Default Security Tab. In the default access Permissions, click on the > Edit Default button, and then click on the Add button and add the IUSR_MachineName account and click on OK. You'll be > able to debug you VB Code. > > There's 2 problems here. > 1. Your MSAgents will stop working. > 2. When you right click on hyperlink on IE. You cannot open them in a new window. If any of you have a solution for this > kindly let me know. > > After you remove the permission from DCOMcnfg everything will work normally, but the debuggin part. > > > Regards > > Trevor Benedict R > Software Engineer > Mascot Malaysia Sdn Bhd > > > "Ingrid van Vliet" <iv.vliet@netjob.dk> wrote in message news:mgQB7.39$lk7.1096@news.get2net.dk... > | I have just upgraded my server to WIN2000 and IIS 5.0. After that I can run > | my components (DLL) in ASP but I can't debug them anymore. > | > | The way I used to debug them in NT 4 and IIS 4 : OPen the component in VB, > | press the start button and set some breakpoints and load my ASP file calling > | the component. This worked fine. > | > | When I try to do the same in WIN2000 and IIS 5.0 I can't even get my asp > | file to run. I get a http 500 - internal server error. > | > | Anyone out there who can help ? > | > | Thanks in advance ! > | > | Ingrid > | Netjob > | > | > | > | >
Re: Debugging in VB - IIS 5.0
Author: White Lightning - [?]
Date: Thu, 29 Nov 2001 18:28
Date: Thu, 29 Nov 2001 18:28
87 lines
3929 bytes
3929 bytes
I know this is a month late, but if you can't right click on a link in IE, and click Open in New Window, go to a command prompt, go to your system32 directory, and type the following line. It should work again, once you restart IE. regsvr32 urlmon.dll That should do it for ya. :) On Thu, 25 Oct 2001 15:23:37 +0200, "Ingrid van Vliet" <iv.vliet@netjob.dk> wrote: >Hi Trevor > >Thanks for your mail !You are right, I can use the debugger when I have >changed the default security. And when I do that I get the problems you >mention: > > 1. Your MSAgents will stop working. > 2. When you right click on hyperlink on IE. You cannot open them in a new >window. If any of you have a solution for this > >So I am also very interested to hear how to solve that !! > >Best regards >Ingrid >Netjob > > > > > > > >"Trevor Benedict R" <*trevor_benz*@yahoo.com> wrote in message >news:OBS7qQUXBHA.2020@tkmsftngp07... >> Hi Ingrid, >> You may have to run DCOMCNFG.Exe and then click on Default Security Tab. >In the default access Permissions, click on the >> Edit Default button, and then click on the Add button and add the >IUSR_MachineName account and click on OK. You'll be >> able to debug you VB Code. >> >> There's 2 problems here. >> 1. Your MSAgents will stop working. >> 2. When you right click on hyperlink on IE. You cannot open them in a new >window. If any of you have a solution for this >> kindly let me know. >> >> After you remove the permission from DCOMcnfg everything will work >normally, but the debuggin part. >> >> >> Regards >> >> Trevor Benedict R >> Software Engineer >> Mascot Malaysia Sdn Bhd >> >> >> "Ingrid van Vliet" <iv.vliet@netjob.dk> wrote in message >news:mgQB7.39$lk7.1096@news.get2net.dk... >> | I have just upgraded my server to WIN2000 and IIS 5.0. After that I can >run >> | my components (DLL) in ASP but I can't debug them anymore. >> | >> | The way I used to debug them in NT 4 and IIS 4 : OPen the component in >VB, >> | press the start button and set some breakpoints and load my ASP file >calling >> | the component. This worked fine. >> | >> | When I try to do the same in WIN2000 and IIS 5.0 I can't even get my asp >> | file to run. I get a http 500 - internal server error. >> | >> | Anyone out there who can help ? >> | >> | Thanks in advance ! >> | >> | Ingrid >> | Netjob >> | >> | >> | >> | >> >
Re: Debugging in VB - IIS 5.0
Author: Trevor Benedict R
Date: Fri, 30 Nov 2001 02:11
Date: Fri, 30 Nov 2001 02:11
9 lines
2015 bytes
2015 bytes
First of all, THANKS for replying. Good work should always be appreciated. Are there any specific reasons as to why this is so and are there any security concerns using this method. Recently we had this Virus outbreak and it's literally created havoc. Regards Trevor Benedict R Software Engineer Mascot Malaysia Sdn Bhd
Re: Debugging in VB - IIS 5.0
Author: Andrew Shafer
Date: Fri, 30 Nov 2001 02:36
Date: Fri, 30 Nov 2001 02:36
22 lines
2779 bytes
2779 bytes
No security concerns. It just fixes how IE looks at links, like it normally should. -- ---------------------------- Andrew Shafer, Certified Internet Explorer Master Do you want to see the Matrix? http://www.students.k12.sd.us/s2997583 ---------------------------- "Trevor Benedict R" <trevornews@yahoo.com> wrote in message news:#HO1HSUeBHA.1988@tkmsftngp02... First of all, THANKS for replying. Good work should always be appreciated. Are there any specific reasons as to why this is so and are there any security concerns using this method. Recently we had this Virus outbreak and it's literally created havoc. Regards Trevor Benedict R Software Engineer Mascot Malaysia Sdn Bhd
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads