I understand. My post was more of an alert the issue is still happening out in the field. If I find out more information on reproducing it, I will share it.
Unfortunately, I don't think I can do that. I personally have never seen it, but our QA see the issue occasionally. On the same system it happens So, coming up with a sample project is unlikely... Here is what the QA reported: files are copied or moved to C:\AI_RecycleBin\ folder under a unique fold...
Thanks for the reply, Catalin. The issue does seem to be machine-specific. I cannot reproduce this at-will. The same MSI will work fine elsewhere, but fail on a 'bad' system. The 'run from' is selected to be the temporary folder in the AI Powershell script options. The links I included possible expl...
Hello! Our (un)installer runs a few Powershell scripts. They all are running from the temp folder (as specified in the Powershell execution options). Unfortunately, on some systems, the invocation of the scrip generates the following error: > MSI (c) (44:90) [18:40:33:647]: Invoking remote custom ac...
The receiving email server refused to accept the email with the .zip file attached:
Error: 550 5.0.350 One or more of the attachments in your email is of a file type that is NOT allowed by the recipient's organization.
Message rejected by: CY8PR11MB7135.namprd11.prod.outlook.com
I have now also noticed that some of the hidden properties are logged in a clear text. Indeed, they are passed as action data to a custom action (a VB script). In the log file they are present like this: PROPERTY CHANGE: Adding XXX_Propertyproperty. Its value is YYY_clear_text. I've followed the sug...
Having this capability would be extremely nice. A single .msi targeting x64 and ARM64 is becoming a hot requirement, at least for me. A part of our installation is x64, even on the ARM64. And we use custom actions to call into out x64 DLLs during uninstall, etc. As is, the custom action 'call functi...
Hello, thanks for looking at this question. I have the following problem: how can I pass some custom properties to the MSI of a version of a product that is being upgraded? Normally the values are obtained via user entering them in a custom dialog. On the upgrade, they can be passed on the msiexec's...
Here is the script in case it helps someone: #this script is used to solve the issue of removing the installation folder when it is locked while uninstalling # (like uninstalling while in the command prompt in the install folder) $installPath = $args[0] $MethodDefinition = @' [DllImport("kernel32.dl...
