ultimately, this may come down to a bug in the code that requires Vlad's intervention.
normally, THAT involves sending a BSV to him for duplication of the error...
of course thats a major PITA, because you'd also need data that he needs to load (somehow) which will show the issue.
WHAT I WOULD DO
is turn on the Logging for FULL SQL statements,
and find that SELECT statement that Aware is sending to the DB
by double-clicking on that line (in the log), it will open a popup whereby you can COPY the SELECT stmt.
Using your SQL management tool, you should be able to paste that same stmt and see the same error appear.
Then, you'll probably see some kind of typo in the complicated SQL that aware generated.
Once you've done this legwork, you prolly won't need to go thru the hassle of submitting a BSV to Vlad, because he now would see the illegal SQL thats being generated.
PS _ You didn't mention your backend DB
