RE: EIF cannot read Win2K3 created log file from Win XP Pro

From: Barath Vasudevan [MS] (bvasude_at_online.microsoft.com)
Date: 05/14/04

  • Next message: crockett: "RE: EIF cannot read Win2K3 created log file from Win XP Pro"
    Date: Fri, 14 May 2004 15:35:30 GMT
    
    

    Hi,

    The TraceLog files have binary data and have a set structure to them; if
    you are able to read it on Win2k then you should not have any problems
    reading it on WinXP or Win2k3 (unless ofcourse the file is corrupted).

    To come to the problem:
    a. I dont believe this is related to the scripting runtime dll or WMI.
    b. I was NOT able to reproduce the behavior here using the Trace Log Reader
    sample available with EIF. Can you try using it on WinXP to read the
    remote trace log file?
    c. Are there any exceptions being reported? (in the Event Log ?)
    d. Does your AppendEntry() method write to a file/console? How are you
    determining that the WinXP is not able to display the records correctly.
    e. Does it happen with other WinXP machines?
    f. Can you explain what you meant by " if the file is not the one being
    logged to I can read it with the XP Pro box".

    Let us know...
    Thx

    Barath
    This posting is provided "As Is" with no warranties, and confers no
    rights.Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm

    --------------------
    >Thread-Topic: EIF cannot read Win2K3 created log file from Win XP Pro
    >thread-index: AcQ5L37K5K+glL86SkavnDcJ8fKi9A==
    >X-WN-Post: microsoft.public.vsnet.enterprise.tools
    >From: "=?Utf-8?B?Y3JvY2tldHQ=?=" <crockett@thewildfrontier.com>
    >Subject: EIF cannot read Win2K3 created log file from Win XP Pro
    >Date: Thu, 13 May 2004 14:16:02 -0700
    >Lines: 47
    >Message-ID: <AB0140C1-E12F-41AE-A428-8DB047ECAE3A@microsoft.com>
    >MIME-Version: 1.0
    >Content-Type: text/plain;
    > charset="Utf-8"
    >Content-Transfer-Encoding: 7bit
    >X-Newsreader: Microsoft CDO for Windows 2000
    >Content-Class: urn:content-classes:message
    >Importance: normal
    >Priority: normal
    >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
    >Newsgroups: microsoft.public.vsnet.enterprise.tools
    >Path: cpmsftngxa10.phx.gbl
    >Xref: cpmsftngxa10.phx.gbl microsoft.public.vsnet.enterprise.tools:2288
    >NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
    >X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools
    >
    >I am having a problem that I can not read the current log file from a
    remote computer using the XP Pro operating system. I have run the test
    suggested by Mike Hayton in the thread "EIF - The preffered event sink in a
    distributed environment" and came up with one difference. The version of
    my sccrun.dll is 5.6.0.6626 . The log files are being created on a
    Win2K3 server. I can open these files using a Win2K Server and a box
    running Win2K Pro but not on a box using XP Pro. I have not taken the
    step of clearing ADAP like Alf. What do I need to do to get this file to
    return the results in it back to the XP Pro box.

    The code I use to read the log files is as follows.

    //----------- Calling the Enterprise Instrumentation APIs
    ------------------------------------

    private void ReadTraceLog(string fileName)
    {
            // open and read the file of the passed fileName.
            // if exception happens during open, let it be thrown.
            TraceLogReader.ReadLogFile(fileName, new
    EventReadCallback(this.MyEventReadCallback));
    }

    private bool MyEventReadCallback(EventContainer container)
    {
            // for each record read, turn it into an EventEntry
            // (catching any deserialization exceptions) and call AppendEventEntry()
            // with the event entry.
            EventEntry entry = null;
            try
            {
                    EventEntrySerializer serializer = new EventEntrySerializer();
                    container.Evaluate(serializer);
                    entry = serializer.GetEventEntry();
            }
            catch (Exception e)
            {
                    entry = new EventEntry();
                    entry.Add(ErrorMessage, e.Message);
                    entry.Type = null;
            }
            AppendEventEntry(entry);

            // return true if we want to continue reading.
            return (reading && !shutdown);
    }

    I get to the place where the TraceLogReader makes the call to read the file
    and passes the delegate but it never calls back to it. And then the
    display shows no records in the file. The file does have the entries in it
    becuase it can be opened on a Win2k box to show that.

    All security has been set up to allow this across the network.

    One last note is that if the file is not the one being logged to I can read
    it with the XP Pro box.

    Thanks
    Crockett

    >


  • Next message: crockett: "RE: EIF cannot read Win2K3 created log file from Win XP Pro"

    Relevant Pages

    • RE: EIF cannot read Win2K3 created log file from Win XP Pro
      ... you are able to read it on Win2k then you should not have any problems ... reading it on WinXP or Win2k3. ... remote trace log file? ... remote computer using the XP Pro operating system. ...
      (microsoft.public.vsnet.enterprise.tools)
    • Re: Upgrading to XP from W2K - advantages?
      ... I've never regretted upgrading from Win2K to WinXP Pro on the day it came ... If your WinXP CD-ROM is a current version, it will have SP2 integrated into ... If you upgrade from Win2K, your boot folder will inherit the prior name ...
      (microsoft.public.windowsxp.basics)
    • Re: Upgrade to WinXP
      ... the VB dudes migrate to WinXP and now the net. ... > want to upgrade my machine. ... upgraded to XP Pro, I am using XP Pro only. ... of my hardware than my Win2k. ...
      (borland.public.delphi.non-technical)
    • Formatting before Win XP Pro setup
      ... I have Win2k Pro and have tried to make a clean install of ... XP Pro on a second new HDD. ... and my Win2k Pro are in english, ... I have tried to format through Partition Magic 8 after ...
      (microsoft.public.windowsxp.setup_deployment)
    • Re: Installing XP Pro *over* Win2k...bad idea?
      ... It's called an upgrade. ... Boot Win2K, insert the WinXP CD, follow the upgrade prompts. ... you must use WinXP Pro. ... you must have one copy of WinXP for each system that you want to install it ...
      (microsoft.public.windowsxp.basics)