This has been an issue every now and then for the last year but now since last Friday it's dramatic.
None of our queries are refreshing like they were before.
Message:
Error interacting with REST API: Couldn't connect to server ERROR
[HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with
REST API: Couldn't connect to server Table:
Notes:
PowerBI - Desktop refresh works
The table or view triggering the error differs, it's not always the same table or view.
It seems to be related to running parallel queries, loading from the same table simultaneously.
Dataflow jobs are reported to be working, since the load sequentially
Can Microsoft and Google talk to each other? On both sides they are pointing to each other.
It seems that this has affected several users in the last days.
I found this Public Issue Tracker where it's said that the BigQuery Eng team is working on this. I could also see that there are no workarounds available for now.
Feel free to ask for updates or add additional questions on it.
Related
We're running into WSO2 Identity Server issues like Admin(Carbon console) user, Normal user(Service provider) unable to login, basically not able to do any operations.
Upon looking into logs, we found that it's because postgres db is getting blocked in one specific scenario which we were able to figure out as mentioned below:
Whenever SCIM2 GROUP PATCH request is made to add a group member who is already present in the same group and when the group member count is more database is being blocked.
This isn't valid scenario, which we later handled at our application end to not add same group member(Also, opted for SCIM2 Bulk API as it won't return all members back to improve performance). But now we're not sure, if we won't run into such issues again. Some times, we're having to restart the server.
So I wanted to know if there are known solutions for such issues. Is there any way, we can reduce DB blocking time.
IS v5.10.0
I have a problem after migration postgres instance from 9 to 12, we were following this method https://cloud.google.com/sql/docs/postgres/upgrade-db.
Before migration, I had a graph whit active connections on instance page and after the migration (on the new instance - postgres 12) - I don`t have values on this graph.
I am receiving a message like "No data is available for the selected time frame."
Also if I am run a query like "SELECT * FROM pg_stat_activity;"
I see the number of connections.
At this moment the graph section for connections count in Postgres12 is not currently supported. The Cloud SQL engineering team is working on implementing this feature as its already implemented for other Postgres versions. This is not just happening to you, it is a general behaviour.
The best way to report an issue is to use a Google Issue Tracker1, where you can share your project information.
I found that same error reported by another client but I cannot relate it to your scenario.
I'm investigating by days with no results about this exception that my NextJS app is currently throwing, in particular when I try to open a single specific URL:
502: BAD_GATEWAY
Code: NO_STATUS_CODE_FROM_FUNCTION
ID: zrh1:4zx5l-1572269318137-64d401b5d058
Here's the screenshot:
Basically, I have on https://lucacattide.dev/about/en a page that this app should open. This is linked to a MongoDB third-party cloud API platform - Squidex - which is responsible to populate the page itself, via GraphQL queries. The app uses Apollo as GraphQL client. The app instead, is hosted on ZEIT.co serverless cloud, with Now 2.0 version.
During the development process, everything works fine. The page loads up and data is fetched in the right way. Notice that for development, I'm working on now-dev environment instead of a custom Express server, in order to reproduce the production one, as suggested by ZEIT itself.
The exception is being thrown on the production environment - the live one on the hosting platform, not on localhost; the main problem is that no errors are being shown on live logs or local development. So I'm literally going mad in inspecting the possible cause.
I've already tried to test the involved page, by splitting it in sections and trying to exclude child components, or focusing the inspection on the GraphQL query. But the first hasn't produced results and the latter works fine in every environment.
As last try, I deleted and re-created the back-end contents related to that page, because in the past I had a similar issue due to an old GraphQL edited schema that didn't reflected its modifications through the API - so in that case I was still receiving 502 errors. But this time it didn't worked.
Anyone could help me to understand what's going on, please?
Thanks everyone in advance
The issue was caused by an incompatibility between the d3-cloud library and the Now environment.
By replacing it with the react-wordcloud one, the error has been solved.
Thanks everyone for your assistance.
We are a small school district and I have written a simple form for teachers to report disciplinary problems. The destination spreadsheet has a script bound to it and an onFormSubmit trigger is set.
The script uses the form data using the event object e from the function onFormSubmit(), creates a report in Google Docs, send email notices to relevant people and does a few maintenance tasks. Link to code.
It's been working fine until recently when the trigger occasionally fails to fire. No error message; the form data is submitted. This morning, two teachers in separate incidents entered a form and the trigger failed; a third entered the form and it worked.
The form and sheet are 'owned' by the Dean of Students account and users access the form anonymously on the network (not in Google account). The form is set with VIEW privilege for anyone with a link; the sheet has no privileges, only owner.
I am completely stumped as to why this would work sometimes and not others. Clues?
I recently developed a Google Spreadsheet with multiple sheets that takes data from 4 different forms. When the form data comes in, I have scripts that run multiple calculations and formatting on that data, so the onFormSubmit trigger is crucial for me. I've come across the exact same problem you are having right now.
At first I thought there was something wrong with my code and I checked it over and over again. Then, I scoured the web for answers to why my triggers failed about 10 to 20% of the time. A lot of what I found on Google forums related to problems from Google's side. I found that tons of people faced the same problem I had, but none of them had a definitive fix.
My eventual solution was to create yet another trigger that fires every 8 hours. This runs everything my other triggers run yet again just to make sure everything I wanted to do has been done. Of course, that trigger could fail, too. But so far, I've been checking the sheet (new data comes in about every 6 hours or so) and I haven't had to fix any problems whereas before, I had to rerun scripts daily.
Maybe for your case, you can have a function that goes through and sends emails that previous faulty triggers failed to send. Then have this function fire every however many hours you prefer.
This is probably not a very satisfying answer but it's the best I can do. Good luck!
I am using Tableau Desktop 8.2 and Tableau server 8.2 (Licensed versions) , the workbook created in Tableau are successfully published to Tableau server.
But when the user want to see the views or workbooks it takes a very long time to preview or open?
The Workbooks are created with Amazon RedShift Database having (>5 million records)
Could somebody guide me on this? like what is it taking a long to preview or open even after being published to Tableau server?
First question, are the views performant when opened using only Tableau Desktop? Get them working well on Desktop before introducing Server into the mix.
then look at the logs in My Tableau Repository which include query strings and timing info to see if you can narrow down the cause. You can also try the Performance Recorder feature.
A typical problem is an overly expensive query just to display a dashboard. In that case, simplify. Start with a simple high level summary viz and the introduce complexity testing the impact on performance. If one viz is too slow, there are usually alternative approaches available
Completely agree with Alex; I had a similar issue with HP Vertica. I had lot of action set on the dashboard. Considering the database structure is final, I did created the tableau extract and used the Online tableau extract in place of live connection. Vola! that solved my problem and the users are happy with the response time as well. Hope this helps you too..
Tableau provides two mode of data refreshes:
Live : Tableau will execute underlying queries every time the
dashboard is referred / refreshed. Apart from badly formulated
queries, this is one of the reason why your dashboard on Tableau Online
might take forever to load.
Extract : Query will be executed once, according to (your) specified
schedule and same data will reflect everytime the dashboard is
refreshed.
In extract mode, the time is taken only when the extract is being refreshed. However, if the extract is not refreshed periodically, the same, stale data will reflect on the dashboard. Thus, extract view is not recommended for representations of live data.
You can toggle Live <--> Extract from the Data Source pane of Tableau Desktop. (refer top right of the snapshot).