Gracenote Web API is failing on ALBUM_TOC query - gracenote

I have been using the Gracenote Web API in an application for the last year without any issues. Suddenly a couple weeks ago, my application stopped working. I am receiving the following error in response to a simple ALBUM_TOC query:
<RESPONSES>
<MESSAGE>GCSP: Hello error: [130] Please contact Gracenote ODP 00431 [Name: ***** *******] [App: ********] support.
[Gracenote Error 130/74]</MESSAGE>
<RESPONSE STATUS="ERROR">
</RESPONSE>
</RESPONSES>
I have no idea what this means. The developer site hasn't been any help, and there doesn't seem to be any way to "contact Gracenote ODP" (at least no way that I can find).
I found this Stackoverflow question, which appears to be strongly related to my issue. However, I get no hex number that I can look up. Also, when I attempt to create a new app on developer.gracenote.com, the only option I am given is to choose the Entourage platform, which is of no use to me.
Any idea how I can resolve this error?
(One other key point: this is a personal app, and one that I didn't use for several weeks before encountering the error, so it can't possibly be a quota issue.)

Related

Corda: Unclear corda error code with a dead link

I came across an error message when running Corda Enterprise. I was able to solve the error. But the link at the end of the error message caught my attention.
[ERROR] 16:28:02+0000 [main] internal.NodeStartupLogging.invoke - Exception during node startup: certificate key must be an instance of java.security.interfaces.RSAPrivateKey or sun.security.mscapi.RSAPrivateKey [errorCode=fnu1lw, moreInformationAt=https://errors.corda.net/ENT/4.0/fnu1lw]
This link is linked to a page that needs a login. And errors.corda.net is a dead link, too. What is the logic behind this link?
When an error occurs, the link that you see will do one of the followings:
try to find a Stack Overflow post that specifically answer to the error code (it is the fnu1lw in your case) and redirect to the page.
take you to the enterprise support site when it can't find a S/O post that is specific to the error code (as it was assumed that Enterprise customers would have a support contract).
Since you are running Corda Enterprise, so it takes you to the login page of Corda enterprise support.

Why is Bing Custom Search API throwing an error when I make a call through node-js?

I was using Bing Custom Search API for the past week with no problems thanks to the free trial, but today, I tried upgrading to the S1 plan, since the API was sending error messages. I tried regenerating the key as well, but despite doing both of these things, I was still getting errors and unable to use the API.
However, I was able to make calls using: https://www.customsearch.ai/applications, where I was able to use my API key to test endpoints and get the results I expected. What baffles me is that my nodejs code which hasn't been modified aside from the subscription key should still work with the upgraded plan, but it doesn't.
I should be able to help here. Let us do little bit of troubleshooting once:
First go to https://www.customsearch.ai/applications -> click on your instance name ->Click on "Production" tab on top -> Try making API call on this page by providing Query and Subscription key you got. If this works, go to the next step.
On the page mentioned above you would have seen Custom Configuration ID and Subscription Key. Make sure those two are same in your node.js code. Ideally this should work.
If it still doesn't work, please share your error code so that I can get better understanding of the error you are getting.

Authentication suddenly stopped working?

I am using the authentication API as directed here: http://docs.microsofttranslator.com/oauth-token.html
Everything was working fine for about a week and suddenly today at around 11:55pm eastern time, all calls to get a new token give 500 errors with the following stack:
http://pastebin.com/uQ3VL6Am
We simply make a POST request to https://api.cognitive.microsoft.com/sts/v1.0/issueToken
with header 'Ocp-Apim-Subscription-Key' set to our key
I tried using our second API key, and it still does not work. I tried regenerating another key, and it still does not work. Our account manager says that the account should be in good standing.
Thank you
This issue has been resolved by Microsoft as of 6pm PST 1/30/17.

PayPal: an error occurred in secure channel support

I'm trying to use the PayPal Express sandbox (which I have to over 5+ years) and all of a sudden, I'm getting this error. I'm running the latest Chrome on a Windows 2012 server that's up to date. It's happening on the first call to PP using SetExpressCheckout. Where do I start looking for the cause?
After a week of trying to get help from PayPal support, I accidentally came across this link: https://www.paypal.com/webapps/mpp/ssl-security-update that let me to the fix. Support never mentioned it.
The key is to actively use TLS 1.2 in your code. It's not enough to just have your server hardened (we were showing an "A" rating on SSLlabs.com). I put the following immediately before the instantiation of WebClient:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Connected to PayPal without a problem after that.

Gracenote Entourage Error 130/74

I first created my Gracenote developer account last night, and without issue, was able to match TV shows using the sample applications.
However today, I'm receiving the following error continuously:
ERROR GCSP: Hello error: [130] Please contact Gracenote ODP 06176 [Name: Mark Pringle] [App: Echos Imterface] support.
[Gracenote Error 130/74] (0x90160165)
Any help would be much appreciated!
The GNSDK error code is the last 4 digits of the hex number at the end. If you check out the gnsdk_error_codes.h file, you can see that 0165 is GNSDKERR_InvalidClientID.
Assuming you are still setting your ID correctly, I am not sure why such an error would be returned by the servers. I could hazard some guesses (maybe you went so far past your quotas that they blocked it?) but I don't really know.
Either way, I would recommend getting a new client ID from the Gracenote dev site and see if that works.
hope this helps!

Resources