We are working on an Intellectual Property and cannot share the Installer. But, the same issue occurs with the BrowseForFile sample MSI as well. All you need to do is, build the installer (32-bit) for BrowseForFile sample and run it on a 64-bit machine with Windows 2008 Server OS. I am ...
I tried on another machine with Windows Server 2008 (64 bit) OS. The same error resulted. The same functionality is working on Windows 7 32 bit systems. We are yet to test on Windows 7 64 bit machines.
Please help me understand if there is anything specific for 64bit architecture that ...
That resolved the last error (error on the Finish page). But, the error which comes after Browse functionality still comes up. Below is the sequence of errors I get. I am able to continue with the Installation and am able to see the license file getting copied. But, these errors give a ...
I tried running the sample on Windows Server 2008 OS. I got a series of errors as in below screenshots -
I ran through the steps of the installer wizard pages and clicked Install. This error comes during the progress (but in my case it comes immediately after browse) Screenshot1.jpg ...
This error occurs on Windows Server 2008. Our MSI targets only Vista and above operating systems and it works on Windows 7. Haven't tested for Vista yet.
Is the sample different from what is given in the Help manual?
I am using BrowseForFile custom. I followed the steps mentioned in the documentation and created the required UI. Now, when it is run on an x64 machine I get the below error after I click OK in the Browse dialog.
I have a situation where I have to validate a license key (custom approach). The need to do this on the Wizard page itself and if valid only then proceed to next page. Since, the UI Custom Actions can take only unmanaged assemblies I created a C++ class to test it. It worked.
A debug trace in my CustomAction dll has revealed the issue. I was not passing certain Arguments required via the Custom Action Data. Thanks for you help. I am able to run the installer successfully now.
I have changed the execution options but still the error persists. But, this time the log shows few additional traces indicating it was able to open the Custom Action.
MSI (s) (88:98) [17:28:27:497]: Executing op: ActionStart(Name=dotNetCustAct.dll,,) Action 17 ...
I am evaluating the Advanced Installer for our project requirements and am facing troubles running the .Net Installer Custom Actions. I get a 2869 error when I attach this action in the Install phase of the Install Execution sequence.
The Installer Action is currently part of a Visual Studio ...
FOLLOW US
Get the latest news in Application Packaging