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!
Related
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.
I've been using the bigrquery library in r to run queries on my google big query project for the past 6 months. This morning I ran a simple query_exec() command that I've run a number of times over the past few days and I got the simple message "Error: Invalid Credentials".
I haven't been able to find documentation telling me how to fix this. I'm also not sure how to give code that will recreate the error.
The only thing that I can think of that changed is that I signed into a different gmail account.
Steps attempted so far:
I logged out of the gmail account and logged back in to the right one.
I uninstalled everything about R on my computer and reinstalled it all.
Still no luck.
I'm also realizing that there isn't a ton of information here.
If there's something else I can provide that I haven't thought of I will be happy to answer questions.
Thanks for any help you can provide.
After more searching I found a way to clear your access credentials in this question and answer: BigRquery - RUN_QUERY_JOB
To summarize, if you force the access credentials to be null set_access_cred(NULL), then get new credentials get_access_cred(); you can re-authenticate.
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.)
I am working on php . I submit my transaction to paypalsandbox
but transaction is not completed and gives error
An error occurred while processing your request. Before submitting this again, log in and check your Account History to ensure that the transaction didn't complete.
If any one know the solution please help me.
Thanks
I'm having this in testing too. It was working about 9 hours ago, and as I'm testing from 3 different servers with two different configs, it may be that it's a PayPal issue rather than a user error.
Later:
Found this which suggest it happens from time to time. I'm seeing this error now, rather than the one reported previously.
https://www.x.com/content/resolved-intermittent-errors-during-checkout-sep-21
I'm getting the following the error message in my content delivery logging:
com.tridion.smarttarget.utils.AmbientDataHelper - can't find defined
trigger-types in claim store (check if your smarttarget cartridge is up and running)
I've checked out my smarttarget_conf.xml and have confirmed the web services are up and running. The one that is failing (or returns a 404 via broswer) is the following:
<Endpoint>http://servername:8180/fredhopper/config/trigger-types</Endpoint>
But having read through the documentation and the forum, i'm under the impression this is correct and that the url doesn't respond to GET requests.
So I'm assuming everything is set up correctly, in my smarttarget_conf.xml, I'm hoping is anyone has some pointers for me to have a look into to resolve this issue.
Thanks in advance.
Solution
The issue here is that my trigger-types.xml file was not correctly formed on the FAS (Fredhopper server). I'm giving Jeremy the winning answer below as he spotted my issue behind the scenes.
Thanks Jeremy - I hope anyone reading this up-votes your answer
The port of my local SmartTarget instance is 8180, not 8080. Perhaps this is the same for you?