My app has been working fine since I changed my free account to a Pay-As-You-Go account but yesterday I started receiving the Access denied due to invalid subscription key error
I haven't changed anything. What can be the source of this error?
Microsoft CRIS servers were experiencing down time starting from ~ 10 pm GMT (according to my observation) on Wednesday 04/19 till 9 am GMT Thursday 14/20. I've experienced problems with log in, deployment access. But some of their servers went back and I was able to log in console. However all my deployments weren't accessible including newly created one. So, as their system went down, you might have problems accessing your deployment. Even if error description is related to invalid subscription key, it might be that issue. It's a new service and I still see 500 Internal errors in console often. If issue is still reproducing, I recommend you to contact their support team crservice#microsoft.com. They are very helpful. However they respond during European working hours.
I have experienced similar issues when we hit the API limits. It would not be a bad idea to check if either the number of requests per second or the volume has been reached ( in case of bootstrap keys it is 1000 hits)
Related
Yesterday, about 1500 PST, my connection to the translation API began emitting errors about exceeding:
Error 8: RESOURCE EXHAUSTED: Quota Error
Quota exceeded for quota metric ‘v2 and v3 general model characters’ and limit ‘v2 and v3 general model characters per day’.
I have googled online, and found this can happen, and that it resets at 0000 hours PST. This time has come and gone, and second day now, the same Error 8 is arriving when attempting to access the service.
I have also signed in to my console, and looked at my quotas. None of them are over-quota, or have they been in the last 7 days. (I’m no where near the limits)
I had a spike (bug) where the code got into a bad state and spammed the API retrying the request, and I’ve found an fixed this issue. This was yesterday, so I don’t know why it’s still giving errors.
OK so I found the answer. My credit card had expired, and the billing was overdue. Unfortunately this is not obvious in any of the errors, or many of the pages the google search results point to (check quotas etc)…hopefully this helps someone else who searches.
As of yesterday, when I publish the (current) Product and its API, the deployed Assembly is not updated and what is running is from an earlier state - most likely from early December. The APIC domain was created at the end of Nov, so what I is deployed could even be the initial deployment.
As a test, I changed the API's description (add 'XXX') and changed a Gateway script to add XXX to a 'console.warn' at the start of the Assembly. The description change can be seen in Portal, but there is no 'XXX' visible in the DP log. I set DP log level to 'debug', but none of the 'tracing' statements added in Dec can be seen.
Does anyone have any ideas as to how I can resolve this? Or, how can I see the API's deployed code? I've looked in the DP File Management, but everything is dated at then end of Nov.
[EDIT]
Catalogs are in Dev mode, so I change and publish using same version. I have just done a series of tests using the api referred to above (VAT-Num-Check) (which is our first 'real' api) and an older trivial one that just divides two numbers. The Sandbox catalog is associated with the DEV gateway, and the SIT catalog, with the SIT gateway.
The other kind of corruption is, after deploying a new api, calling it results in 404 'No resources match requested URI'.
My conclusions are:
Something has broken in Mgmt server and/or DP APiC Gateway. Once code has been deployed to DP, it can't be changed or deleted. Changes in Portal are correct.
The possible exception is that the deployment of the VAT-Num-check API appears to have reverted to an earlier version after a CLI publish to the SIT Gateway this morning.
[/EDIT]
Background:
I have been creating a Windows script to publish draft Product/APIs and then run Postman tests. This means that I have been performing a lot of publish actions to DP (V5 type). On Monday evening, in my last run, the Postman tests all worked. Yesterday morning, some failed.
Back in early Dec, I made a change so that all JSON error messages in user responses used error as the 'prefix' to the message contents. Before that, some used message and some used reply. The reason for the failures is error messages have reverted to using the earlier 'prefix'.
API Connect 2018.3.7 went out of support on November 15, 2018. You'd need to upgrade to 2018.4.1.x, which will be supported for a longer term.
If you still have the issue at that point, then please open a support ticket for further investigation.
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.
Every morning between 8 and 9 am CET my site shows this error:
Error Over Quota
This application is temporarily over its serving quota. Please try again later.
although billing is enabled and the site has been running for many months now. On the old billing status page, there's a setting for Maximum Daily Budget (Set this to handle peak traffic and to buffer against sudden traffic surges.) which is set to $0.00, but even if I change that to e.g. $10.00, it still shows the 503 error, so it seems this has nothing to do with it.
The new billing page looks like this:
It happens every morning between 7 and 8 am CET, so that would be around midnight PST which would at least indicate that it still might have something to do with billing?
Here's how the external monitoring system shows the outages, i.e. multiple outages every morning and then no problems for the rest of the day.
The Google Developers Console Overview page Errors by status code also shows the 503 error in green.
If I look at the monitoring logs most of the 503 errors between 7 and 9am for the following pages:
/
/wp-cron.php
And then there are some 500 errors, e.g. at 8 am
08:07:08.092 ... [26/Nov/2014:23:07:08 -0800] "GET / HTTP/1.1" 500 0 - "Pingdom.com_bot_version_1.4_(http://www.pingdom.com/)" "www.coworking-radolfzell.de" ms=921 cpu_ms=1042 loading_request=1 exit_code=108 instance=00c61b117c9ad93b9da1f63314065ff8f4188095 app_engine_release=1.9.16
08:07:08.092 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application.
08:07:08.092 Process terminated due to exceeding quotas.
The (new) quota details page says Quotas are reset every 24 hours. Next reset: 1 hours and now it's 8:30 am CET. All of the listed resources are rated Okay.
If I go to the old Quota Detailsp page, though, I see that my requests' Frontend Instance Hourshave reached 100% and are rated Limited.
So I went back to the new console under Compute / App Engine / Settings which showed Your budget today is $10.00. Effective tomorrow, you will be using only free quota. which I now increased to a daily budget of USD 5.
My site now still shows the 503 error, but hopefully this will be the solution. I should be able to tell in 24 hours, shouldn't I?
If anyone from Google App Engine is reading this, there might be some inconsistencies between the old and new panels that should probably be fixed.
My problem has been solved by increasing the daily budget vom 0 to 5, although it took a couple of hours to take effect. We haven't had any notifications from the monitoring system, so it seems to be all fine now.
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