+ New Ticket

Aginity Closes When I Execute a Query

Comments

15 comments

  • Official comment
    Avatar
    Aleksander Vinokur

    Hi,

    We regret hearing you have such problems with Aginity Workbench.

    Please, send us Workbench log to support@aginity.com and we will try to help you.

    Regards, Alex.

    Comment actions Permalink
  • Avatar
    Michael Min

    Here's the log:

    00000014 11:56:27.857:     WARN: Unrecognized data type `abstime`
    00000014 11:56:27.859:     WARN: Unrecognized data type `anyarray`
    00000014 11:56:27.860:     WARN: Unrecognized data type `timestamp with time zone`
    00000014 11:56:27.866:     WARN: Unrecognized data type `real[]`
    00000014 11:56:28.001:     WARN: Unrecognized data type `interval`
    00000014 11:56:28.004:     WARN: Unrecognized data type `tid`
    00000014 11:56:28.049:   LEAVE: ObjectCache.DoGetDBObjectsAsync()

    0
    Comment actions Permalink
  • Avatar
    Matt White

    Aginity is crashing for me enough that it's almost unusable. I'm running against a Redshift database. Your log is more informative than mine..at least its complaining about unrecognized data types. My log doesn't seem to be warning about anything...

    My colleagues are also having problems with it crashing, so far not quite as bad as what I'm experiencing. Sometime rebooting seems to clear it up.

    I've tried some other tools but, at least on Win10, so far none of them are great...they may not crash but then they have other problems.

    Would love to solve this crashing problem!

    0
    Comment actions Permalink
  • Avatar
    Michael Min

    Unfortunately, I have not been able to resolve this issue... even with Aginity support's help. Aginity had me verify permission (access) to the software folder. When that didn't resolve the issue, they have me verify that I had the correct version of .net installed. Finally, they stated that some other software must be interfering with Aginity and told me to check the Windows Event log. 

    If you get this issue resolved, would you mind sharing your solution? I'll do the same.

    0
    Comment actions Permalink
  • Avatar
    Matt White

    I will certainly share, if the issue is resolved or if I find a different tool that works for me.

    0
    Comment actions Permalink
  • Avatar
    Matt White

    Working with Aginity, it seems that there is a windows .dll that is the 'cause', and that isn't easily changed. I'm on win 10. The problem is happening for me and a colleague who also has win 10. Another colleague who is still on win 7 has no problem. So maybe they'll come out with a new build that will be more stable for win 10?

    In the meantime, I noticed that the .dll was related to clipboard functionality, so I (almost entirely irrationally) stopped trying to use the 'run highlighted sql' (F5) functionality. It's less convenient but it seems like it crashes about once a day now versus every 20 minutes before.

    Once it does crash I find that I have to reboot to get it stop crashing. 

    0
    Comment actions Permalink
  • Avatar
    Aleksander Vinokur

    Hello Matt,

    Unfortunately, we can't reproduce this issue on our end. Myself and my colleges use Aginity Workbench on win 10 on the daily basis and do not experience any issue related to yours.

    We a fully understand it is destructive for you. The only one thing at this moment we could suggest is to try installing Aginity Workbench for Redshift on the bare Windows 10.

    0
    Comment actions Permalink
  • Avatar
    Michael Min

    My recommendation is to using SQL Workbench/J. It's free and works well.

    Download can be found here:

    http://www.sql-workbench.eu

    0
    Comment actions Permalink
  • Avatar
    Kenneth Ehrman

    POTENTIAL SOLUTION

    Aginity would completely die no matter what the query just as described above.

    WHAT WORKED 

    Turn "Ssl Mode" to "Disable" on Redshift connection setting screen.


    0
    Comment actions Permalink
  • Avatar
    Aleksander Vinokur

    We would suggest using the latest version of Aginity Workbench for Redshift with Amazon Redshift ODBC driver.

    Please, read the article below:

    https://www.aginity.com/documentation/WB/RS/Default.htm#Aginity_Topics/Aginity_Workbench/Aginity_Workbench_Release_Notes.htm%3FTocPath%3D_____3

     

    Regards, Alex.

    0
    Comment actions Permalink
  • Avatar
    Kenneth Ehrman

    @Alexsander Vinokur

    That is exactly the version we are running:
    Version 4.9.3.2778 (build 12/19/18).
    Fresh install, not upgrade.


    On the developer machine in question running Aginity against Redshift without "Ssl Mode" set to "Disable" the application completely crashes when running any query, even something as simple as 

    SELECT 1 AS Foo;

    We are checking Windows-related SSL settings, because, the problem presents itself on one developer's machine here, but not the other.

    I will post any findings here.

    0
    Comment actions Permalink
  • Avatar
    Aleksander Vinokur

    Kenneth,

    Please try to use the Amazon Redshift ODBC driver instead of the "Aginity native driver". To do this, download and install the Amazon driver by following the instructions from the Release Notes:

    For instructions on how to download and install the Amazon Redshift ODBC driver, see the Amazon Redshift documentation. After you install the driver, depending on your version of Windows, select Amazon Redshift (x64) ODBC or Amazon Redshift (x32) ODBC in the driver list, in the lower-left corner of the database connection dialog box. To specify an authentication type for your connection, click Advanced, select the authentication type, and provide values for the required authentication properties.

    Regards, Alex.

    0
    Comment actions Permalink
  • Avatar
    Kenneth Ehrman

    @Alexsander,

    I have the Amazon Redshift (x64) ODBC installed.

    MACHINE A (mine) ::
    Have used native for past year, never crashed.
    Switched to ODBC/SSL Require ==> Crash
    Switched to ODBC/SSL Disable ==> No Crash
    Switched to Native/SSL Require ==> No Crash
    Switched to ODBC/SSL Require ==> No Crash

    So you can see, I am having a difficult time duplicating the crash reliably.

    HOWEVER, I WANT TO HELP
    So, here are the results of my experiments.


    Machine A
    (Driver/SSL Setting)

    ODBC/Disable=> Works
    ODBC/Allow => Works
    ODBC/Prefer=> Works
    ODBC/Require => Works

    Native/Disable => Works
    Native/Prefer => Works
    Native/Require => Works

    CONCLUSION: once i successfully executed a query, every combination of driver and ssl settings worked. Now unable to make it crash.

    I will run the same tests on the machine on which Aginity had been reliably crashing and post results later.

    HTH,

    //ken

    0
    Comment actions Permalink
  • Avatar
    Aleksander Vinokur

    Kenneth,

    Thank you for your feedback. We apreciate it!

    Regards, Alex

    0
    Comment actions Permalink
  • Avatar
    Ryan Smithman

    For what it's worth to anyone else who runs into this, my problem appears to be that I had too many applications open while trying to run queries.  When I closed most/all open applications and tried again, Workbench has been running just fine without crashing.

    Really just noting it may help for some to try something super simple (close all programs, restart computer, etc.) before digging into logs, settings, etc.  My guess it my issue had something to do with available memory to run queries.

    0
    Comment actions Permalink

Please sign in to leave a comment.