Hi, Neils,
In this case, I agree with you. The log4net has been found. It is in the
right directory, namely, \bin where the other dlls are.

It is not like what Ben said.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 10, 2004 12:02 PM
To: [email protected]
Subject: RE: Access is denied: 'log4net'

Wouldn't that throw a FileNotFoundException?

-----Original Message-----
From: Benjamin Peikes [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 10, 2004 1:50 PM
To: Log4NET User
Subject: RE: Access is denied: 'log4net'


Actually, it looks like log4net is not in a directory where the server
can
find it. Might want to ask your ISP where it should go.

Benjamin Peikes 
Gargoyle Strategic Investments 
201-227-2209 





From: Mario Gutierrez [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 10, 2004 2:38 PM
To: 'Log4NET User'
Subject: RE: Access is denied: 'log4net'


ASPNET user  needs R/W/Create permissions to the directory where log4net
writes its log files. If it's a network share you'lll need to use
impersonation.

-----Original Message-----
From: Linda Wang (IT) [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 10, 2004 11:32 AM
To: [email protected]
Subject: Access is denied: 'log4net'



HI, I am using log4net in my web application. It works fine in my local
development machine.
But after I deployed to a host server, log4net can not be loaded when a
page
referring to it has been called. I got this error shown as below. This
hosting server is paid shared one. Any clues?

Thanks,
Linda
Server Error in '/' Application. 



Access is denied: 'log4net'. 
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code. 

Exception Details: System.IO.FileLoadException: Access is denied:
'log4net'.

Source Error: 
 
[No relevant source lines]



Source File: lltnzgya.0.cs    Line: 0 

Assembly Load Trace: The following information can be helpful to
determine
why the assembly 'log4net' could not be loaded.


Reply via email to