We are using Google ad-libs v201506 jar. While downloading google adwords reports, intermittently we get the error
org.xml.sax.SAXParseException: Open quote is expected for attribute "lang" associated with an element type "html".
I see that response code is 502 ( bad gateway ) and it appears that the parser is trying to parse the error message from the HTTP response and fails.
Has anyone using the this library seen this error or know a way to fix this?
An "AdWords API Forum" thread from 2013 indicates that one person solved a similar issue by changing from the AdWords sandbox environment to production.
Related
I am getting 502 Bad gateway error while creating team using Microsoft Graph Api and even using PowerShell commands. What am I doing wrong?
1.First attempt from Postman using Microsoft graph api:
Attached is the screenshot of Postman console while I am trying to create a new team:
I had searched online but I haven't got any solution so I tried doing the same thing from PowerShell using Microsoft Teams PowerShell cmdlets but I am still getting the same error .
Here I am using the access token i got from application permissions and I also assigned the app "Helpdesk administrator" role
2.Second attempt with Powershell cmdlets:-
Here is the screenshot of output in PowerShell
I had logged in to Microsoft Teams as a global administrator.
How can I fix this?
Is there a reason you are using the Microsoft beta api instead of the v.1.0?
The fact that you are using two different methods and getting a back-end error suggests either it is a problem with the beta api or possibly some error related to your account.
According to the documentation here https://learn.microsoft.com/en-us/graph/api/team-post?view=graph-rest-beta
When creating a new team based on an existing group, the body should be in this format:
POST https://graph.microsoft.com/beta/teams
Content-Type: application/json
{
"template#odata.bind": "https://graph.microsoft.com/beta/teamsTemplates('standard')",
"group#odata.bind": "https://graph.microsoft.com/v1.0/groups('groupId')"
}
Your Postman screenshot has the "group#odata.bind" value as a slightly different format. Try using the one above, and replace groupId with your actual group id.
Good luck.
I am trying to integrate docusign with java application.
I am following Github example which is working.
https://github.com/docusign/docusign-java-client
Here I am just changing Integrator key,clientId and private key but is not working.
https://github.com/docusign/docusign-java-client/blob/master/src/test/java/SdkUnitTests.java
Here I have attached how I am copying key and id etc...
https://gitlab.com/sanju24689/docusign
Here I have also attached my code also.
It's giving me error like
"com.docusign.esign.client.ApiException: Error while requesting an
access token: POST https://account-d.docusign.com/oauth/token returned
a response status of 400 Bad Request"
See the stack trace
Please try starting with the Java webapp that is ready to go--it is a complete project.
See eg-03-java-auth-code-grant
Recently, a 2 days ago we started to experience exception in google gdata client in Java, when trying to access contacts (feed : /m8/feeds/contacts/default/full). The exception is :
com.google.gdata.util.ParseException: No parser for content type:application-xml[application/xml]
at com.google.gdata.client.Service.parseResponseData(Service.java:2142)
at com.google.gdata.client.Service.parseResponseData(Service.java:2098)
at com.google.gdata.client.Service.getFeed(Service.java:1136)
at com.google.gdata.client.Service.getFeed(Service.java:1077)
at com.google.gdata.client.GoogleService.getFeed(GoogleService.java:676)
at com.google.gdata.client.Service.getFeed(Service.java:1034)
Did some sniffing with Wireshark and in the google documentation I see that correct responses should come with Content type : application/atom+xml but failed responses from google now coming with Content Type : application/xml.
Seems that something changed in google, and now it's returnes not correct content type and our code stopped to work (it was working fine for few years).
Need to say that part of the google app tenants (our customers) still working fine (with the same code) , but some parts of the customers is failing.
Is there any possible workaround for that issue ?
Thanks
The problem was fixed on Google side, so there is nothing to do on our side.
My website has suddenly started reporting this error when ever anyone logs in with Facebook:
HTTP Status 500 - Authorization is required for the operation, but the
API binding was created without authorization.
type Exception report
message Authorization is required for the operation, but the API
binding was created without authorization.
description The server encountered an internal error that prevented it
from fulfilling this request.
exception org.springframework.social.MissingAuthorizationException:
Authorization is required for the operation, but the API binding was
created without authorization.
I have not changed anything relating to Facebook logging in recently, so why might my website be suddenly giving this error?
It seems that version 2.2 of Facebook's Graph API (which is used for this kind of thing) ceased to be available on 25/3/17: See https://developers.facebook.com/docs/apps/changelog. Hence, the sudden change in behaviour in spite of there being no change to my website.
My website uses v1.1.0 of the spring-social-facebook library. I suspect this is the problem and that I ought to be using v2.0.3: http://projects.spring.io/spring-social-facebook/. However, I don't have the skills to take this any further.
I registed for a Yahoo Messenger SDK api and plugged-in the consumer key/sercret into this code:
https://github.com/fernandezpablo85/scribe-java/blob/master/src/test/java/org/scribe/examples/YahooExample.java
However, I'm getting this error:
Exception in thread "main" org.scribe.exceptions.OAuthException: Response body is incorrect. Can't extract token and secret from this: 'oauth_problem=consumer_key_rejected'
at org.scribe.extractors.TokenExtractorImpl.extract(TokenExtractorImpl.java:41)
at org.scribe.extractors.TokenExtractorImpl.extract(TokenExtractorImpl.java:27)
at org.scribe.oauth.OAuth10aServiceImpl.getRequestToken(OAuth10aServiceImpl.java:52)
at com.yahoodemo.YahooExample.main(YahooExample.java:28)
I'm pretty sure that the consumer key/secret is correct because I can get the 'RequestToken' using the same key/secret with a generic HTTP GET request.
Is this a bug in the Scribe library or it's something else?
Even i faced the same problem. But i finally found that:
In developer accounts (http://developer.apps.yahoo.com/projects) After creating the project, Don`t forgot to give alteast one permission for the application like: Contacts - READ, Knowledge Plus- READ. Finally save
The solution from Nagendra worked for me but don't forget to refresh the Yahoo Project page as both the key and the secret code are changed after editing the permissions.