yet another ODBC Connect: timeout exceeded - Advanced Installer Community
igorskys
Posts: 2
Joined: Tue Oct 08, 2013 10:49 am

yet another ODBC Connect: timeout exceeded

Hello,

I reviewed a lot of topics regarding this issue, but my issue is something different.

Into.

I have SQL Inline script which is executed during uninstall. It works perfect when I use Remove.

MSI is trying to run this sql script when I upgrade/patch installed application. And there are 2 issues.

1. I don't need to run this script when I upgrade. To prevent this I added conditions (NOT PATCH, NOT AI_PATCH, NOT MSIPATCHREMOVE) to AND Script AND Connection.
2. even if it tries to run SQL script it cannot connect to database. I don't store it in registry. User provides SQL connection details like (type, sql server/instance, username password if needed)

so questions.

1. how to avoid running UNINSTALL SQL Scripts.
2. How to avoid ODBC connect: timeout exceeded.

Thanks in advance.
Please let me know if you need more information.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: yet another ODBC Connect: timeout exceeded

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

In order to achieve what you want you should use a condition like this:

Code: Select all

(REMOVE="ALL" AND (NOT UPGRADINGPRODUCTCODE))
for your SQL Script.

Let us know if this helped, otherwise please give us more details about your scenario.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
igorskys
Posts: 2
Joined: Tue Oct 08, 2013 10:49 am

Re: yet another ODBC Connect: timeout exceeded

Dear Daniel,

AI provides great support and correct, useful, helpful answers! It helped! UPGRADINGPRODUCTCODE - did the job...

To make it working I had to uninstall previous version, install new one with UPGRADINGPRODUCTCODE and tried to update with updated version. As I understood UNINSTALL SQL Script or conditions are executed from previous version, not from updated. Is it correct assumption?

Have a good day!
Igor
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: yet another ODBC Connect: timeout exceeded

Hello Igor,
AI provides great support and correct, useful, helpful answers! It helped! UPGRADINGPRODUCTCODE - did the job...
Thank you for your consideration words.
To make it working I had to uninstall previous version, install new one with UPGRADINGPRODUCTCODE and tried to update with updated version. As I understood UNINSTALL SQL Script or conditions are executed from previous version, not from updated. Is it correct assumption?
Yes, this is correct. The UPGRADINGPRODUCTCODE property is set in the MSI which is being upgraded if the package is uninstalled by an updated version (during upgrading).

If you have any questions just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”