This Is a Cryptic Problem
I've noticed that if you put the World.Application object on a web that is password protected using NT authentication (right click on your website in IIS and set a user and pass for your site, it doesn't matter what)
If you enter your administrator username and password in the user/pass dialog box that your webpage presents you, you shouldn't have a problem creating the object.
This is what I've been doing to debug, but when it comes time for me to put my world.application up on the web --- I can't be giving out my admin user and pass =p
just like you I went into dcomcnfg with not a clue as to what it did just like microsoft's KB article explained:
http://support.microsoft.com/support.../Q198/4/32.ASP
This is very cryptic, the summary says that this is 'by design'
So, why would this be by design?? ***??
If this is by design, than how would you make a world.application type object without having to go through that hassle (by design) and with ALL the books written about VB and COM and ASP there HAS to be an answer to this.
If someone had simply taken the time to put a link on that KB article to a source to explain how NOT to encounter this problem, it would have made our lives easier...
Well, I'm done venting
Have you found an answer to this?? and if so, what'd you do??
Thanks for your time
-Brad