asked on Getting Event 17 in Event Log for Exchange Server
Hi,
I noticed in the event logs on one of our Exchange 2010 servers that that we were getting an error for Event ID: 17. I checked on google but I haven't really found a solution to the problem not sure if anybody has any ideas. This is a new Exchange 2010 server it's been running for about 2 weeks now. I've included a screenshot
Solution 1
Solution 2
Exchange1.jpg
I noticed in the event logs on one of our Exchange 2010 servers that that we were getting an error for Event ID: 17. I checked on google but I haven't really found a solution to the problem not sure if anybody has any ideas. This is a new Exchange 2010 server it's been running for about 2 weeks now. I've included a screenshot
Solution 1
Solution 2
Exchange1.jpg
ExchangeMicrosoft IIS Web Server
Last Comment
Saif Shaikh
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hi,
Just so you know the Event ID mentioned a server (computer object) not a user. I erased this out of the screenshot sorry I should have made this clearer.
Just so you know the Event ID mentioned a server (computer object) not a user. I erased this out of the screenshot sorry I should have made this clearer.
Please add the server (computer object) to Organisation Management Group and check it again.
This issue may be caused by the improper RBAC permission, please run below command to double check:
Get-Mailbox Identity | FL RoleAssignmentPolicy
Get-RoleAssignmentPolicy Identiy | FL Name,AssignedRole
In Active Directory Users and Computers you will find a new container called Microsoft exchange Security Groups. If you locate the group called Exchange Organisation Administrators and add your user in to this group it should resolve it.
http://exchangetechexperts.com/process-w3wp-exe-pid-25480-rbac-authorization-returns-access-denied-for-user-na-imtn-comusersum_mwi-reason-no-role-assignments-associated-with-the-specified-user-were-found-on-domain-controll/
all the best