SQL Server Connection Never Times Out

[ketteringkid]

Guys,

I am running version 11.7.1. I cannot upgrade because things don't work 100% right with moving files for me when built in versions 12. Regardless, I am having a problem where the SQL Test does not honor the timeout value that I have set it to. I have tried 3 different places setting the value of SqlConnectionTimeout. I set it to 1 (second I had assumed) and I placed it in the Install Parameters, the dialogue load, and immediately before running

I read this thread and the example and I have matched it, but it doesn't seem to make any difference. Also, I checked the script and the value is only being set when I expected it to be.

Any thoughts/help?

-Ryan

[ketteringkid]

I also reviewed this page, and matched it's process.

[ketteringkid]

I ran this in debug mode, and it seems to set the SqlConnectionTimeout value correctly, but the ODBC driver never honors anything I set. I also confirmed that executing a SQL Query, with a configured timeout will also always fail.

[ketteringkid]

This has to be an issue with the 11.7.1. Nothing seems to matter. Here is a snippet from the log. As you can see, I am properly setting the timeout.


MSI (c) (5C:E4) [10:14:57:165]: PROPERTY CHANGE: Modifying SqlConnectionTimeout property. Its current value is '10'. Its new value: '15'.
MSI (c) (5C:E4) [10:14:57:167]: PROPERTY CHANGE: Adding SqlConnectionString property. Its value is 'Driver={SQL Server};Server=sadf;Port=1433;Uid=sadf;Pwd=asdf;'.
Action ended 10:14:57: SQLConnectionDlg. Return value 1.
MSI (c) (5C:2C) [10:14:57:170]: Doing action: TestODBCConnection
Action 10:14:57: TestODBCConnection.
Action start 10:14:57: TestODBCConnection.
MSI (c) (5C:64) [10:14:57:209]: Invoking remote custom action. DLL: C:\Users\02PETR~1\AppData\Local\Temp\MSI8C20.tmp, Entrypoint: TestSqlConnection
MSI (c) (5C!28) [10:14:57:242]: PROPERTY CHANGE: Adding SqlConnectionOK property. Its value is '0'.

[mihai.petcu]

Hi Ryan,

I think issue was fixed in version 11.8. Can you please upgrade and see if it persists?

All the best,
Mihai

[ketteringkid]

Yeah... I confirmed it was fixed in 11.8.

In a related note, that would have been very good information for the version history. I had to try a bunch of versions.