Web page calling COM+ DLL

[Griff]

I have a web server that has a COM+ DLL. This is successfully called by a
web page running on that server.

I exported the COM+ package (as an MSI and NOT as a proxy stub) and imported
it onto a new machine. I set up the web application in (I believe) an
identical fashion. When I run the ASP page it errors - permission denied;
can not create object.

Things I have checked:
1 - the COM+ package runs under the LOCAL ADMINISTRATOR account (same as on
the other server).
2 - the NTFS permissions on the DLL (sitting in C:\Program Files\ComPlus
Applications\{xxxxxx} are identical on both machines
3 - the IIS security and NTFS permissions on the script are identical
4 - I've ensured that the DLL is registered correctly (using regsvr32)

I'm at a loss to see what else could be the problem. The COM+ DLL only
references standard Windows components that exist on the server.

Any suggestions please?

Thanks

Griff

[Mark Yudkin]

I know you said "3 - the IIS security and NTFS permissions on the script are
identical", but nevertheless verify that the IIS security really is
identical. There are a huge number of places things have to be set up.
Enabling full IIS tracing to see where the problem may be.

"Griff" <Ho*****@The.Moon> wrote in message
news:uN****************@tk2msftngp13.phx.gbl...

I have a web server that has a COM+ DLL. This is successfully called by a
web page running on that server.

I exported the COM+ package (as an MSI and NOT as a proxy stub) and
imported it onto a new machine. I set up the web application in (I
believe) an identical fashion. When I run the ASP page it errors -
permission denied; can not create object.

Things I have checked:
1 - the COM+ package runs under the LOCAL ADMINISTRATOR account (same as
on the other server).
2 - the NTFS permissions on the DLL (sitting in C:\Program Files\ComPlus
Applications\{xxxxxx} are identical on both machines
3 - the IIS security and NTFS permissions on the script are identical
4 - I've ensured that the DLL is registered correctly (using regsvr32)

I'm at a loss to see what else could be the problem. The COM+ DLL only
references standard Windows components that exist on the server.

Any suggestions please?

Thanks

Griff

[AL_LONGO]

You will need to check the "launch and activation" permissions in your DCOM
application's properties in the Component Services. You may have to check the
"access permissions" as well. Make sure that the IUSR_xxxx has access to
this component so that it can launch/run this app.

Hope this helps,
AL
"Mark Yudkin" wrote:

I know you said "3 - the IIS security and NTFS permissions on the script are
identical", but nevertheless verify that the IIS security really is
identical. There are a huge number of places things have to be set up.
Enabling full IIS tracing to see where the problem may be.

"Griff" <Ho*****@The.Moon> wrote in message
news:uN****************@tk2msftngp13.phx.gbl...

I have a web server that has a COM+ DLL. This is successfully called by a
web page running on that server.

I exported the COM+ package (as an MSI and NOT as a proxy stub) and
imported it onto a new machine. I set up the web application in (I
believe) an identical fashion. When I run the ASP page it errors -
permission denied; can not create object.

Things I have checked:
1 - the COM+ package runs under the LOCAL ADMINISTRATOR account (same as
on the other server).
2 - the NTFS permissions on the DLL (sitting in C:\Program Files\ComPlus
Applications\{xxxxxx} are identical on both machines
3 - the IIS security and NTFS permissions on the script are identical
4 - I've ensured that the DLL is registered correctly (using regsvr32)

I'm at a loss to see what else could be the problem. The COM+ DLL only
references standard Windows components that exist on the server.

Any suggestions please?

Thanks

Griff