Forum Discussion
Exchange 2016 Event 2159 ADAccess Validation Failed
We intermittently see event id 2159 generated on our Exchange 2016 Server (CU23 Jan23SU). They seem to have appeared sometime in the past month. We tend to see about 50-150 events per day. We've e...
I've examined the database objects I'm seeing these events for and they are our production mailbox DBs, we have 5 of them DB2016-01->05.
If I run Get-MailboxDatabase it lists those 5 DBs so in my case it doesn't appear that these are old/stale objects. I'm able to run Get-AdObject against each of them and it lines up with what I see in the Get-MailboxDatabase output.
I noticed that setting the logging level to expert also generates event ID 2161 which has a little bit of additional information, "Attribute: EdbFilePath. Error message: You must provide a value for this property.. Invalid data: ."
When I look at the DB objects in ADSIEdit there is no attribute EdbFilePath on any of the objects. They do have an attribute msExchEDBFile which points to the actual database. Is it expected that EdbFilePath doesn't exist? If so maybe this is just a weird bug in Exchange.
If I run Get-MailboxDatabase it lists those 5 DBs so in my case it doesn't appear that these are old/stale objects. I'm able to run Get-AdObject against each of them and it lines up with what I see in the Get-MailboxDatabase output.
I noticed that setting the logging level to expert also generates event ID 2161 which has a little bit of additional information, "Attribute: EdbFilePath. Error message: You must provide a value for this property.. Invalid data: ."
When I look at the DB objects in ADSIEdit there is no attribute EdbFilePath on any of the objects. They do have an attribute msExchEDBFile which points to the actual database. Is it expected that EdbFilePath doesn't exist? If so maybe this is just a weird bug in Exchange.
I am having the same issue. We have 4 2k19 Exchange Servers all in a DAG on Windows 2019 Server. About every day we are having to restart the transport services and we are also getting the Event ID 2159. I have a ticket open with MS. Has anyone fixed this issue as of yet?
