Logs no longer accessible after installing build 6964
Problem reported by DarrenL - January 29 at 1:58 AM
Resolved
Hi - upgraded to release 6964 on Sunday - now can’t access or search for log files via Troubleshooting / View log Files:

‘Access to the path 'c:\SmarterMail\Logs\2019.01.29-delivery.log' is denied.”

Any ideas to fix?

9 Replies

Reply to Thread
0
Robert Emmett Replied
Employee Post
Darren, can you verify that that particular file does exist on your server and that permissions are configured correctly?
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
DarrenL Replied
Files are definitely there and can be accessed from command line / text file reader.
Could you kindly confirm what the file permissions should be or point me to a kb (did a search in the kb but couldn’t find anything so far!).

Cheers.
0
Alex Clarke Replied
Marked As Resolution
I had the same problem after my upgrade to 17.

You'll need to grant Full control to the Logs folder (replacing all child object permissions) for NETWORK SERVICE.
0
Jade D Replied
Never grant Full control to anything on windows...
Modify permissions are sufficient



0
Alex Clarke Replied
I've always been advised to grant full control by ST, but I guess modify permissions are safer.
0
DarrenL Replied
Perfect - fixed.  Many thanks Alex & Jade.
1
Jade D Replied
@ Alex - no problem at all
The age old battle of Dev's vs Sys Admins
Granting full permission allows to the user to take ownership of those files and remove permissions for other users.
If your server / SM gets hacked, you'll be stuck in a situation where you're unable to do anything with those files or folders. 
Never grant full permissions and never set an application pool identity to one that has administrative rights - these are two common mistakes that developers tend to make :)
0
Alex Clarke Replied
Thanks for the recommendations Jade!
0
Mark Wilson Replied
I was having this same issue on 16.x and once I added the SYSTEM SERVICE and gave it Modify rights, my issue was resolved.

Reply to Thread