PipeLineTracing in Exchange 2013 fails to write output

mbkitmgr
mbkitmgr used Ask the Experts™
on
I am troubleshooting an issue with email flow in Exchange 2013.  I have enabled PipelineTracing and all parameters
Set-TransportService Mailbox01 -PipelineTracingSenderAddress chris@contoso.com
Set-TransportService Mailbox01 -PipelineTracingPath "F:\Anti-Spam_Agents_Log"
Set-TransportService Mailbox01 -PipelineTracingEnabled $true 
Get-TransportService Mailbox01 | Format-List PipelineTracing*

Open in new window

With the last command it reports all is configured correctly but... when I send an email from the mailbox nothing is written to the output folder.  I can't see any details of required folder permissions (set it to everyone FC as a test but no change) for Exchange to write to the chosen output folder,

Any suggestions

Late edit - I also stopped and restarted ther Transport and MBX Transport Delivery services just in case
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
AmitIT Architect
Distinguished Expert 2017

Commented:
Do you see any folder created under F:\Anti-Spam_Agents_Log

Author

Commented:
HI Amit, I had created this folder for another pupose, so it already existed.  Should I perhaps have let the trace create it itself?

Author

Commented:
After 2 days of letting the config of Pipeline Tracing execute it finally wrote some logs - dated 1 June 2019

What is odd is that I have sent other emails since that date and Exchange hasnt written any logs for them yet.  I posted the exact same question on Technet and no one has responded so we appear to be in unknown territory.
AmitIT Architect
Distinguished Expert 2017

Commented:
I have verified your commands and all looked fine to me. So, nothing else, i was able to find, why it was not working. How many servers you have?

Author

Commented:
In this case its a single exchange server.  MSFT technet support suggested checking Role Membership in Exchange, but they are mentioned in the doco for PipelineTrace setup and I'd already had them configured.

I ran Get-ServerHealth in case something was "ill" all is ok.  No idea.

If I get time, I am thinking of testing it on another server at another clients site that has Exchange 2013 on Server 2008 R2

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial