O365 message trace logs suddenly stopped logging.
We are seeing following error in Splunkd.log
ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/TA-MS_O365_Reporting/bin/ms_o365_message_trace.py" HTTP Request error: 500 Server Error: Internal Server Error for url: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace?
We had that verified credentials are valid.
Please suggest how to fix this.
I opened a case with microsoft for this error - the issue for me was that the docs (both on splunkbase and in the Microsoft docs article referenced by Splunkbase) say that the Message Trace API can gather data up to 30 days prior. This is incorrect. The correct documentation can be found here, which shows that only a max of 10 days prior is allowed: https://docs.microsoft.com/en-us/powershell/module/exchange/get-messagetrace?redirectedfrom=MSDN&vie...
Switching the start_date from 30 days to 9 or 10 days prior ended up working for me!
This thread has a working solution:
@poisar opened a case with MS and adding a \ before the $filter in the script solved the problem for me
It seems like a lot of people are having the same issue so it's likely on Microsoft's side.
https://answers.splunk.com/answers/779459/microsoft-office-365-reporting-add-on-for-splunk-i-2.html
https://answers.splunk.com/answers/780097/microsoft-office-365-reporting-add-on-for-splunk-n.html
Hi @parikshithreddy ,
If your credential are correct than most probably, it is not able to connect to MS Office365 portal due to proxy or firewall settings.
You may be able to access the portal via web browser, but api callls from terminals are blocked due to your network proxy or firewall settings.
If it is not the case, please share some logs.
Accept & up-vote the answer if it helps.