none
使用Process Tracking Log tool统计邮件收发数量,统计出来的计数为0? RRS feed

  • 问题

  • 我使用下的processtrackinglog.vbs脚本区统计exchange2007邮件的收发数量,结果在MTSummaryResults统计出来的邮件收发数量却是0,这是什么原因呢,我操作步骤如下:

    1)运行脚本

    [PS] C:\Windows\System32>.\cscript.exe C:\mailscripts\ProcessTrackingLog.vbs "C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking" 0  all

    2)运行脚本显示的结果

    [PS] C:\Windows\System32>.\cscript.exe C:\mailscripts\ProcessTrackingLog.vbs "C:
    \Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking" 0
    all
    Microsoft (R) Windows Script Host Version 5.7
    版权所有(C) Microsoft Corporation 1996-2001。保留所有权利。

    Results will be logged to c:\temp\MSGTRACK\Output\
    Starting Script Version 12.03 at 2012/10/12 16:56:14
    Processor architecture: AMD64

    Process Summary: ""C:\Windows\System32\cscript.exe" C:\mailscripts\ProcessTracki
    ngLog.vbs "C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\Messag
    eTracking" 0 all" (PID=4624)    WorkingSet=10407936     RunTime=0       ProcessT
    ime=.03125      Files=0 UserName="Administrator"


    Server Latency SLA Goal is 30 seconds
    End-to-End Delivery Latency SLA Goal is 90 seconds
    Delivery Latency Exception Logging set at 270 seconds
    Aggregate Queue Size Threshold set at 500 (Total Transport Mail Items)
    Max Message Size Threshold set at 65536 KB (details logged for messages exceedin
    g thresold)

    Process Summary: cscript.exe(PID=4624)  WorkingSet=10780672     RunTime=0
    ProcessTime=.03125      Files=0 UserName="Administrator"

    2012/10/12 16:56:14     ENTER   GetFolders working with Files in C:\PROGRAM FILE
    S\MICROSOFT\EXCHANGE SERVER\TRANSPORTROLES\LOGS\MESSAGETRACKING (count=30, maxPa
    rse=30)
    2012/10/12 16:56:14     OPEN    ParseFile 1 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120913-1.LOG (1 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 2 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120914-1.LOG (2 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 3 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120915-1.LOG (3 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 4 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120916-1.LOG (4 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 5 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120917-1.LOG (5 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 6 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120918-1.LOG (6 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 7 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120919-1.LOG (7 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 8 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120920-1.LOG (8 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 9 C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\Logs\MessageTracking\MSGTRK20120921-1.LOG (9 of 30 files)
    2012/10/12 16:56:14     OPEN    ParseFile 10 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120922-1.LOG (10 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 11 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120923-1.LOG (11 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 12 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120924-1.LOG (12 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 13 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120925-1.LOG (13 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 14 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120926-1.LOG (14 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 15 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120927-1.LOG (15 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 16 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120928-1.LOG (16 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 17 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120929-1.LOG (17 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 18 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20120930-1.LOG (18 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 19 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121001-1.LOG (19 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 20 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121002-1.LOG (20 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 21 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121003-1.LOG (21 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 22 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121004-1.LOG (22 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 23 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121005-1.LOG (23 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 24 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121006-1.LOG (24 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 25 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121007-1.LOG (25 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 26 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121008-1.LOG (26 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 27 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121009-1.LOG (27 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 28 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121010-1.LOG (28 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 29 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121011-1.LOG (29 of 30 files
    )
    2012/10/12 16:56:14     OPEN    ParseFile 30 C:\Program Files\Microsoft\Exchange
     Server\TransportRoles\Logs\MessageTracking\MSGTRK20121012-1.LOG (30 of 30 files
    )
    2012/10/12 16:56:14     DONE    GetFolders done working with Files in C:\PROGRAM
     FILES\MICROSOFT\EXCHANGE SERVER\TRANSPORTROLES\LOGS\MESSAGETRACKING (0 files pa
    rsed, 0 total)
    2012/10/12 16:56:14     INFO    GetFolders encountered 0 files parsed out of seq
    uence (0 total parsed, 0 total processed)

    >>> Removing 0 oServerLatencyDictionary entries for

    2012/10/12 16:56:14     DONE    Main done with files in C:\PROGRAM FILES\MICROSO
    FT\EXCHANGE SERVER\TRANSPORTROLES\LOGS\MESSAGETRACKING (0 total files parsed)

    2012/10/12 16:56:14     INFO    MAIN: Calling WriteSummary

    Summary Results available in c:\temp\MSGTRACK\Output\MTSummaryResults.txt

    2012/10/12 16:56:15     INFO    MAIN: Calling ArchiveFiles
    Could not find C:\Program Files (x86)\WinZip\WZZIP.EXE

    2012/10/12 16:56:15     EXIT    MAIN: Script done!

    3)但是在MTSummaryResults显示出来的结果却为0,我的邮件日志是保留一个月,所以不存在日志为空的现象。

    Script Version 12.03

    Process Summary: cscript.exe(PID=4624) WorkingSet=17698816 RunTime=0 ProcessTime=.078125 Files=30 UserName="Administrator"


    Oldest Log File Processed: 2012/10/12 16:56:14 UTC
    Newest Log File Processed: 01/01/1970 12:00:01 AM UTC
    Total Log Files Processed: 30
    Total Log Files Processed Out of Sequence: 0
    Total Log Files Parsed: 0
    Total Log Files Parsed Out of Sequence: 0
    Maximum File Duration: 0 min
    Minimum File Duration: 1000 min
    Log File Statistics: c:\temp\MSGTRACK\Output\MTLogStatistics.csv
    Valid FAIL events with no DSN Failures found, see c:\temp\MSGTRACK\Output\MTDsnFailureNotFoundResults.csv for details)


    Total Messages sent: 0
    Total Messages delivered: 0
    Total Messages delivered (duplicate): 0 (0 recipients)
    Total Resolve: 0
    Total Expand: 0
    Total Fail with NDR: 0
    Total Fail (Recipient): 0
    Max Fail Events/Min: 0
    Max DSN(Fail) Events/Min: 0
    Total DSN Generated: 0
    Total DSN Badmail: 0
    Total Defer: 0
    Total Poison: 0
    Total Split Errors: 0


    Total MailSubmission Submit Events: 0
    For details on SMTP Send and StoreDriver Deliver NextHop statistics, see c:\temp\MSGTRACK\Output\MTNextHopResults.csv
    Unique FAIL Recipient Status codes: 
    Delivery Latency exceeded 270 sec for 0 messages
    Delivery Latency Exception Details at c:\temp\MSGTRACK\Output\MTDeliveryLatencyExceptions.csv
    DSN Failure Details at c:\temp\MSGTRACK\Output\MTDsnFailureResults.csv

    Mailbox Full Recipient Details at c:\temp\MSGTRACK\Output\MTMbxFullRecipResults.csv

    FAIL Event Sources: 


    Unique StoreDriver Sender Domains: 0


    Unique DSN Source Context: 0


    Unique Encapsulated Addresses: 0


    Public Folder Message Types: 0


    Valid FAIL events with no DSN Failures found, see c:\temp\MSGTRACK\Output\MTDsnFailureNotFoundResults.csv for details)

    Server Latency Distribution for 0 Individual Deliveries:

    Server Latency Distribution for  Messages Processed:

    End-To-End Delivery Latency Distribution for 0 Messages Delivered:

    请大家帮我分析一下,是不是脚本需要设置啊,脚本是在微软官方这里下的:

    http://gallery.technet.microsoft.com/scriptcenter/2f3df4e4-ce50-49a9-aad8-3f9ac251b4f1

    谢谢!


    2012年10月12日 9:02

全部回复

  • 您好!

    1.根据上面的脚本我的测试结果不全为0。

    2.根据你提供的那个链接对一个Log运行下该脚本看看结果。

    谢谢!


    Cara Chen

    TechNet Community Support



    2012年10月15日 8:08
  • 我对一天的日志进行统计,结果依然是一样的。

    统计出来结果:

    Script Version 12.03
    Process Summary: cscript.exe(PID=4492) WorkingSet=10956800 RunTime=0 ProcessTime=.046875 Files=1 UserName="Administrator"

    Oldest Log File Processed: 2012/10/17 16:43:12 UTC
    Newest Log File Processed: 01/01/1970 12:00:01 AM UTC
    Total Log Files Processed: 1
    Total Log Files Processed Out of Sequence: 0
    Total Log Files Parsed: 0
    Total Log Files Parsed Out of Sequence: 0
    Maximum File Duration: 0 min
    Minimum File Duration: 1000 min
    Log File Statistics: c:\temp\MSGTRACK\Output\MTLogStatistics.csv
    Valid FAIL events with no DSN Failures found, see c:\temp\MSGTRACK\Output\MTDsnFailureNotFoundResults.csv for details)

    Total Messages sent: 0
    Total Messages delivered: 0
    Total Messages delivered (duplicate): 0 (0 recipients)
    Total Resolve: 0
    Total Expand: 0
    Total Fail with NDR: 0
    Total Fail (Recipient): 0
    Max Fail Events/Min: 0
    Max DSN(Fail) Events/Min: 0
    Total DSN Generated: 0
    Total DSN Badmail: 0
    Total Defer: 0
    Total Poison: 0
    Total Split Errors: 0

    Total MailSubmission Submit Events: 0

    For details on SMTP Send and StoreDriver Deliver NextHop statistics, see c:\temp\MSGTRACK\Output\MTNextHopResults.csv

    Unique FAIL Recipient Status codes: 

    Delivery Latency exceeded 270 sec for 0 messages
    Delivery Latency Exception Details at c:\temp\MSGTRACK\Output\MTDeliveryLatencyExceptions.csv

    DSN Failure Details at c:\temp\MSGTRACK\Output\MTDsnFailureResults.csv

    Mailbox Full Recipient Details at c:\temp\MSGTRACK\Output\MTMbxFullRecipResults.csv

    FAIL Event Sources: 


    Unique StoreDriver Sender Domains: 0

    Unique DSN Source Context: 0

    Unique Encapsulated Addresses: 0

    Public Folder Message Types: 0

    Valid FAIL events with no DSN Failures found, see c:\temp\MSGTRACK\Output\MTDsnFailureNotFoundResults.csv for details)

    Server Latency Distribution for 0 Individual Deliveries:

    Server Latency Distribution for  Messages Processed:

    End-To-End Delivery Latency Distribution for 0 Messages Delivered:

    2012年10月17日 8:47
  • 您好!

    根据你提供的脚本,我的测试环境下是好的,该问题可能出现在你的日志文件上。


    Cara Chen

    TechNet Community Support

    2012年10月23日 3:31