NLog internal log not working with ASP.Net MVC

Question

I have a problem with NLog for logging its internal logs with this configuration

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  throwExceptions="true"
  internalLogFile="${basedir}/App_Data/NLog.log"
  internalLogLevel="Trace">

   <targets>
      <target name="debug"
              xsi:type="File" 
              fileName="${basedir}/App_Data/Site.log" />
   </targets>

   <rules>
      <logger name="*"
              writeTo="debug" />
   </rules>
</nlog>

The target "debug" is working well, but the internalLogFile is only working if I set it for exemple to "D:/NLog.log".

Any idea why this happening?

Note; the default path is where ever IISExpress is installed. If you specify: InternalLogFile="nLogError.txt". Then (at least on my PC) it will try and write to "C:\Program Files (x86)\IIS Express\nlogExceptions.txt". Which can have permission problems. — OzBob
– OzBob, Commented Apr 14, 2015 at 4:24

Rolf Kristensen · Accepted Answer · 2021-10-12 00:02:01Z

12

You can't use layout renderers ${...} in the internalLogFile property. They are for a target's layout only:

<target layout="${...}" />

Try to use relative path like "..\App_Data\NLog.log"

Update NLog 4.6 enables some simple layouts.

edited Oct 12, 2021 at 0:02

Rolf Kristensen

20.2k2 gold badges59 silver badges87 bronze badges

answered Feb 24, 2012 at 10:57

kolbasov

1,59812 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

JuChom Over a year ago

Thanks for the answer. Relative path are not working, it seems that it needs absolute path.

Neel Over a year ago

you are wrong..i am using ${} in internal logging and it works fine!! @Swell u can use ${..} in internal log file

Neel Over a year ago

internalLogFile="${specialfolder:folder=CommonApplicationData}/Logs/Nlog/${shortdate}/Nlog-Internal.log"

Gonzalo Contento Over a year ago

Very good comment from a NLog collaborator on why this is not a good idea internalLogFile: NLog variables

Tim Abell Over a year ago

for the record the comment mentioned was " 304NotModified commented on 18 Feb 2015 | As answered at Stackoverflow: this isn't possible and also unwanted. The internal logfile should be as stable as possible (a so no fancy features). Also I think thank the internal log should only be used in rare cases."

|

Ed Spencer · Accepted Answer · 2015-05-01 09:40:02Z

5

The internalLogFile attribute needs to be set to an absolute path and the executing assembly needs to have permission to write to that absolute path.

The following worked for me.

Create a folder somewhere - e.g. the route of your c: drive, e.g. c:\logs
Edit the permissions of this folder and give full control to everyone
Set your nlog config: internalLogFile="C:\logs\nlog.txt"

Remember to clean up after yourself and not leave a directory with those sorts of permissions on

answered May 1, 2015 at 9:40

Ed Spencer

4621 gold badge8 silver badges21 bronze badges

1 Comment

Tod Birdsall Over a year ago

Thx for the tip. That worked for me. It appears that .NET Framework requires an absolute path, but ASP.NET Core allows for relative paths.

Rolf Kristensen · Accepted Answer · 2020-11-26 22:27:13Z

1

NLog ver. 4.6 add support for environment-variables like %appdata% or %HOME%, and using these basic layouts in internalLogFile=:

${currentdir}
${basedir}
${tempdir}

NLog ver. 4.7 also adds this:

${processdir}

See also: https://github.com/NLog/NLog/wiki/Internal-Logging

answered Nov 26, 2020 at 22:27

Rolf Kristensen

20.2k2 gold badges59 silver badges87 bronze badges

Comments

Willy · Accepted Answer · 2014-03-28 10:55:45Z

0

from this link I think the path is absolute

answered Mar 28, 2014 at 10:55

Willy

1,7297 gold badges38 silver badges82 bronze badges

Collectives™ on Stack Overflow

NLog internal log not working with ASP.Net MVC

4 Answers 4

7 Comments

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

7 Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related