Tocano
Enthusiast
Enthusiast

Thank you for the follow up. 

Steps to reproduce:

  1. Launch powershell 5.1 console with empty profile (no autoloading modules)
  2. > $VerbosePreference = "Continue"
  3. > Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log
  4. > Get-Process
  5. > Import-Module VMware.PowerCLI

If you open the transcript file, you'll notice that it begins logging lines, but at some point during the middle of that import process, it stops logging and closes the transcript file properly with a Windows PowerShell transcript end and an End time.


As for your troubleshooting suggestion, that was a good idea. And initially, when I opened VMware.VimAutomation.Common.ps1 and commented out the content, and relaunched a new console, the transcript would progress, but still end - just this time at like VMware.VimAutomation.Cis.Core.ps1.  When I edited that file and commented out the content, it would progress to VMware.VimAutomation.Core.ps1. And commenting that one resulted in the transcript ending at VMware.VimAutomation.ViCore.Cmdlets.dll - and since I don't know how to edit a dll, that's where I stalled.

This is starting to feel like a line involving ending a running debugging transcript was accidentally left in a function of the compiled code and is getting called at the conclusion of each (or at least many) modules.

Thanks again for your suggestions. I'm still open to any troubleshooting recommendations.

Thank you.

 

Edit: Easier steps:

  1. Launch powershell 5.1 console with empty profile (no autoloading modules)
  2. > $VerbosePreference = "Continue"
  3. > Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log
  4. > Measure-Command {Get-VM} 

This will end in an error, but will import less modules and you'll still be able to see the log be stopped and closed prematurely. 

Reply
0 Kudos