This sounds like the need for a Support Ticket to be opened. To help the team in this thread and in Support, try the following to see if you can get a Workstation log file that contains more detailed information.
1) Exit out of the Workstation application so it is not running
2) Navigate to your c:\users\<yourId>\lisatmp_10.2.x directory and remove the Workstation.log This simply clears out the log file so it is easier to review while debugging the error in question.
3) Start Workstation
4) If the step that is causing you issues is deep in a test case, start the Test in ITR mode and execute to the step prior to where the exception occurs. This simply minimizes the amount of output going into the Workstation log file.
-- Leave ITR running but do not execute the step that fails just yet,
-- Open an editor
-- Edit your LISA_HOME\logging.properties file
Change log4j.rootCategory=INFO,A1 to log4j.rootCategory=DEBUG,A1
Add these lines below log4j.rootCategory
log4j.logger.com.mchange.v2.c3p0=DEBUG
log4j.logger.com.mchange.v2.resourcepool=DEBUG
log4j.logger.com.mchange.v2.sql=DEBUG
(I am hoping the above will dump more information about the SQL query into your Workstation log file)
-- Save the file
5) Go back into the ITR Session and continue execution of the step causing the error.
You may need to 'kill' ITR manually.
Check the Workstation.log file afterward and see if any more detailed information is produced.
6) Reopen logging.properties, set the debugger back to INFO, and comment the logging of the mchange class.
Please let us know if this produces more detailed information from which we can help you.