.NET custom installer issue - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

guruvn
Posts: 6
Joined: Tue Mar 08, 2011 2:52 am

.NET custom installer issue

Hi All,

I created a .NET Custom Installer DLL which was added into the InstallExecuteSequence\Commit within the Custom Page. However everytime when I run the setup file I got an error message dialog box such as: "Product: Custom Installer -- Error 2869. The dialog ErrorDlg has the error style bit set, but is not an error dialog.". So what should I do now.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: .NET custom installer issue

Hello,

To see the typical reason and solution to this error, please follow this article from our user guide.

Best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
guruvn
Posts: 6
Joined: Tue Mar 08, 2011 2:52 am

Re: .NET custom installer issue

Thank you Mihai.
I actually had got the link before I posted my question onto the Forum. I just wondered would the issue be due to the trial version edition which I have been using.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: .NET custom installer issue

Hello,
I just wondered would the issue be due to the trial version edition which I have been using.
I don't believe the issue is related to the trial version. Have you tried the solution proposed in our user guide article?

Best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
gvasko
Posts: 33
Joined: Mon Jun 07, 2010 7:11 pm

Re: .NET custom installer issue

Hi,
since I spent a lot of time with a very similar issue, I put here my notes.

I created a custom action (.NET Installer class action) and the 'Action Data' was filled automatically with

Code: Select all

/LogFile= /ReqVersion=4.0.30319 /InstallType=notransaction /Action=Install "[#CXNSharedAddinInstaller.dll]" "[TempFolder]dotNetCustAct.dll_2_Config.xml"
I didn't pay too much attention to this and that was the mistake. 'ReqVersion' means the version of the required .NET framework. Apparently AI uses the latest framework can be discovered. However, running the msi on other machines, AI's dotNetCustAct.dll tries to load the .NET framework with the given version even if it isn't installed on that machines.

After I modified this to

Code: Select all

/ReqVersion=2.0.50727
everything worked well.

There is a similar post: http://www.advancedinstaller.com/forums ... =2&t=11706

I think mentioning the role of the ReqVersion parameter would be useful both in the documentation and in the FAQ 'Why do I receive the 2869 error?'

Hope this will be helpful for others.
Gabor Vasko
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: .NET custom installer issue

Hi Gabor,

Thank you for the details, I have added the recommended improvement on our list and it will be performed as soon as possible.

Please let us know if you have other suggestions/questions regarding our application.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”