locked
Strange behaviour with transcript RRS feed

  • Question

  • Hi all,

    In our application we use the transcription feature quite heavily for outputting log files. Recently we saw strange behaviour in the transcript, and we have pinned it down to update KB2919355 (https://support.microsoft.com/kb/2919355). After applying this update to our systems (Windows Server 2012R2 Standard, english) , the transcription feature starts to behave strangely.

    Here's the transcript contents while doing a simple write-host.

    **********************
    Windows PowerShell transcript start
    Start time: 20150203163637
    Username: LAB\administrator
    RunAs User: LAB\administrator
    Machine: VE-RDCB (Microsoft Windows NT 6.3.9600.0)
    Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Process ID: 2456
    **********************
    Transcript started, output file is c:\test.log

    PS C:\Users\Administrator.LAB> write-host "testing writehost"

                CurrentMatchIndex              ReplacementIndex             ReplacementLength CompletionMatches
                -----------------              ----------------             ----------------- -----------------
                               -1                             0                            10 {System.Management.Automat...



    PS C:\Users\Administrator.LAB> Stop-Transcript
    **********************
    Windows PowerShell transcript end
    End time: 20150203163650
    **********************

    And here's the output for our script, which throws weird "the pipeline has been stopped" errors...

    **********************
    Windows PowerShell transcript start
    Start time: 20150203163605
    Username: LAB\Administrator
    RunAs User: LAB\Administrator
    Machine: VE-RDCB (Microsoft Windows NT 6.3.9600.0)
    Host Application: powershell.exe -Command Import-Module 'amclient';Update-AMCache;Disable-AMSystemEventFlag;Invoke-AMEvent -Name Startup
    Process ID: 1920
    **********************
    Transcript started, output file is C:\ProgramData\Automation Machine\Logging\Startup_20150203163605-997353497.log

    PS>TerminatingError(): "The pipeline has been stopped."

    PS>TerminatingError(): "The pipeline has been stopped."

    PS>TerminatingError(): "The pipeline has been stopped."

    PS>TerminatingError(): "The pipeline has been stopped."
    False
    Updating policy...

    Computer Policy update has completed successfully.
    User Policy update has completed successfully.

    Updating policy...

    Computer Policy update has completed successfully.
    User Policy update has completed successfully.


    **********************
    Windows PowerShell transcript end
    End time: 20150203163635
    **********************

    Weird thing is, after uninstalling KB2919355, it all works fine again...

    Does anybody have any idea what is going on?


    Kind Regards, Henk Hofs | http://www.IThastobecool.com

    Tuesday, February 3, 2015 3:50 PM

Answers

All replies