Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2555
  • Last Modified:

Exchange 2013 SP1 - Event Error Code 6003 - Unable to access path for logs

Folks:

I have been searching Experts Exchange and the Web about this error and everyone says to add it to the "Environment Variable" but doesn't tell you where to add the path.

I am getting this error over and over in my Event Viewer:

SmtpSendProtocolLogs: Failed to create the log directory: E:\Mailbox Database Logs\Company\Protocol Log\Send because of the error: Access to the path 'E:\Mailbox Database Logs\' is denied.. Logs will not be generated until the problem is corrected.

For pretty much everything that is going to this location (regardless if it is a Protocol Log or not, it is showing up in the Event Viewer.

So I need to ask where do you I add all of these variables for these logs?
What type of permission should these folders have so that Exchange can write to them?
0
JustinBMak
Asked:
JustinBMak
1 Solution
 
MaheshArchitectCommented:
Since the path mentioned above is not default one, you need to create folder manually at above location

That will help hopefully

Mahesh.
0
 
JustinBMakAuthor Commented:
Mahesh:

The location is created. I created everything BEFORE making the changes via PowerShell.

window to show the folder is already and has been created
0
 
Adam BrownSr Solutions ArchitectCommented:
The Exchange Servers AD group would need to be granted read and write permissions on the folder if it isn't already located on an Exchange server, and possibly if it is (since those logs may be written by another exchange server).
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
JustinBMakAuthor Commented:
I have checked and the AD Group called "Exchange Servers" has Read/Write access at the root (Mailbox Database Logs) and the children below are set to get their permission from the parent.

Any other thoughts/ideas?
0
 
R--RCommented:
Are you able to create a directory and try to create a file under the directory.
Verify if you have organization management permission for the user from which you are upgrading SP1.

reference link http://technet.microsoft.com/en-us/library/dd638213.aspx
0
 
Md. MojahidCommented:
http://technet.microsoft.com/en-us/library/cc727009(v=ws.10).aspx

and may have to fixed by Microsoft Tech support.
0
 
JustinBMakAuthor Commented:
R--R:

Yes, I can create a file in the directory:

Creating a file in that directory.
0
 
JustinBMakAuthor Commented:
Md. Mojahid:

I did contact Microsoft, they suggested that "Authenticated Users" has Read/Write access to the folders.

So I added that right yesterday (last night) and still today I see:
Which is why I am turning to Experts-Exchange for assistance.

Event Error 6003 - Exchange 2013
0
 
MaheshArchitectCommented:
Can you please try by changing log location to some else location \ Drive ?
0
 
JustinBMakAuthor Commented:
Mahesh:

I have moved it over to the "C:\" Drive and waiting for any errors, which generally take an hour.

I will post if it continues to happen.
0
 
JustinBMakAuthor Commented:
So of course it works just fine. I have checked the permissions between the folder on where it WAS (C:\Temp) to where I wanted it to be, I didn't see a difference. So I moved the folder (again) because C: only have a 40GB Partition and then (just for the heck of it) added "Everyone" to the Security ACL and now Exchange writes to the folder.

Obviously this isn't best practice, so does any one have any other ideas on what the permissions should be? I have contacted Microsoft and they say to add the security group "Authenticated Users" however the guy I spoke to that was on the phone was helping me on a different issue and honestly didn't know the answer to my question. So since it didn't work, it's obviously something else.

Does anyone else have any other idea?
0
 
MaheshArchitectCommented:
If everyone group causing your custom path is working, its not good

Instead please try below

Grant system account and Exchange Servers group full control on folder (I hope its already there) and grant folder ownership to Exchange servers group and then try

Mahesh.
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now