Been unable to access Fastlink via the 'Developer Info' tab as well as from 'TestDrive' using Google Chrome as my browser. I keep getting a 'Connection was reset' error within the iframe. Its not consistent behavior with some attempts allowing me to add accounts. Tried using another computer and seeing same issues (both on the same wireless network). Are there any known issues on Yodlee's side? Please let me know if you need additional information from me.
It seems like you were facing that issues temporary or intermittent.
In case if you still sees the issue, please do report to this on chat option available at developer.yodlee.com
Related
What is the issue with Cloudflare custom URL purge caching not working on different accounts? Bascially I have the account, and this functionality does work, but my colleague who lives in USA, I live in Europe, for her this does not work.
Can the issues be with account settings? Basically she gets the error or sometimes the cache does not want to work
I've faced issues in the past where features in Cloudflare was not working due to plugins or browser configuration. First you should confirm if the error is indeed coming from Cloudflare or from the browser.
Ask her to try to use a different browser and also a different device to confirm the issue is either tied to the account or to her location.
Try to inspect the page when performing the action to try and find out what's happening behind the scenes.
I commented this problem on the following thread for an active issue regarding Auth0 lock, but wanted to ask here for more reach in case anyone else has experienced this.
From what I've researched, it seems that many people are having this issue, and it doesn't seem like there's a known explanation to what's going on.
The unfortunate thing is that this is happening to end users, and from what I have seen devs have not been able to reproduce this error.
https://github.com/auth0/lock/issues/1838#issuecomment-918434321
Description
User is able to view our Auth0 Lock
User is not able to successfully sign up
We created an account for them in Auth0 directly and are able to log in using credentials we created for them via the Lock
User is not able to log in using the credentials and is shown the "We're sorry something went wrong when attempting to log in message"
Auth0 logs don't actually show this user's attempts/errors when logging in
Reproduction
Unable to reproduce locally, but trying everything we can to do so, including blocking all cookies (not the problem)
Attempting to get any console warnings from the user as well
Environment
Lock version: 11.30.4
React Version: 17.0.2
Next.js Version: 11.1.0
Chrome 91, Windows
I have installed maximo-anywhere version 7.6.3. This is just a development environment using the simulator with mobilefirst on eclipse.
I am currently unable to login with the following message. Not authorized when logging into Maximo Anywhere - on other environments I have created I have just given the user the correct security group... however in this scenario even though I have deployed the WorkExecution application and provided the user with the ANYWHERE_TECHNICIAN security group the user is still unable to login.
Any thoughts? Has anyone come across this issue?
Login failure
This issue is related to HTTP/HTTPS. It looks like anywhere is currently unable to go over HTTPS.
The error message was just a rogue message throwing it off.
Thanks
I have an issue while recording SAP BPC10 accessing with Netweaver with loadrunner 12.55. while recording, the event count is getting increased and I am able to navigate through application (excel sheet) but once the recording is stopped nothing is getting generated. similar issue with fiddler as well, it is not capturing any traffic. please let me know if anyone has faced this issue and how it got resolved. Thanks in advance.
I tried changing proxy settings and also there is no firewall placed in between my machine and server. I have followed sap document as well(https://www.sap.com/documents/2015/08/008b8186-547c-0010-82c7-eda71af511fa.html)
Record Winsock, see if you receive anything. If so, but not using Fiddler or an HTTP Virtual User, then you simply need to record a different protocol or use a different generation path, such as a Citrix/RDP/GUI virtual user to run excel.
Alternate path, grab Wireshark/Ethereal to take a look at the protocols expressed between your Excel add in and the next upstream architectural component for insight into how you should be developing your test code.
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.