Previous Next

• 09-19-2007, 11:22 AM

  Nainoo Joined on 03-21-2006, 2:10 PM Posts 3 Nainoo

  Debug VB 6 COM component calling from classic ASP in Windows 2003 Reply Contact Hello, I have just upgarded my OS from W2k to Windows 2003 Standard Server. I have reconfigured all my website including classic ASP and the ASP.NET ones. Initially I had a problem with running my classic ASP web site but that has been sorted out by getting answers on the internet. Well, I want to run my classic ASP website and debug my COM component in VB 6 IDE in this new OS (Windows 2003 Server) just like I used to do it on Windows 2000. I have spent much time on the internet but couldn't find any thing working. Can anyone please help me to get rid of this issue as it may stop us our migration to Windows 2003 server as a developer machine? Regards, Nainoo

• 09-20-2007, 12:01 AM

  In reply to

  steve schofield Joined on 06-10-2002, 4:54 PM MI Posts 2,213 steve schofield

  Re: Debug VB 6 COM component calling from classic ASP in Windows 2003 Reply Contact It has been many moons since I debugged in VB6 IDE, if you can post the errors you are getting, or obvious things, others might be able to help out.  Have you tried to enable debugging on the client side?  Are you logged into the dev machine as an admin?  Are there specific global policies being forced on the machine?  It can be a variety of things contributing to the error.  I would ensure you have all the tools and various components on your w2k3 box as you did in w2k.  Hope that helps provide some direction. Steve Schofield Windows Server MVP - IIS MCTS - Windows Hosting http://weblogs.asp.net/steveschofield http://www.iislogs.com http://www.orcsweb.com/ Managed Hosting Solutions #1 in Service and Support

• 09-20-2007, 5:32 AM

  In reply to

  Nainoo Joined on 03-21-2006, 2:10 PM Posts 3 Nainoo

  Re: Debug VB 6 COM component calling from classic ASP in Windows 2003 Reply Contact Actually, when I run the COM DLL within the VB6 IDE using CTRL+F5 and then call my classic ASP page to use this component, it returns an error “Object required”. To me it is not picking up the COM object while running from within the IDE unlike in Windows 2000 server that we are using to build our classic ASP solutions. However, when I build the same code (and register it) then my ASP page works. I don’t really know what is causing the problem but I guess is it something to do with the difference of W2K IIS and W2K3 II6 in handling/executing the ASP page and probably ASP context issue or something. Really no idea!

• 09-20-2007, 7:42 AM

  In reply to

  Nainoo Joined on 03-21-2006, 2:10 PM Posts 3 Nainoo

  Re: Debug VB 6 COM component calling from classic ASP in Windows 2003 Reply Contact Hi, I’m very glad. I have actually managed to solve this issue. Basically, it was related to some sort of access permission as guessed earlier. Solution: I have resolved it by giving Internet Guest Account (MachineName\IUSR_MachineName) Access Permissions and Launch and Activation Permissions to this user by using MMC and going to Component Services -> Computers -> My Computer Properties -> COM Security tab.

  Tags: Classical ASPdllvbASPerroriisdebug COM

• 09-20-2007, 8:20 AM

  In reply to

  steve schofield Joined on 06-10-2002, 4:54 PM MI Posts 2,213 steve schofield	Re: Debug VB 6 COM component calling from classic ASP in Windows 2003 Reply Contact Thanks for posting the resolution.   This should help others in the future.  Steve Schofield Windows Server MVP - IIS MCTS - Windows Hosting http://weblogs.asp.net/steveschofield http://www.iislogs.com http://www.orcsweb.com/ Managed Hosting Solutions #1 in Service and Support