Forum Discussion

anhtnt's avatar
anhtnt
Copper Contributor
Aug 23, 2022

Get-MessageTrackingLog showing no results - Exchange 2013

Hello,

I trace mail with command: get-messagetrackinglog from 06/30/2022 to 07/31/2022 but return nothing. I checked in the directory containing the log, the log file still exists.

Why is there no result when I run the command?

Many Greetings and thanks for any hint. 

  • Thai_Lam's avatar
    Thai_Lam
    Brass Contributor
    anhtnt
    You have to test the following in your lab before doing it. It was sometime ago and this happened to me so i can't recall exactly what i did but here it is. There is a index folder in the message tracking log folder, you may try to delete it (just the file in it not the folder) and restart "Microsoft Exchange Transport Log Search" service, it should take a while to rebuild.

    I would suggest not to tinker on the message tracking log file, make sure antivirus exception was made to the path. If you need to work on the file, you can try to copy it to another location and work on it, log parser etc.
  • cengizyilmaz's avatar
    cengizyilmaz
    Brass Contributor

    yes, before going into more detailed problems, would you run the command suggested by @farislaeb, and then make a query via a sender

    Get-MessageTrackingLog -Sender email address removed for privacy reasons

     

  • farismalaeb's avatar
    farismalaeb
    Steel Contributor

    anhtnt 

    Why to use the date as this format

    Try to pass the date by using the Get-Date cmdlet

    Get-MessageTrackingLog -Start (Get-Date).AddDays(-4) -End (Get-Date).AddDays(-1)
      • cengizyilmaz's avatar
        cengizyilmaz
        Brass Contributor

        anhtnt 

        anhtnt 

        Try Get-TransportServer | select MessageTracking* to see what the path is for you.

         

         

         

         

        Get-TransportServer | select MessageTracking*

         

         

         

        Have you restart your Exchange service and try to get the logs again?
        Try to restart the Microsoft Exchange Transport Log Search service and Microsoft Exchange Active Directory Topology service manually.

Resources