Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / COM / February 2005



Tip: Looking for answers? Try searching our database.

VB Component Problem - ASP error 80020009 Permission denied

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andreas.Bretl - 12 May 2004 10:04 GMT
Hi there,

we are running a com dll created with vb6 together with a iis 5 and ASP on a
win2k server. This system is productive and works fine at the moment. But
now we want to migrate the intranet server to a win2003 server with iis 6.

After installing my dll and the PDFlib dll (referenced within my dll)  i get
the asp error '80020009' / Permission denied in Line XXX (where line XXX
stands for the line where the object is created -> set obj =
server.createobject("myobj.LBO")) on some sites. But the real strange thing
about this issue is that some sites using this dll work fine and others
cause errors. But after an error is thrown by one of the errornous aspfiles
even the ones that worked before throw errors.

I have looked through google groups and found out that i have to grant
filesystem permissions to iwam_<machinename> and iuser_<machinename>. I have
tried this, I even granted full control to everyone in the folders where the
both dlls are located. But i keep on getting the error as described above!
Are there any other folders where i need to grant access?

The dll runs in an iis6 applicationpool. Are there any settings I have to
change?

I even installed vb6 to this machine to test the dll, which works fine and
to recompile it with works, too

To test all the other referenced Objects within the dll I wrote a small test
file that instances all used "thirdparty" objects and calls some functions.
Even this works fine. Besides the PDFLib i am using
scripting.filesystemobject, scriptingContext, CDONTS and ADO. The funny
thing about this is that we have another custom dll running on both servers,
which is referencing the same objects except PDFLib and it works without any
problems. It did not need any customization of the filesystem userrights!
But PDFLIB is running properly from vb6 and from the testfile.

I hope somebody can help me.

Thanks a lot in advance,

Andreas Bretl
bretl@brainlab.com
Vins - 16 May 2004 15:06 GMT
I had the same problem in my windows 2000 server. I Disabled Anonymous Login from IIS Manager for the Folder of the asp and it is working fine now

All the best

Vins
aldiboro(@yahoo.com)
Andreas.Bretl - 17 May 2004 08:08 GMT
Thanks a lot Vins,
That made the job ;)
Everything is working fine now.

Greetings from munich,

Seize the Day

Andreas Bretl
bretl@brainlab.com
Wilson Ten - 22 Feb 2005 04:54 GMT
Dear Anyone,

Good morning to you. I faced that same problem here which require your
advise.

I have asp to call the dll by using Server.CreateObject, and gets the
permission denied. After I have added to the component to the COM+
service, it works fine. May I know why should I add the dll classes to
the COM+? It works fine in my development pc without having to add to
the COM+.

My concern is, I have a class call clsUpload in that dll that handles
file upload from my asp pages. My clsUpload doesnot work at all, cant
even retrieve the form items. But it works in my development pc.

I dont know why, is this related to COM+?

Pls help.

Wilson Ten

> Hi there,
>
[quoted text clipped - 3 lines]
>
> After installing my dll and the PDFlib dll (referenced within my dll)
i get
> the asp error '80020009' / Permission denied in Line XXX (where line XXX
> stands for the line where the object is created -> set obj =
[quoted text clipped - 30 lines]
> Andreas Bretl
> bretl@brainlab.com
Ralph - 24 Feb 2005 13:50 GMT
> Dear Anyone,
>
[quoted text clipped - 16 lines]
>
> Wilson Ten

The five cent answer is simply that it is a matter of security. Due to the
nature of the Net, asp pages must run in an isolated environment, under its
own user, with its own set of permissions and resources. To allow simple
COM/DCOM to operate uncontrolled would allow any object to 'callout' into
the outer world - mayhem and destruction would surely follow. COM+ 'wraps'
interprocess communication and allows the OS to manage and protect its
resources.

The components run OK during development as they are at that time running as
'you' with your permissions and resources. Problems with components that
don't appear to run even when registered with COM+ can usually be traced to
an 'unprotected' resource the component is attempting to access or denied
activity.

hth
-ralph
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.