Error during install ODBC connect : Timeout execeed - 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!

beuch26
Posts: 2
Joined: Wed Nov 28, 2012 3:54 pm

Error during install ODBC connect : Timeout execeed

Hello,
I make an application in vb.net who use SQL server 2008 R2. In advanced installer i configure correctly (i think) Predifinetion connection.
But During the instalation there are an error when the instalation begin Executing install SQL scripts and the message is OBC Connect: Timeout execeed.

Where come from the error?

Thank for your help :D
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Error during install ODBC connect : Timeout execeed

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

I'm not sure why you are encountering this behavior. This error is shown when the SQL connection fails. You can take a look on our "Creating Database Instance" thread which may be helpful for you.

Let us know is this helps, otherwise please give us more details about your scenario.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
visualsi
Posts: 40
Joined: Fri Oct 14, 2011 4:16 pm

Re: Error during install ODBC connect : Timeout execeed

Hi,

I've seen this message before and unfortunately, it can be a "grab bag" sort of error message that can be shown as the result of one of many errors. Some of the ones I've found:

[*] your script is too big - we get this a lot and it is a REAL pain in the neck - it seems that the installer is OK with 1MB or smaller scripts. When they get larger than that, your package gets more unreliable.
[*] there are two different SQL Server drivers (my descriptions may not be exactly right here) - the "SQL Server" driver (I believe you get this with Windows and the "SQL Server Native Client" (you either get this with SQL Server or you can download this). Installers that don't work or timeout with the "SQL Server" driver, sometimes work for me when I switch to using the "SQL Server Native Client" - it appears to have better functionality. But, whichever you use, you should use the same one when you have the user select the server and database (during the dialogs) and when you run your scripts. If you use the Native Client in the dialog boxes, the installer may think "I can get to this server just fine" and then when you use the "SQL Server" client to run the scripts, it may have difficulty gettting to them. There is a lot of documentation on these drivers.
[*] we also have problems with firewall ports being blocked somewhere in between the installer machine and the database machine...

Hope this helps.

Return to “Common Problems”