Groups | Blog | Home
all groups > dotnet interop > may 2005 >

dotnet interop : call dotnet dll from asp object doesn't support this property or method



koenappeltans NO[at]SPAM gmail.com
5/12/2005 8:06:13 AM
Hi,

I wrote a simple dotnet class that I want to access from classic asp.

After building the dll I registered him with regasm and included him in
the gac.

On my machine (Win XP service pack 2, IIS 5.1) it works perfect to
access this class from classical asp.
I do a CreateObject, call the method and everything works.

When I try to do the same on the webserver (Windows 2000, IIS 5.0) it
fails.
The CreateObject call works, there is no error on that line, but when I
try to call a method he gives the error : 'Object doesn't support this
property or method.'

Next I made a testscript on the webserver so a simple .vbs file where I
make the same calls and this works perfect. So it should have someting
to do with the internet-environment that tries to call the method.

Next, I tried to set the application protection to low. Then it
suddenly works without problems. When I put the application protection
to medium (pooled) it doesn't work anymore. On my development server I
also have the application protection on medium (pooled) and there is no
problem at all.

I've searched a lot allready in groups and found some similar problems
but the solutions provided don't work for me. I also tried to make a
serviced component of the dll, but that still gives the same error.

I guess it has something to do with security issues, I also tried to
put the IIS_USR and the IWAM user in the administration group but that
doesn't solve the problem. Sot my inspiration is running dry at the
moment.

If anyone has a clue how to solve the problem, or can point into a
certain direction, please help. If there is a better group to post a
problem like this, notify me too.

Tnx in advance!

Koen
one
5/12/2005 4:50:03 PM
just briefly, what have you try? Like restarting IIS...

[quoted text, click to view]
koenappeltans NO[at]SPAM gmail.com
5/17/2005 2:08:02 AM

Restarting IIS I haven't tried because it's a production-server. I also
think chances are small that would work. If I put the
application-protection on low then it works so I don't think restarting
IIS will help to let it work on Medium(pooled) protection).

I've tried to change a whole bunch of security settings, cause I
suppose it's a security issue somewhere. I also tried to make it a
COM-component and let it run under component services, but without any
success.

Do you have any suggestions what I could try??

Regards,

Koen Appeltans

one schreef:
[quoted text, click to view]
AddThis Social Bookmark Button