Assigned
Status Update
No update yet.
Comments
bl...@google.com
ke...@google.com
mi...@google.com
el...@google.com
[Deleted User] <[Deleted User]>
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.
bv...@google.com
bw...@google.com
an...@walmart.com
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.
ta...@gmail.com
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?
as...@fastretailing.com
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.
ba...@periscope-tech.com
Hello,
Thank you for your comments, this has been forwarded internally.
Regards.
an...@gmail.com
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
ko...@google.com
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
lu...@gmail.com
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.
ol...@kroo.com
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.
ga...@sayatalabs.com
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.
hz...@dotdashmdp.com
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
no...@gmail.com
I'm also having this issue, and the error rate is increasing with time.
kf...@google.com
Hi
Can any one help on this, incase found any solutions
Can any one help on this, incase found any solutions
ol...@openvpn.com
We've also experienced an increasing amount of errors. On aug 26, I found that our IP whitelist was outdated so depending on the IP that was used on Google's side the connection might have been failing because of the firewall that was blocking the connection.
A few days ago I've updated the whitelist based on this document:https://www.gstatic.com/ipranges/goog.txt . This has reduced the number of errors drastically. However, it seems that every now and then we still have the same error. Maybe the list provided by Google is outdated and it's using different IP addresses than the ones listed?
A few days ago I've updated the whitelist based on this document:
in...@simplerain.com
Hi, I am experiencing a heap of sporadic connection errors. My users are based across the United States, meanwhile I am accessing the app from the UK and it seems that I can always connect without issue. It seems like people on the west coast are more likely to experience it than the east coast. Some people reporting the problem are operating from as far east as Texas.
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?
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?
he...@gmail.com
We have had this issue as well and has increased recently as previously stated.
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.
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.
si...@aboutyou.com
Hi All,
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
ke...@sony.com
To the above response, thank you but this did not work for me. It's still about 50/50 with enabledTLSProtocols=TLSv1.2, so there's no noticeable change.
ga...@google.com
[Deleted User] <[Deleted User]>
Any update from Google? The issue has been reported a month ago. My organization is not able to use any of the Apps Scripts applications because of this error.
ch...@yahooinc.com
Any updates to this? Been over a month.
te...@sendbird.com
deleted
ma...@gmail.com
1.5 Months later and still no real feedback or support. Followed the recommendation from the Google rep to contact their support line and was told that it's outside of the scope of standard Google Support, and was redirected to Google Developer Support instead.
I recommend that everybody file a support ticket here:https://support.google.com/a/contact/wsdev?fl=1
We need to continue escalating this issue and bring more attention to it.
I recommend that everybody file a support ticket here:
We need to continue escalating this issue and bring more attention to it.
la...@google.com
ri...@dojocloud.tech
redacted
ma...@google.com
An update from my side.
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:https://www.gstatic.com/ipranges/goog.txt .
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.
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.
Description
Problem you have encountered:
Using an external table with inferred schema, the data source are JSON documents. Querying the table using Standard SQL, often results in error "Unsupported empty struct type for field 'field1'". This happens because empty struct types are not supported by BigQuery.
What you expected to happen:
We would like to be able to query the table even if all records have null values for the struct.
Other information (workarounds you have tried, documentation consulted, etc):
This works for Legacy SQL and for Standard SQL, it works if records with a non-empty struct are returned alongside the records with the null values. However, the use of Standard SQL is preferred over legacy and there are scenarios were customers cannot control when the struct is empty or not.