ASP with COM+

[GoTerps88]

I needed to create a component that can be used by both ASP and ASP.NET at the same time. I originally created a COM Interop assembly, but I don't believe that's accessible by ASP.NET. I then created a COM+ assembly. I successfully referenced this locally in both in ASP and ASP.NET.

However, I started having problems when I deployed this to a webserver on the network. I used regsvcs to register the component on the webserver. That ran successfully. I verified the entry for this component in the registry, so I am assuming it registered properly.

When I accessed this from ASP.NET everything was kosher. But when I accessed this component via ASP, I received a 'cannot create object' when I call the component from Server.CreateObject("..."). I had COM Visible = true specified in the AssemblyInfo file. Again, this identical dll works locally but throws an error when I try to access this via ASP on the development webserver. I have specified full trust on the entire virtual directory folder for the localintranet code group.

Any pointers in the right direction will be much appreciated.

 

[Sheco]

Try just making a little VBS file that creates and then destroys the object and see if you can run that without error while logged into the console of the server (remote desktop/terminal services is fine.) This will just let if you know if it can be created with plain [tt]Set o = CreateObject("foo.bar")[/tt]

Now if that works use the IIS Admin and temporarily change the security for your ASP so that it doesnt use anonymous access, just integrated security. Then request the page using your browser and it should prompt for credentials to use instead of the default local IUSR_<MachineName> account. Give it the same credentials you used to log into the console. It might not prompt if you are using IE without high security and the server machine is in the same branch of the Active Directory as your client browser box.

 

[GoTerps88]

I think the way they have it set up on the web server is that they are running IIS under a default account, not the IUSR_Machine name. It's definitely not anonymous access.

Would that change at all what you just suggested?