PowerShell Universal - 5.0.2

PowerShell Universal releases
1

PowerShell Universal - 5.0.2

Release Notes

Apps

  • Fixed an issue with displaying non-authenticated apps (#3641)

Automation

  • Fixed an issue with scheduling on Windows Server 2016 (#3647)
  • Fixed an issue with script folder display (#3639)
  • Fixed an issue where the Time Zone selector was missing for schedules (#3649)
  • Added missing list view for scripts (#3635)
  • Fixed an issue where the inline debugger wouldn’t trigger in the integrated environment (#3622)
  • Fixed an issue where schedule parameters would not display
  • Fixed an issue with the script folder view (#3660)

Portal

  • Fixed issue with parameter sets on portal (#3617)

Platform

  • Fixed issue with license enforcement in the admin console
  • Fixed an issue where the agent would give up retrying to connect after some time (#3614)
  • Fixed an issue with psudb.exe throwing an exception then migrating app tokens and jobs (#3652)
  • Improved performance of psudb.exe
  • Fixed an issue where disabling Windows Auth would cause users to fail to login until cookies were deleted (#3648)
  • Fixed an issue where the platform would attempt to use powershell.exe, if configured
  • Fixed an issue changing Script Base Path when API Base Path was already set (#3651)
  • Fixed a concurrency issue with SQLite databases
  • Fixed issue copying app tokens on HTTP servers (#3655)
  • Improved connection logic in cmdlets to support more server configurations
  • Fixed an issue with online license activation retry failing

Downloads

1 Like
2

I’m getting a blank page with the error message Object reference not set to an instance of an object. when accessing the scripts page.

If I blanked my scripts.ps1 file then the page would load again, so I quickly narrowed it down to this occurring any time you have a script-defined in the root of your scripts, so maybe an issue that cropped up when fixing #3635 or #3660?

Simply going to the scripts page and creating a script with the name “Test.ps1” will trigger the bug, i.e. the following line will be present in scripts.ps1: New-PSUScript -Name "Test.ps1" -Description "Test.ps1" -Path "Test.ps1"

1 Like
3

I can’t reproduce this. Can you check the system log for an extended error message\stack trace?

Never mind. Installed on a new machine and can see it.

1 Like