1,753 questions
Log4net not write log on IIS .net core 6
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 90%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Stefano Ghinassi - NetribeGroup
0
Reputation points
I have two .NET Core 6 services on IIS in two separate application pools. In both, I use Log4Net to log errors. I have given NETWORK DEVICE user permissions on the log directories. The first service logs correctly, but the second one does not. However, if I stop the second application pool and start the service from the command line, it starts logging.
However, no errors are recorded in the event viewer
Windows development | Internet Information Services
Developer technologies | ASP.NET | ASP.NET Core
4,830 questions
{count} votes
-
AgaveJoe 30,126 Reputation points2024-09-20T17:12:33.6066667+00:00 It sounds like your account has write access to the log folder while the application pool identity does not.
-
Stefano Ghinassi - NetribeGroup 0 Reputation points
2024-09-23T05:50:33.3466667+00:00 Tanks Agavejoe for your suggestion, but I have two application pool on the same machine , one write the log and the other do not. I don't think is authorization problem.
The application that don't write the log it's alwaysrunning.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 24%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Sam Wu-MSFT 7,561 Reputation points Microsoft External Staff2024-09-23T08:32:40.0466667+00:00 @Stefano Ghinassi - NetribeGroup
Ensure that the identity of the application pool for the second service is correctly set. By default, it might be set to
ApplicationPoolIdentity, which may not have sufficient permissions.- Go to IIS Manager > Application Pools.
- Right-click on the application pool for the second service and select Advanced Settings.
- Check the Identity under Process Model. If it's
ApplicationPoolIdentity, try changing it to a custom identity orNetworkService.
-
Lex Li 6,037 Reputation points2024-09-23T20:31:31.1066667+00:00 Modern IIS releases no more use
NETWORK SERVICEas default pool identity, so you might have configured the right file system ACL. Alternatively, you might grant IIS_IUSRS group write access on that log folder, which covers all possible IIS application pool identities. -
Stefano Ghinassi - NetribeGroup 0 Reputation points
2024-09-24T06:18:22.1733333+00:00 Hello everyone, today I checked the log again and I saw that, after the weekend, the application pool started writing it without me making any changes.
Sign in to comment
Sign in to answer