KB0034 - How to collect logs

KB0034 - How to collect logs

Purpose

The purpose of this article is to provide clear ordered steps for users of PowerShell Universal and to submit them to Ironman Software (typically for a support case).

Background

Having logs from PowerShell Universal is typically needed to assist with troubleshooting issues. Providing a quality bug report can help to speed up the time to resolution.

Version 4.x Procedure


1. Recreate the issue (if applicable) and note the time ⌚
2. From the PowerShell Universal console, navigate to 'Platform', 'Logging'.
3. Click 'Download System Logs' to download a .zip file containing the logs.
4. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.
5. Please include a summary that explains the issue that is occurring along with the timestamp of approximately when the issue occurred.



Log verbosity levels were removed in version 4.x of PowerShell Universal. All logging is verbose regardless of appsettings.json.


Version 3.x Procedure (Quick method)

1. From the PowerShell Universal console, navigate to 'Settings', 'General', 'Diagnostics'.


2. Click 'Download Logs' to download a .zip file containing the logs.
3. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.

Version 3.x Procedure (Advanced method)

1. From the PowerShell Universal console, navigate to 'Settings', 'General', 'Diagnostics'.
2. Change the logging levels to Debug for both 'Log Level' and 'Microsoft Log Level'

3. Take your time to recreate the issue for which you are gathering logs. Note the time ⌚ at which the error occurred.
4. Click 'Download Logs' to download a .zip file containing the logs.
5. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.
6. Include as many details as possible, including the timestamp of when the error occurred.
7. Set the log level back to 'Information' and the Microsoft Log Level back to 'Warning'.

    • Related Articles

    • PowerShell Universal Service crashes on startup after an upgrade to 1.4.6

      Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer.  Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...

    • KB0011 - Are licenses different between Production, QA and Test/Development servers?

      Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...

    • KB0074 - Connecting to PSU API w/Windows Auth

      Scope This article applies only to PSU environments where Windows Authentication[1] is enabled and known to be working[2]. Problem You are not able to interact with the PSU instance using the Invoke-WebRequest PowerShell cmdlet even though logging in ...

    • KB0066 - Get-WMIObject cmdlet not working

      Scope This article applies to any scenario where the Get-WMIObject cmdlet is expected to be available and functioning within a PowerShell Universal instance. Effectively, this article will only apply to instances that run under the Windows operating ...

    • KB0041 - About Templates

      Purpose The purpose of this article is to provide a timeline around the Template functionality of PowerShell Universal. Background Templates were introduced to provide a starting point for newcomers to PowerShell Universal. They have since been ...