Message Tracking in Exchange server 2003 using DOTNET? RRS feed

  • General discussion

  • Hi..

    I have some doubt about message tracking in Exchange server using dotnet. pls help me.

    I know  power shell command is best for Exchange server 2007 and 2010.

    I want to read Exchange 2003 message log files  using DOTnet. How can i do?

    Note: I have used WMI for Exchange 2003 and it works well. But every WMI service has some Qouta limit for Example Windows xp Qouta limit is 128 mb only. So It couldn't perform the Bulk mail tracking opertaions(above 100,000 mails), If I perform it will occurr the Qouta violation error.(

    So pls help me..

    1)How to read Exchange 2003 message log files  using DOTnet.

    Path Finder..

    Wednesday, June 15, 2011 1:39 AM

All replies

  • The Message Tracking Log files are simple Tab separated Text files to read them any normal File.IO code will work eg .

    The real problem maybe for you is how big are the tracking logs files if they are 100 MB's or GB's in size you need to be careful that whatever you use doesn't have memory or performance issues.

    My suggestion however would be to use Microsoft's log Parser this is optimized for reading large files and there are plenty of examples of using it to parse message tracking logs just google log parser and message tracking logs.



    Wednesday, June 15, 2011 10:32 AM
  • Thanks Glen.

     I have created a task Using WMI and I handover that task to my boss in last month. Now only I got the Quota violation error. So pls help me now how can I avoid the Quota error for WMI service. Also my boss said dont use log parser becasue he didn't interset logparser. SO that In starting I have used and developed WMI task.

    I am waiting for you reply.
    Is any other method is have? or how to increase the Quota Limit?

    A PathFinder..

    Wednesday, June 15, 2011 2:47 PM
  • I don't think the quota limit really is the problem for you if your saying your code is failing after 100000 records you need to redesign your queries. Eg don't try to get everything is one query try retrieving the records just for short time intervals eg maybe just grab 1 hours worth of data at time instead of one day this will mean that all your queries will comes in under the quota.



    Wednesday, June 15, 2011 11:23 PM