Internal error executing query

Answered

From time to time Datagrip returns the following error: "Internal error executing query. No results returned.". This happens on pretty random intervals and even after running a query that beforehand worked. Nothing works again until I restart Datagrip (which is often followed by the pop-up that I have to log in to my databases, even though I have those saved as forever). Is there a solution to this?

0
2 comments

Hello Perry,

Please reproduce the problem again, collect the logs (Help | Collect Logs and Diagnostic Data), upload them to https://uploads.jetbrains.com/ and provide its ID.

0

Hello Perry,

We've carefully looked through the logs you sent us. We see there were attempts to establish a connection

2022-09-29 15:40:59,034 ...... Connecting as: <username>

But it seems that it never succeeded. Going through the stack trace, we see that it ends with the driver failure

Caused by: com.denodo.vdb.vdbinterface.common.VDBServerException: The username or password is incorrect

Due to incorrect credentials, the driver loses connection with the databases

2022-09-29 15:40:59,277 ...... Driver: com.denodo.vdp.jdbc.Driver 8.0 20220815
2022-09-29 15:41:00,426 ...... DbSrcWriter stopped

The IDE shuts down and resumes afterward

2022-09-29 16:39:26,196 ...... START INDEX SHUTDOWN
2022-09-29 16:39:29,847 [3528859] INFO - #c.i.u.i.FileBasedIndexImpl - END INDEX SHUTDOWN
2022-09-29 16:39:30,104 [3529116] INFO - #c.i.i.StartupUtil - ------------------------------------------------------ IDE SHUTDOWN ------------------------------------------------------

This cycle continues with every exception

java.sql.SQLException: authentication error: The username or password is incorrect

which correlates with the error you're getting. That being said, we're assuming that this could be an issue related to user credentials changing over a certain period of time. To start troubleshooting this issue, we would advise checking your infrastructure settings (domain politics, deployments, etc). See if there are any deployments within your application taking place that could be possibly changing the password.

0

Please sign in to leave a comment.