Error 404 flight inspiration search test mode - amadeus

Im getting error 404 while searching flight inspiration search in test mode. Even is happening in the "try ot out" feature in the official web from Amadeus.

There is a technical issue with the Flight Inspiration API in the test environment. If you need to use the API before it's fixed, you can move your app to the production environment where it works as expected. In this environment you will receive a free amount of transactions each month just like in test.

Related

Accessing production key for Amadeus Developer Self-Service API

Has anyone be able to get a production key for the Self-Service API? I wasn't able to complete the form request, always throws an error at step 2.
Sorry for the inconvenience, Amadeus for Developers Self-Service is still in beta version. We are actually fixing this issue and making some improvments before releasing (in the coming days) the new version.
Changes are coming to the portal and the APIs that’s why it may not be perfectly stable yet.
EDIT
The new version has been released. You can now move from the test environment to the production environment.

Getting error when executing smartjmx through jmeter for ecommerce site

I have recorded the smart jmx of ecommerce site with blaze meter but when i'm using the same file in jmeter getting error's. It's working fine till add to cart, when it processing the customer information throw exceptions.
image
SmartJMX is a commercial third party tool by Blazemeter and its code is non public.
As such it's impossible to help you, so you should contact their support to report the issue.
Most probably your issue is due to:
Missing correlation not detected by SmartJMX
Wrong correlation done by some extractor added by SmartJMX
You can debug this using JMeter View Results Tree and Debug Sampler or Debug PostProcessor and comparing a recording with a play of your script to see what differs.

RROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support

We are in the process of implementing Success Factors LMS, and trying to play and view SCORM compatible files exported from Adobe Captivate 8 and 9 in Success Factors LMS.
I get the message - 'ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support’
I have tried SCORM versions 1.2 v3 and 2004 V2 and V4. We can view the content, however it does not track, show as complete etc.
We are also producing Scorm compliant files using Skillcast and Articulate, but we still hit the same issue, we can view the content after closing the API error window, but still does not track.
Anyone experienced this problem before? Or know of a fix?
Many thanks
Normally this issue comes up when the course is unable to get the SCORM API from the LMS...I have seen a ton of SCORM content running in Success Factors before, so I wonder if the issue is in the setup. Are you seeing any "Access Denied" type errors in the browser element inspector/developer tools? I wonder if the course just can not find/have access to the player window. If the course is launching in a new window, you may want to try launching it in the frameset. I have seen folks get around this issue by making sure the player and sco are in the same window...
If you wanted to rule out the content being the issue, you can always test your content in the SCORM Cloud's free sandbox (https://cloud.scorm.com) to make sure the course is properly asking for the API...
If you have any other questions, we would be happy to help...you can just shoot us an email at support#scorm.com.
Thank you!
Joe
The error occurs because the content is not speaking to the Learning Management System (LMS). The code that runs to initialize the session doesn't happen. There is no return "ping" from the LMS.
You will get this error when you publish in SCORM and run from your desktop, or from a web server that isn't connected to an LMS. If it occurs when you are launching from an LMS it can either mean that the SCORM API isn't configured correctly, or your content server is on a different domain (cross-domain) than your application servers.
To test, you should try launching your content in different browsers. Our system was configured in such a way that Firefox and Chrome read our content to be cross-domain issue, and threw the SCORM API error, but Internet Explorer worked just fine.
In the end, it was determined that our server configuration in tandem with our firewall and security settings read the Content server as cross-domain and we had to redeploy our content servers within the firewall.

Since today: Google 500 Error

I get 500 Errors when I redirect my users to the OAuth Endpoint from Europe. Has anything changed? It worked for several months
I also don't have the rep yet to comment. But I have been noticing this issue today also.
All of my sites that use Google oauth (different tokens) are returning 500 errors after choosing the google account you want to log in with.
500. That’s an error.
There was an error. Please try again later. That’s all we know.
I checked the status page and I don't see any errors or any other reports of this https://status.cloud.google.com but it seems there is something going on since at least a few of us are seeing this. I have tried from multiple computers on different networks, and I had a friend try on a different google account and had the same issue. I am using the following gem in a rails app:
gem "omniauth-google-oauth2", "~> 0.2.1"
Edit: That page has now been updated with an notice on the bottom.
We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific.
I can't post a comment as a guest but I have been noticing this as well. I have found that several refreshes sometimes bring up the authentication window, but I haven't actually been able to authenticate and connect yet. I am on the Eastern coast of NA trying to access GMAIL api.
This started to happen to me this afternoon , it will occasionally work but most of the time it doesn't.
I have read this may be because you must now past through the oauth_verifier which has only just been changed, although it should not have just yet.
Source GarretMurray - https://twittercommunity.com/t/oauth-access-token-stopped-working-today/1630
He said that after adding the verifier it started to work again !
I also experienced this, but the problem seems to have been resolved by Google. I observed the errors happening on our application from roughly 13:42 - 14:28 UTC.
As per https://status.cloud.google.com/
"We are investigating an issue with Authentication services. We will provide more information by 07:30 US/Pacific."
There is also subsequent post specifically on the Google Cloud App Engine service regarding this outage available at https://status.cloud.google.com/incident/appengine/16003.
Sources: See above.

Web application Testing

Hi guys i have developed a web application that is hosted on client side test server, i have to check the response time of each page (loading) but i cant install any tool on the test server totally confused. guys give some idea.
Use FireFox and the Life-Of-Request info plugin. It will tell you how long until first byte, how long to display entire page. How many requests were made. Other stuff.
https://addons.mozilla.org/en-US/firefox/addon/lori-life-of-request-info/
Does this need to be automated or can you do a one off for a few pages and call it a day?
FireBug add-on for Firefox (http://getfirebug.com/). It will help you with quite a few things related to web app development / testing. Specifically page response time can be tested in Net panel of FireBug: http://getfirebug.com/wiki/index.php/Net_Panel.