Published October 8th, 2003 by Jim O'Halloran
Problems debuging VB6 WebClasses under Windows 2000/XP
I’ve had quite a number of problems debugging getting VB6 WebClasees working in the development environment on a new Windows XP box. I’ve documented what I’ve done here so that it can help someone else out in the same situation.
Firstly, whenever I tried to access any file in the project’s Virtual Directory via the brwoser I received a 404 File Not Found error. This wasn’t just restricted to to projects asp page, but the HTML templates, etc as well. The problem seemed to be related to the fact that long file names were used in the projects path (e.g. the source was in “D:\Server Code\WebClass Component”). When VB created the Virutual Directory in the IIS Configuration it changed used “D:\SERVER~!\WebClass Component” as the path, which seemed to cause IIS problems even though the two should be equivelent. In the IIS Manager, right click on the Virtual Directory, select Properties, then Click on the “Browse” button. This will locate the full directory name again. While you’re there it wouldn’t hurt to create a new “Application”, set Script Access to “Scripts and Executables” and Application Protection to “High (Isolated)”. Save these changes and restart IIS. You should now be able to browse to HTML files in this directory, but the WebClass project still may not work.
This could be a DCOM permissions thing, which results in an ASP 0178 error.
Error Type:
Server object, ASP 0178 (0×800A0005)
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
It would appear that under Windows 2000 and XP you need to fiddle with DCOM permissions before you can debug WebClasses. MSKB article 259725 explains how to create a registry file to add VB ASP Debugging into DCOM, and what to permissions to change and why. I set permissions on both the VB ASP Debugging DCOM component AND changed the default permissions as well. This might be overkill, but it does work.
Hpe that helps someone. I did change quite a few other settings in the course of making this work, but these are the ones thart seemed to have fixed the problem for me.
Sup Says
Excellent tip! I was having so much problem with an old application I am supporting. This tip helped out a lot. Thanks.
Jan 8th, 2004 at 8:48 am
Frank Says
I tried Microsoft’s “workaround 1″ described in MSKB article 259725, but that was not enough. You pointed me at the default permissions on the “My Computer” level. I changed these as well, and this did really help.
Jan 25th, 2005 at 2:01 am
John Duncan Says
Hi,
Microsoft was, as usual, no help, but your tips saved the day. Thank you so much.
John
Mar 28th, 2007 at 9:50 am