error '8007045a'

[sunaj]

Hi,

I'm getting "error '8007045a'" when creating an instance of an AxtiveX object on my asp page. The error means that the dll initialisation failed. If I run the exact same code in a VBScript (instead of through the webserver), it works fine. I have given the IWAM and IUSR users permission 'full control' of the dll in question - but this dll links to hundreds of other dll's which I have not been through. Can anybody help me on how to find out extactly where the permission problem arises?

There are no entries in the event logs associated with this problem.

How do I find out on which dll's I should give which rights to which users?

Thanks in advance

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[cmartin75]

Has the user IWAM (or IUSR) permissions to create the ActiveX in the DCOM configuration?

 

[sunaj]

I don't know, the component is not in the list of DCOM applications. Should it be? It does not appear in the list on my own XP either, and here it works fine...

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[cmartin75]

In the event viewer of the server will be some error about it. And It helps you to find the component

 

[sunaj]

Unfortunately (as I wrote in my first post) there are no relevant entries in the event logs.

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[cmartin75]

The dependency walker can help you to find if there's another dll you must install on the server

http://www.dependencywalker.com/

 

[sunaj]

Well the component works fine (as I also wrote in my first post), it's only when I run it through the webserver that it fails.

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[cmartin75]

Only for a test and only for a moment try to give administrator privilegies to the iis user to ensure that the user is the problem

 

[sunaj]

Yes I've tried that and it solves the problem above. However I get a similar error message on an other ActiveX component!
So I would really like to be able to see/debug/monitor extactly where the problem arises...

I've tried FileMon and RegMon, which did not give any additional information. I've also tried Auth Diagnostics 1.0 (

http://www.microsoft.com/downloads/...-4a21-4066-bd22-b931f7572e9a&displaylang=en),

but noting seems to happen when I click the 'Dianostics' button (I used "mstsc /v:server name /console" and am running windows server 2003 R2).

I can't believe that it is that hard to figure out what is going on when you run things through IIS 6.0 - Right now I'm ready to stick Microsoft up where the sun never shines!

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[wvdba]

what you can do is put sectional messages in your code to identify small sections of the code. and see after which message the error occurs. then you can concentrate on the small section of your code.

 

[sunaj]

I know exactly where the error occurs, it's when I create the AxtiveX component.

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[sunaj]

The answer is here:

http://www.microsoft.com/technet/pr...787-982a-478c-b319-e703b270d8ee.mspx?mfr=true

when using the dllhost, the server must run in 'IIS 5.0 isolation mode'.

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'