Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Hi. We are also experiencing the same behavior since several days ago.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.
If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.
Please advice.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.
If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.
Please advice.
mi...@google.com <mi...@google.com>
[Deleted User] <[Deleted User]> #3
Hello,
As the example shown in the video is testing the connection multiple times in a row, has it happened by testing the connection once (or until it succeeds), then running the code and queries needed and after a while trying to connect again? Is it still failing?
Regards.
[Deleted User] <[Deleted User]> #4
hi. it is happening randomly. the user uses the same credentials and same scenario each time.
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.
Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.
Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?
ib...@google.com <ib...@google.com>
la...@gmail.com <la...@gmail.com> #5
I have the same problem, since in this last month my script is executed by many users.
It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.
I tell my users to try to run the code over and over again, until they finally connect.
It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.
I tell my users to try to run the code over and over again, until they finally connect.
la...@gmail.com <la...@gmail.com> #6
Comment has been deleted.
la...@gmail.com <la...@gmail.com> #7
Hi Team,
I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.
We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8
Please fix this issue ASAP
I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.
We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8
Please fix this issue ASAP
ib...@google.com <ib...@google.com> #8
Hi team,
Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.
After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).
I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.
Thanks
Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.
After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).
I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.
Thanks
ap...@google.com <ap...@google.com> #9
Hello,
In order to move this investigation forward our product engineering team may need sensitive data, therefore Issue Tracker is not the best environment (public) to do so.
This is why I strongly encourage you to reach out to your admin to open a ticket to
If you have any additional questions, please feel free to reach out.
Kind regards.
ib...@google.com <ib...@google.com>
la...@gmail.com <la...@gmail.com> #10
Is there any update on this ticket?
We are getting frequently below error and unable to use the application -
Error : Failed to establish a database connection. Check connection string, username and password.
We are getting frequently below error and unable to use the application -
Error : Failed to establish a database connection. Check connection string, username and password.
ib...@google.com <ib...@google.com> #11
Hi there, I'm another Enterprise level user with roughly 50 automated Apps Scripts that need to connect via the JCBC. I was not affected by this issue last yet, but now it's precisely as mentioned above. My scripts fail roughly 50 of the time and it seems to be a completely sporadic error. I'm going to go ahead and take the advice above to open a ticket with our Google Admin.
ap...@google.com <ap...@google.com> #12
I'm also getting this error increasingly. Many scripts running that normally run without issue but the error rate seems to be increasing by the day
na...@google.com <na...@google.com> #13
I'm also having this issue, and the error rate is increasing with time.
Description
Component used: AndroidX ExifInterface Version used: 1.3.6 Devices/Android versions reproduced on: Samsung Galaxy S22 Ultra, Android 13, One UI 5.1
When reporting bugs, please always include:
Where possible, please also provide:
I attached an image that is experiencing this issue. It was captured in portrait mode and should show that in EXIF data that it was rotated 90 degrees. It appears correctly in MacOS Preview and on this online EXIF data site:https://jimpl.com/results/FWuAnboJWW1vdDpRmeUKsccb?target=exif
I added this to dependencies:
I added this to code:
This is the result: