Catalin wrote: ↑

Mon Nov 27, 2023 1:12 pm

Hello,

If possible, could you please give me some more details about this scenario so I can further investigate this?

It would help if you could provide some screenshots of the issue so I can have a better view of the scenario.

Best regards,
Catalin

...some logic that get information and combines file paths
& $devconPath $params
...some additional logic that would complete device installation using default PowerShell commands

The script doesn't have any try/catch block and do not return any exit values.

Catalin wrote: ↑

Wed Nov 29, 2023 12:58 pm

Hello,

The script doesn't have any try/catch block and do not return any exit values.

This is something you should add to your script if you need it.

The script either returns success or error, these are the only options for the Windows Installer service that interprets them.

Best regards,
Catalin

try {
    # Some code that may cause an error
}
catch {
    # It is not clear how I should pass an error message to see this message in Advanced Installer Analytics exception details 
    # It seems simple Write-Host doesn't work.
    Write-Host "Encountered Error:"$_.Exception.Message
    exit 1
}

Catalin wrote: ↑

Mon Dec 04, 2023 3:19 pm

Hello,

What I'm thinking here is that in case of failure, you can set a property and then see it in the "Custom Properties" section of your Installer Analytics account.

Have you tried that?

Best regards,
Catalin