Scenarios Where ProfileUnity Writes to Windows Event Log

The ProfileUnity client writes to the Windows Application event log when errors occur during certain operations such as failing to restore or save portability archives, failing to playback FlexApp packages, and various AWS AppStream processes. 

There are two sources reported in the Application log: ProfileUnity Client.Net and ProfileUnity Client.NET FlexApp. Entries from these sources all report as Event ID 0. 

The following example entries outline scenarios for both sources along with associated event details.

ProfileUnity Client.Net

Portability Restore Failed

ProfileUnity Client.Net Error 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
module:      PortabilitySettings
message:     There was a problem restoring part of your profile from your Portability archive.  This archive will not be saved again at logoff until the restore failure has been corrected by your Administrator.  Portability Archive UID: '{ArchiveUID}'
error:       ArgumentException {error message}
stack trace: at {object process}

Portability Backup Failed

ProfileUnity Client.Net 6.8.7.9256 a5545d52b {DOMAIN\USERNAME} {COMPUTERNAME} Portability Backup Failed

Portability Restore Succeeded (Optional)

ProfileUnity Client.Net 6.8.7.9256 a5545d52b {DOMAIN\USERNAME} {COMPUTERNAME} Portability Restore Succeeded

Portability Backup Succeeded (Optional)

ProfileUnity Client.Net 6.8.7.9256 a5545d52b {DOMAIN\USERNAME} {COMPUTERNAME} Portability Backup Succeeded

ProfileUnity Client.NET DIA

Validating Package XML - Cannot Read

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Failed to playback package: could not read xml data ({\\Server\FlexAppShare\App_Name.package.xml})

Validating Package XML - Missing

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Failed to playback package: missing xml data ({\\Server\FlexAppShare\App_Name.package.xml})

Failed to Playback Non-CTL Application Already Installed

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Failed to playback package: {Application Name} [005]

Failed to Playback Non-CTL Application NOT Already Installed

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Failed to playback package: {Application Name} [010]

Validating Shortcuts - Missing Target

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Shortcuts are missing or invalid for {Package Name}:
     Shortcut target application is missing ({C:\Program Path\Application.exe})

Validating Shortcuts - Missing Shortcut

ProfileUnity Client.Net DIA 6.8.7.9256 a5545d52b
user:        {DOMAIN\USERNAME}
machine:     {COMPUTERNAME}
message:     Shortcuts are missing or invalid for {Package Name}:
     Shortcut is missing (C:\Users\Public\Desktop\{Application}.lnk)
     Shortcut is missing (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\{Application}.lnk)

Events related to AWS AppStream are written from a single source and to a custom log location: Applications and Services Logs\AppStreamDynamicCatalog\Vendor\Liquidware\Operational.

The following example entries outline scenarios where AWS AppStream events are reported by ProfileUnity along with associated messages displayed under the "Details" tab.

AppStreamDynamicCatalog-Vendor-Liquidware

Add Application Failed

[Error] [AddApplications_Failure] [Timeout waiting for Appstream transport to open.]

Add Application Failed

[Error] [AddApplications_Failure] [Failed to open Appstream transport.]

Add Application Succeeded

[AddApplications_Success] [Added {n} applications to Appstream.]

Add Application Latency Check

[Metric] [AddApplications_Latency] [{1234.56}]

Remove Application Succeeded

[Log] [RemoveApplications_Success] [Added {n} applications to Appstream.]

Remove Applications Latency Check

[Metric] [RemoveApplications_Latency] [{1234.56}]

Remove Application Failed

[Error] [RemoveApplications_Failure] [Error removing applications from Appstream:{...}]

App Virtualization Succeeded

[Log] [AppVirtualization_Success] [Processed {n} CAP files. First one: {C:\FADIA-T\VHDM\...\Data\appinstall.cap}]

App Virtualization Succeeded

[Log] [AppVirtualization_Success] [Processed JITCut w/ {n} shortcuts. First one: {C:\Program Path\Application\App.exe}.]

App Virtualization Time Metric

[Metric] [AppVirtualization_Time] [{12345.6789}]

Source Install Completion

[Log] [Install completed of {EventSource}.]

Install Start Request

[Start] [Start processing request {...} for Operation {...}]

Install Stop Request

[Stop] [Stop processing request {...} for Operation {...}]