.tim Files - 3.5 Error with Sybase Connection


None of my .tim files previously created work in TDP 3.5 when their query connection type is Sybase. It appears that the port is now part of the .tim XML whereas in prior versions of TDP it was not. I feel like this happened with 3.4 also but I thought it was fixed with a patch.



Any way I can fix this without manually rebuilding each of .tim or manually editing the XML?


Hello Dave,

What error are you seeing? Also would it be possible to get a sample file from you so I can do some tests on my end?



I will email you some sample files I put together, however, I just realized that this error only occurs while using automation and the .tims seem to work if you open them directly.

– 4/25/2014 8:50:15 AM: Script_21.log: Setting up environment

– 4/25/2014 8:50:15 AM: Script_21.log: Script run by Toad Data Point

– 4/25/2014 8:50:15 AM: Script_21.log: Build started

– 4/25/2014 8:50:15 AM: Script_21.log: Compiling script

– 4/25/2014 8:50:16 AM: Script_21.log: Warning: No Exception Handler. To send an Email when there is an error, change the value of Email on Error to true and enter email values. – 4/25/2014 8:50:16 AM: Script_21.log: Build completed

– 4/25/2014 8:50:16 AM: Script_21.log: Begin execution script activities

– 4/25/2014 8:50:16 AM: Script_21.log: Running Import template C:\Users<user>\Desktop\test.tim

– 4/25/2014 8:50:16 AM: Script_21.log: Import_1 - Connection Sybase://@/ is not available

– 4/25/2014 8:50:16 AM: Script_21.log: Failed

Hello David,

Thank you for your email and description. I will have a look at the files and let you know what I find.

Michael, were you able to reproduce this error?

Hello David,

I apologize for the delay. Yes, we were able to reproduce and fix the issue.

Thank you for taking the time to create the sample files. They were a great help.

It should be in the next Beta which should be available around May 19th.