+xThanks. Since the troubleshooting steps didn't conclude outside of LOGbinder, it shows that this is an Exchange issue. Unless Exchange is providing audit log search results, LOGbinder will not be able to operate. Please work with your Exchange admin and possibly with Microsoft to resolve this issue. - Can you do synchronous audit log search instead of the asynchronous? Do you get results?
Use the Search-MailboxAuditLog and Search-AdminAuditLog cmdlets instead of New-MailboxAuditLogSearch and New-AdminAuditLogSearch. - Is there any error message in the MSExchange Management log in Event Viewer after you initiate an audit log search?
- You should also check the status of your mailbox databases using the Get-MailboxDatabaseCopyStatus cmdlet to make sure they are in the Healthy state.
We performed the above mentioned tests but still no result on email. Can you please confirm a few details about the log binder. We have a typical distributed exchange setup with 2 transport servers and 3 mailbox servers. 1 is HA whose address appears by running the command for virtual directory. I need to confirm on which exchange server should we be running the above commands. I was running the commands on transport as well as the HA server, as shown in the thread I can see the receipt of the request after entering the command but no success. Please confirm the server on which I should be running the request, the set of ports that I need to open on the firewall and the directionality for the ports. Kindly mention the direction of port opening e.g., "Open port 443 on firewall from logbinder server to exchange server. etc" I need this information for the network team and exchange team to confirm the issue is on there end.
|