Status Update
Comments
pa...@visma.com <pa...@visma.com> #2
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.
se...@google.com <se...@google.com> #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.
pa...@visma.com <pa...@visma.com> #4
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?
pa...@cecytebc.edu.mx <pa...@cecytebc.edu.mx> #5
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.
se...@google.com <se...@google.com> #6
Hello,
Thank you for your comments, this has been forwarded internally.
Regards.
pa...@ame.g4s.com <pa...@ame.g4s.com> #7
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
pa...@supermetrics.com <pa...@supermetrics.com> #8
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
se...@google.com <se...@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.
pa...@eastwestseed.com <pa...@eastwestseed.com> #10
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.
ca...@centralsanitary.com <ca...@centralsanitary.com> #11
au...@cernogroup.com <au...@cernogroup.com> #12
el...@austinpetsalive.org <el...@austinpetsalive.org> #13
pa...@ame.g4s.com <pa...@ame.g4s.com> #14
Can any one help on this, incase found any solutions
er...@g2g-online.nl <er...@g2g-online.nl> #15
A few days ago I've updated the whitelist based on this document:
ma...@article.com <ma...@article.com> #16
The DB we are connecting to is an AWS RDS database. So far, no signs of trouble with the database itself.
I don't see what I can do to improve the experience (apart from migrating the app). Any insights?
wc...@gmail.com <wc...@gmail.com> #17
One behavior I noticed was when I caught the error in error handling and tried to reconnect in the same code execution it would fail 100% of the time. So my work around ended up writing code that if the execution was from a trigger to create a new trigger to run the code and that seems to work. If the execution was from a menu I would simply alert the user to re-try.
pa...@ame.g4s.com <pa...@ame.g4s.com> #18
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
[Deleted User] <[Deleted User]> #19
pa...@eastwestseed.com <pa...@eastwestseed.com> #20
ch...@arnoldgroupweb.com <ch...@arnoldgroupweb.com> #21
jr...@gmail.com <jr...@gmail.com> #22
[Deleted User] <[Deleted User]> #23
I recommend that everybody file a support ticket here:
We need to continue escalating this issue and bring more attention to it.
de...@madwire.com <de...@madwire.com> #24 Restricted
[Deleted User] <[Deleted User]> #25
After corresponding with a Google rep I went ahead and followed their advice (and the advice of others on this thread) and whitelisted the full IP address list found here:
This - in addition to the fact that I'm about 99.9% sure that the Apps Script team made some form of update within ~24 hours of responding to my ticket without actually announcing/admitting the fact that they did so - completely resolved my issues. I now have a 0% error rate on my scripts. I highly recommend that anybody else experiencing this issue starting by whitelisting the full IP address list.
I will say that this is strange considering it was not necessary at all the past ~2.5 years I've been using GAS, but it seems necessary now. Some updated documentation would be very helpful from Google's side, but it is what it is. I'm just very glad to have found this fixing and hoping/praying it's a permanent one.
dy...@hakesbrothers.com <dy...@hakesbrothers.com> #26
Please escalate as this is starting to affect the production of my company.
wc...@gmail.com <wc...@gmail.com> #27
dy...@hakesbrothers.com <dy...@hakesbrothers.com> #28
wc...@gmail.com <wc...@gmail.com> #29
wc...@gmail.com <wc...@gmail.com> #30
aw...@bingologistics.com <aw...@bingologistics.com> #31
mi...@gmail.com <mi...@gmail.com> #32
mi...@lodgingdynamics.com <mi...@lodgingdynamics.com> #33
[Deleted User] <[Deleted User]> #34
jr...@gmail.com <jr...@gmail.com> #35
We processed the list at:
through the helper tool:
to get a start-stop, range-based list
from the helpful SQL stored procedures described at:
we dumped into a spreadsheet to build a quick formula-based list of
// EXECUTE sp_set_firewall_rule @name = N'Google Whitelist 11 -
...
Hope that's helpful to someone and this really does resolve this annoying issue.
yo...@3pxmedia.com <yo...@3pxmedia.com> #36
Any chance to resolve???
pa...@cecytebc.edu.mx <pa...@cecytebc.edu.mx> #37
After a long time, we had the opportunity in our school to update the IP list (
It would be a great improvement if you could send us an email informing us of the changes in the IP whitelist when it happens.
Thank you.
cu...@curtismartialarts.com <cu...@curtismartialarts.com> #38
I understand this is a very insecure, bad idea, but this just confirms the issue is with google and their IP ranges. I have triple checked adding all of the IPv4 addresses in the link mentioned in the last comment, but I still had frequent connection problems. (Note: I did not add any IPv6 addresses because there is no option for that with my host.)
I contacted Google and explained my problem and, like another commenter above, they said it was out of their scope and advised me to contact my database host.
I am lucky that none of my data is very important/sensitive so I am not overly concerned with the insecurity, but I am more than a little irritated that Google has been ignoring this issue.
If your use-case allows the risk of the insecurity, I would open everything up like I did and see if it solves your issue. I am not holding out hope Google will rectify this issue.
Best of luck!
is...@google.com <is...@google.com>
ma...@gmail.com <ma...@gmail.com> #39
fe...@gmail.com <fe...@gmail.com> #40
The same issue is still present despite adding the %.%.%.% to remote MySQL. It does not resolve the sporadic failure problem.
jp...@google.com <jp...@google.com>
ro...@gmail.com <ro...@gmail.com> #41
Sometimes it's working very well, sometimes not
I hope you fix it soon
ge...@newyorkmoney.com.co <ge...@newyorkmoney.com.co> #42
si lo anterior lo soluciona, quiere decir que NO esta actualizada la lista de IPS, ahora, mi administrador de la base de datos debe estar en la capacidad de informar la lista de ips que son bloqueadas, alguno de ustedes sabe como hacerlo sin necesidad de pedirle al administrador de la base de datos, o cpanel, o servidor o como se llame? agradezco.
Description
Basic code sample (with a few variables omitted) is as follows:
var dbUrl = 'jdbc:sqlserver://'+dbhostName+'databaseName='+db;
return Jdbc.getConnection(dbUrl,dbUser,dbUserPass);
This code will succeed 50% of the time and fail the remaining 50% of the time sporadically. I am running a test function that returns the JDBC connection and it's literally like flipping a coin: 50/50 chance that it will fail.
I have attempted the "useSSL=false" workaround - and many other work arounds - to no avail.
Just to provide some additional information that may be helpful, I am connecting to an Azure SQL Server instance via the following Apps Script JDBC getConnection(url, userName, password) method:
This has happened on and off over the past 2 years or so, but turning off the V8 runtime would typically help. That is no longer the case, and this issue now occurs in both the legacy and V8 runtimes. Also, this issue seemed to previously be isolated mostly to time-based trigger functions, but now this occurs across the board with any function, time-based or manual execution.
Lastly, this issue seems to have increased DRAMATICALLY over the past ~2 weeks or so. I noticed a huge spike towards the end of July 2022 and this has persisted as of today, 2022-8-8.
While Apps Script is an extraordinary tool for Google Workspace users and it has transformed my company's ability to spin up quick solutions, these types of long-running issues with JDBC and V8 runtime are simply unacceptable. I am seeking a permanent solution to this issue and will provide any additional information necessary if it will help achieve that goal.
Screen recording of the issue attached.