Just to make sure, but you did register them correctly, right? I find it's sometimes worth reregistering the COM component just to be sure. Also, if you're running IIS6, check the application pool to make sure what account you're running under. By default it's Network Service.
Erick > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Mike Andrews > Sent: Wednesday, October 26, 2005 8:06 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: [ADVANCED-DOTNET] Trouble creating COM components in > Web application... > > Guys, > I'm having a lot of trouble creating a COM component in an > ASP.NET<http://ASP.NET>Web application. The COM object was > created with VB6. And the only exception I get is that the > ActiveX component can't be created, but with no other help as > to the root cause. I tried (just for testing) adding the > ASPNET machine account to the administrators group to see if > that made any difference, but to no avail (unless I need to > reboot my machine to get it work). > Is it possible to turn on some kind of auditing to find out > what exactly is causing the failure? > I'm just having a hard time with this one. None of these COM > components can be rewritten, so I'm stuck with trying to call them. > The odd thing is that I can create a webservice (which > ultimately is what will call the COM component) and that > works when I run it from the test harness that VS provides. > However, when I call the webservice from the ASP.NET > <http://ASP.NET> Web application, it fails. > I'm at a loss here. > Any help would be appreciated. > Thanks, > Mike > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
