When working with cross connection queries using Teradata, TDP didn't keep the new password. (4314233)

When working with cross connection queries using Teradata, TDP didn't keep the new password.

When working with cross connection queries  using Teradata, TDP didn't keep the new password.

For example the following scenarios:

 First Scenario:

  The end user reset the Teradata password and updated the password on the Teradata connection in Toad. However when the end user was working  across multiple databases, using Query Builder, the end user was getting an error about invalid password.

Second Scenario:

The end user reset the Teradata password and updated the password on the Teradata connection in Toad, if the end user leaves the jobs running, in TDP,  MySQL database tries  to connect to Teradata and get invalid password.

Files corrupted  under :  " %LOCALAPPDATA%\Quest Software\Toad Data Point Hub Data\conf " 

WORKAROUND # 1 :

1. Make sure Toad Data Point is closed and No jobs are running

2. Back up this folder   " %LOCALAPPDATA%\Quest Software\Toad Data Point Hub Data\conf " 

3. Delete manually the files under:  " Toad Data Point Hub Data\conf "

QAT-13094

Beta Disclaimer : Please note that the beta program is open for evaluation and feedback only. It is not recommended that you use it as a replacement for the current commercial version or use in a production environment. If you have any feedback relating to issues within the beta version, please report this via the  Beta Community