sorry we encountered an error and were unable to complete your request

 

Hello, I need help...

I am trying to connect MySQL 5.6 in Looker Studio but cannot connect to the database in Looker Studio with this error ID. - Error ID: 7c8e2211

How can I solve this issue? 

lookerstudio.png

15 REPLIES 15

Has anybody found a fix for this issue? I still get the same error while connecting new or exisiting DB via Mysql v8..

Same here 😞 Trying to validate a working data source to postgres on AWS. The RDS itself is reachable by other apps but not looker. It happens from time to time, without consistency and I couldn't find out why. 

Same. I cannot add or edit datasource from AWS RDS PostgreSQL

jorgenivia_0-1716217899216.png

 

hello, i have the same problem, i dont know if is a problem for Sql or is a problem of the google servers, if any know what are happening, please respond my comment

It's an issue with their app. Waiting for their resolution.


--
Cheers,
Damu R

Seems fixed although I couldn't find any notification from Google about it .... 

I am still getting this issue with my Redshift cluster 

Same problem, using 5.7. Tried opening my remote hosts to % in Cpanel and no luck. Works fine in Navicat. 

Any update on this issue ??

I'm having the same issue again. Any update?

the solution is don't use Looker Studio, Use Power BI...
--
*Simon Cortes Arango*
Database Analyst MySQL

<>

*M:*
*O:* (305) 631-2780
*A:* 2111 NW 84th Ave, Miami FL, 33122

<>

Currently facing the same issue for the past 2 days

Sorry, we encountered an error and were unable to complete your request.

Error ID: b35a7f47

for SQL Server connection, anyone else ?

Having the same issue.
Connecting Looker Studio to GCP hosted SQL instance - it worked before, nothing should have changed but it just stopped working.

Sorry, we encountered an error and were unable to complete your request.

Error ID: 2eb0f448

Any suggestion as to what this could be?

Can you give it a try today, it seems to be working smoothly right now. Not sure if there was an update.

As I was replying you, now the issue has returned lol. There's a reliability issue with Looker Studio for the past 6 months it seems. And not really anyone to support.