Yahoo put in a new UI for the YQL today and now I keep getting the following error message. I've got this msg before, but by logging out and logging-in it would go away. That doesn't do it anymore.
"Authentication Error. The table requires a higher security level than is provided, you provided ANY but at least USER is expected"
Here is my YQL, it worked fine last week.
select * from fantasysports.teams.roster where league_key='371.l.150156';
Here is the new url for the YQL console
Its not just me Yahoo confirmed the console is down. Since 17 days ago.
"We are aware that the YQL Console is offline. We are investigating the issue."
source: https://twitter.com/ydn/status/936763870974173185
Related
How do I go about troubleshooting login problem with the Microsoft Graph API?
I'm using the new nodejs-connect-rest-sample on node 6.9.1, and used the quick-start page to generate and an AppID. After pressing the "Connect to Microsoft Graph" button, and choosing my normal Hotmail account for login, I'm redirected to an error page saying:
We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later.
What's the next step in troubleshooting this sort of error?
The error page URL actually contains a query string with a more detailed explanation than the displayed web page does... In my case: https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.&state=a9SlXZGisoIQrPQUbDHX732izad7LJzM
The login.live.com page should be able to display this more detail description, but currently fails to, but I'm going to mark this answered as far as a "next step", because I found I could correct the problem by changing the redirect URL registered for the app.
Does this link work?
https://appcenter.intuit.com/Playground/OAuth/IA
I am trying to get my QB online token secret required for working with a ruby gem. I have a valid QB account and I have entered my app's consumer key & secret. All I am trying to do is follow the instructions required to get the example app working from
https://github.com/minimul/qbo_api
Every time I click on the Connect to Quickbooks button, I just get an error message.
Oops! An error has occurred.
Please close this window and try again.
Error Code: no_access_to_this_field
Message: Team Intuit IA Application not allowed to get access to QuickBooks
I have changed the urls in my app and I still cannot get past the error message. I am at a loss since this seems to be a very basic step to start working with the gem. Please tell me the newbie mistake I am making.
Is there any other SDK I need to install? I do not have a Desktop version...just the online version.
So if anyone here happens to not figure out this answer already, its because I set the "Access Token Duration:" option on the Intuit Playground to 120 seconds...the default option.
I changed it to 1200 seconds by mistake, and the login works just fine now! I don't understand why that works, so if someone could answer that I could understand it better!
Thanks #William Lorfing
This can happen if you are using the playground to generate Oauth tokens for either QuickBooks or Payments access and you are not setting the correct data source.
See the answer here: https://intuitdeveloper.lc.intuit.com/questions/1247785
regards
Jarred
In Google console API manager, if I click on "Credentials", a popup comes up up stating "Failed to load service accounts."
If I dismiss that and then try to "add credentials" and select "Oauth 2.0 Client ID" I get another popup that says "A required resource is not available."
When I dismiss that, the underlying page has an exclamation icon and says "Failed to load".
This happening to anyone else? Just started failing this morning.
It looks like it may have been a temporary block. I was having the same issues earlier today, but this afternoon I was able to get past the warning messages. I didn't do anything special outside of refreshing the page (which I did try earlier) and the errors didn't come up, leading me to believe there was some service disruption, but status.cloud.google.com only reported a Google Compute Engine issue.
I use Oauth via Microsoft and it has worked fine for a while, then a couple of weeks ago (can't remember exactly when) i got some tweet or something from someone saying that they had problems signing in with MS Oauth.
The error i get is this.
https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.
The page actually says
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
And that indicates that they may actually have some issues but i think it's been like this for a while so i suspect it's just some generic error.
If i look at my request it says.
client_id=[MY CLIENT ID]&scope=wl.basic&response_type=code&redirect_uri=http://dev.ohso.se/login/ExternalLoginCallback/?provider=microsoft&sid=[some id]
I do get the same error on both my dev app and the production app i have setup.
This is how my callback URLs look like. I have tried to add URLS both with ExternalLoginCallback and externallogincallback but it doesn't seems to work. It looks like it's saved but it's gone when you return to the page.
Anyone know how to contat MS to at least report this bug and maybe also get hold of someone that can help debug my problem?
/Ola
OK, got it. The issue is with your request URL, remove / character from ..back/?provid.... Your request URL should be
client_id=[MY CLIENT ID]&scope=wl.basic&response_type=code&redirect_uri=http://dev.ohso.se/login/ExternalLoginCallback?provider=microsoft&sid=[some id]
and you can have any redirect URL #MS
http://dev.ohso.se/login/ExternalLoginCallback
or
http://dev.ohso.se/login/ExternalLoginCallback/
When creating a new Client ID for OAuth 2.0, I got a message "An error has occurred. Please retry later.". I tried several times this week without success. But I am user with the role owner and I created successfully a Client ID last month with the same user.
Besides, by checking the requests and responses sent with the Chrome Developer Tools, I can notice that I get a 500 error for https://console.developers.google.com/m/project/my_project/client/web/create?xsrf=qwerty
Is there something wrong at Google or it's me ?
Yes, the problem is in the Request you are sending and the Response is an Error response. So if you want to identify the exact error, I suggest if you are passing credentials, double check it once; it might have changed or upgraded.