PowerShell Universal - 3.8.4

PowerShell Universal releases
1

PowerShell Universal - 3.8.4

Release Notes

APIs

  • Fixed an issue where viewing an endpoint ID that didn’t exist would show an error page (#2227)

Automation

  • Fixed an issue where schedule parameters would not be populated when editing a schedule (#2023)

Dashboards

  • Fixed an issue where New-UDMap would not render properly
  • Rolled back a change to UDDynamic that caused it to fail to load properly
  • Fixed an issue where reopening a mobile web browser would cause the dashboard to stop working
  • Fixed an issue where New-UDTextbox -OnValidate would never return as valid
  • Fixed an issue where New-UDUpload was not aligned with other buttons (#2216)
  • Fixed an issue where New-UDatePicker could not be disabled (#2141)

Platform

  • Fixed an issue where submenus would not collapse in the admin console (#1838)
  • Fixed an issue where the license notification would not show in git manual mode (#2220)
  • Fixed an issue where initialize.ps1 would not be run during the first git sync (#2225)
  • Fixed an issue where user names would not be shown for user sessions established with Windows authentication (#2224)
  • Fixed an issue where MSI would fail if the installation directory was changed between installs (#2207)

Downloads

1 Like
2

Since installing this update PSU service wont start and im getting the following application error in the event logs.

Faulting application name: Universal.Server.exe, version: 1.0.0.0, time stamp: 0x6387d353
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x00007ffd17d6f004
Faulting process id: 0xafc
Faulting application start time: 0x01d9608f8d8ef909
Faulting application path: C:\Program Files (x86)\Universal\Universal.Server.exe
Faulting module path: unknown
Report Id: 91846e14-11a0-4e3f-9931-1aeb3201a7d7
Faulting package full name: 
Faulting package-relative application ID:
3

I updated from 3.7.13 to 3.8.4.

I had two dashboard pages with a “New-UDDynamic with a New-UDTable” in each, the UDTables have unique Id’s, but the UDDynamic had the same ID. It was fine in old version, but in the new version it loads the same table on both pages, the table that gets loaded is the first table you loaded. So if you go to page 1 and load the table, then go to page 2 and try to load that table, the table from page 1 appear. And visa versa.

I changed the New-UDDynamic id on one of the pages, now one table loads and I need to update the page (F5) to get the other table to load, and then the first table doesn’t load until I update the page again.

4

@Banzarykey - There should be another error alongside this one that will provide a better error message.

@djo - I will try to reproduce this issue and circle back. - EDIT: I can reproduce this and I see the issue. We may roll out a 3.8.5 build shortly to get this corrected.

1 Like
5

We will do a release as soon as GitHub is restored…

1 Like
6

Thanks Adam,

I should of looked a bit closer the first time, Having started the process again i get these 2.
Error:

Faulting application name: Universal.Server.exe, version: 1.0.0.0, time stamp: 0x6387d353
Faulting module name: coreclr.dll, version: 6.0.1322.58009, time stamp: 0x6387cbf1
Exception code: 0xc00000fd
Fault offset: 0x0000000000094f6e
Faulting process id: 0x1a60
Faulting application start time: 0x01d960a8030d6242
Faulting application path: C:\Program Files (x86)\Universal\Universal.Server.exe
Faulting module path: C:\Program Files (x86)\Universal\coreclr.dll
Report Id: e9a48e3a-d243-49fb-aeb9-c0c04fa22721
Faulting package full name: 
Faulting package-relative application ID:

Information:

Fault bucket 2057887317129239444, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Universal.Server.exe
P2: 1.0.0.0
P3: 6387d353
P4: coreclr.dll
P5: 6.0.1322.58009
P6: 6387cbf1
P7: c00000fd
P8: 0000000000094f6e
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2b37add4-cabe-4758-8c3b-61aa171790e8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bfd7bbdd-cc06-405e-9aed-d0c0dea3763a.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7b59fae9-242d-4c61-902e-7e756924def2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.80087a17-c347-487c-bec3-cb54baa19493.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4d955ee1-8963-45ae-9438-e837c03bfc82.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Universal.Server_3e8338b9b5d8b45d5ea3d618e080505d9e6_ce6cdf41_3140b49f-298a-4828-9107-5f38b0f0bfbf

Analysis symbol: 
Rechecking for solution: 0
Report Id: e9a48e3a-d243-49fb-aeb9-c0c04fa22721
Report Status: 268435456
Hashed bucket: 24f3a439362b67b2ac8f159c9d451b94
Cab Guid: 0
7

Is there an error labeled .NET Error or something like that? I’m expecting a stack trace in one of them.