If it’s any help to anyone who might
be checking on this for me, I have determined that the exception is due to the AppDomain.CurrentDomain.BaseDirectory
returning an URL formatted string (i.e. http://server/AppName). Apparently the colon
is not appreciated by the FileInfo object in log4net.Config.DOMConfiguratorAttribute.
Is there any other way to configure Log4Net so that the AppDomain.CurrentDomain.BaseDirectory won’t be taken into account? Or any other ideas?
Thanks again,
Josh Hawthorne
jhawthorne@xxxxxxxxxxxx
From: Josh Hawthorne
[mailto:jhawthorne@xxxxxxxxxxxx]
Sent: Wednesday, February 09, 2005
1:39 PM
To:
log4net-user@xxxxxxxxxxxxxxxxxx
Subject: URI formats are not
supported
Hello all,
First posting here so please be gentle. J
I’m hoping this is a known issue and has an easy fix. Although
I’ve found someone else having this issue by searching the net, their
solution was to remove Log4Net. That’s not what I’m hoping for. My
previous experience was with Log4J so please excuse any blatant ignorance
I’m working on resolving. J
General info first:
Version: 1.2.0-beta8
Assembly: exe launched via ASP.Net No-Touch Deploy
Runtime: .Net
Issue: I get the following exception when I try to run my
app from a No-Touch Deploy from IIS.
// Begin Exception
An unhandled exception of type 'System.ArgumentException'
occurred in mscorlib.dll
Additional information: URI formats are not supported.
// End Exception
This same application runs fine when directly executed on
the workstation as well as directly executed on the server. I have played
around with permissions on the workstation to grant full privileges to the app,
and still get the same exception. The exception is occurring when I try to
initialize a logger.
Code:
private static
readonly log4net.ILog log =
log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);
Thanks in advance for any help you might be able to provide.
Regards,
Josh Hawthorne
jhawthorne@xxxxxxxxxxxx
