TD 6.0 SP4 Crash on Invalid Sybase Connect

[Brian Howard]

Hi,

The following issue relates to an invalid setup, but I believe TD should not crash under this scenario.

On attempting to connect to a Sybase database that is defined correctly in the TD sql.ini, is defined correctly in the sybase sql.ini BUT is no longer a valid server, i.e. the server is shut down / decommissioned then TD crashes.

Repro case attached.

Could Unify please comment on when and if this issue will be fixed.

thanks in advance.

Brian

[Jeff Luther]

I'm surprised there's a crash; if the server name is wrong, TD won't find and the SqlConnect() will return FALSE. That's what I see when I tried your test.

One possible reason: When you installed SP4 did you first uninstall your prior v6 then do a full/complete install of SP4? Or did you apply the upgrade/patch of SP4 to your existing TD v6 install? If you used the upgrade, I suggest uninstalling your SP4 and doing a complete install of SP4.

Also, try connecting using the SQLTalk that's in your TD install folder and see what happens. It should fail gracefully too.

BTW, I suggest commenting out the When SqlError in your test. Why? because it's 'masking' whatever error TD would be reporting in its default SQL error dlg. box. Once you get things working and want to filter out certain errors, then use When SqlError.

[Brian Howard]

Hi Jeff,

Thanks for your quick response.

I did a complete uninstall and resinstall of sp3.

This issue is in sp3 as well, i.e. it is not new, but it took me a while to work out how to reproduce the error.

I tried with sqltalk and it crashed too.

I know the When SqlError is masking any built in responses but the app crashes with or without it.

When you tested this did you change your sybase sql.ini so that it was pointing to an invalid server?
i.e. the entry in both sql.ini files must exist but the sybase entry point to an invalid server address.

thanks

Brian

[Jeff Luther]

When you tested this did you change your sybase sql.ini so that it was pointing to an invalid server?

Just tried that with v6 SP4 and get a SQL error only, as I'd expect:

JL_InvalidNameError30003-NoCrash.png

If that is what you mean by invalid server name then I am not sure what the problem could be. I'll ask our router developer about this.

the entry in both sql.ini files

Both??? There's only one INI that TD and TD's local SQLTalk, use: That's the SQL.INI in your TD install folder. (If you are also referring to the other INI in the local \sqlbase folder under TD's folder, that INI is used for SB only and is not used for connecting to any other DB brands.)

[Jeff Luther]

P.S. You know what, I do not see where you say what the SYBASE DB server and your client are. Here's what's certified for TD v6:
http://www.guptatechnologies.com/Produc ... atrix.aspx

and may run with other SYBASE/client versions, but could this be your issue??

[Brian Howard]

Hi Jeff,

No, this is not what I meant. The entry in the TD sql ini needs to point to a correct entry in the Sybase sql ini. But the entry in the Sybase sql ini needs to be invalid. i.e. point the sybase ini value to an invalid ip / port combination, or to a server that is shutdown.

i.e. if the following is the correct value for Fred06
[FRED06]
query=NLWNSCK,10.99.11.236,5000

change it to
[FRED06]
query=NLWNSCK,10.99.11.237,5000

where there is no Sybase server at 237

cheers

Brian

[Jeff Luther]

Brian - I tried again and did not get a crash. I'm just not sure what is different (wrong?) about your configuration what would cause a crash like this.

[Brian Howard]

Hi Jeff,

Thanks for trying. I have looked further into this and it could be an issue with using Sybase 12.5.3 Client ( 15 Servger ), which according to your compatibility matrix is not supported. The problem is we cannot change the Sybase client until we completely upgrade to 6, as Sybase 15 client does not work at all with TD 3.1. So I guess we have a catch-22 situation.

We will have to manage this by ensuring our clients do not have any invalid configuarations.

Once again thankyou for your time and consideration.

cheers

Brian