Exchange 2010 mp 14.02.0071.0
You might be experiencing empty report issues for the following reports if the default log paths for exchange message tracking are changed.
This post is covering the solution and the way that Exchange 2010 MP collecting the data for these Reports.
Exchange 2010 MP utilizes System.ApplicationLog.GenericCSVLogReader module type as the datasource to collect data from message tracking logs for server statistics. The overridable parameters for this data source (therefore the rules using this datasource) are LogFileDirectory and LogFilePattern.
There are 6 rules using this datasource module with write actions collecting the data to DW in Microsoft.Exchange.2010.Reports.mp.
These rules collect the data which can be viewed through the vServerStatisticsRawV14 view in DW. Then the data is aggregated to hourly and daily views using custom aggregations (lest pause our story here and leave these custom aggregations not to distract from the root issue) so that the reports (mentioned in the beginning) query.
The default LogFileDirectory for all these roles (edge and hub transport roles) includes the default exchange installation path are as follows.
If the Exchange Admin Decides to change this path to a custom one then the rule in OpsMgr wont be aware of the change unless the OpsMgr Admin overrides and therefore wont be collected to DW.
The following Exchange shell command could be used to determine which servers are not on defaults.
for determining the ActiveUserStatistics “get-transportServer | Format-Table Name,ActiveUserStatisticsLogPath” can be used.
Once the servers and the custom LogFileDirectories are Identified the following rules needs to be overrided for the new ones.
Below is a simple table with what to override and how.
System.ApplicationLog.GenericCSVLogReader - http://msdn.microsoft.com/en-us/library/ff427477.aspx
Exchange 2010 MP Guide - http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=692
I experience this issue and i am now able to see reports for the time th change was made however there whre alot of exisitng log files in that location. is there a mechanism to get scom to read the previously generated logs.
The module that reads these logs only supports reading the last line in the log, I am afraid it will only work starting from the change.