HI,
We created a web application which is running in many web servers. One of the server was recently updated. When they request the web page which usually streaming PDF content, the alert message displayed and return back to last page visited.
The alert message has the title: Windows Internet Explorer
Alert message is "The System is experiencing problem that requested for support".
We never faced this exception. Can anyone help me?
Thanks,
P.Gopalakrishnan.
grep your source code for the message; it's probably raised by javascript in your app.
What happens when this problem occurs? Does the browser crash?
I've seen this sometimes with IE. I don't know why. It has happened when dowloading Excel spreadsheets, but it has also happened when downloading code from SourceForge.
Related
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.
I'm trying to reach TestFlight on iTunesConnect but it keeps only the loading spinner and do not show anything. I've tried with Chrome and Safari without success.
http://prntscr.com/8sv799
In my other application on the very same account everything works correctly.
I've already written to support waiting for their response.
My issue was resolved from the support team. They didn't provide me full details what caused this, however after sending them needed information(including page source code) they fixed it on next day.
So if you experience the same, I advise you to contact them(via iTunesConnect).
I implemented the ShareScreen of Web RTC.
But when "Choose Share Screen" popup opens,few of the windows keep flickering and show blank content (black screen) most of the time. On selecting one of those windows and doing screen share, the peer also gets the same flickering.
Please help. I have attached the image link which shows the problem https://webrtc.googlecode.com/issues/attachment?aid=43840000000&name=Screenshot.png&token=ABZ6GAdcyh_dpvmXdbR02t3LX72wbfE4Qg%3A1425623918522&inline=1
Regards
Raghav
Please check your signalling server. This error occurs only when something wrong in your signalling server. Similar kind of error occured to me. I used nodeJS. Sometimes handshakes may be established, but data have to be transferred for sharing.
For instance check whether the request and response is prompt.
This is a known issue in Chrome on Windows:
https://bugs.chromium.org/p/chromium/issues/detail?id=613987
Try to migrate to FF or to Linux...
My SL application is commercial and working just fine on hundreds of machines.
SL is using a WCF service and it works as expected, but today I observed behavior on client machine, where literally no call is made to server.
After you click button that sends a call, some error occures, and no record about WCF call is created in Fiddler.
Error is:
[HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable...
I read about this error that people recommend to use Fiddler, but as I say there is no call displayed in Fiddler
So problem is worse than I thought initially.
It comes and goes. Currently we have found a working solution that fixes the problem after it appears although it doesn't make any sense to me.
For example if I get this error in chrome & mozilla & OOB version,
launching a program in IE works, and after that chrome,mozilla & OOB
start to work too.
Thing is that same people who had this problem solved with this workaround experience it again in some days, like a week, with no apparent reason, and then combination of launches from various locations helps (usually IE helps the most).
Any help appreciated, I start a bounty as its pretty sick bug and I need to fix it somehow.
Update
Weird IE fix scenario:
At some point OOB version gets into state where it doesn't send any WCF request to server.
(fiddler doesn't see it, server doesn't gets it).
After launching web version in IE, and hitting the same button, that sends WCF request we get desired result in IE web version.
Without changing anything else, just relaunching OOB version which was in this buggest state before, makes OOB version work correctly. Its not reinstalled, not changed - nothing.
This is what I call "IE cure" of this problem.
So the question is what can IE launch potentiall change for OOB version?
According to this thread the message Debugging resources are unavailable appears when de client is not using the the Silverlight Developer Runtime.
This means that the actual exception is hidden from you (and us) so the next step is to reproduce the error on a system that has the Silverlight Developer Runtime.
I found this article. It might be worth it to check the certificate you are using (are you using a certificate) It is one of those things that is different with OOB apps and browsers.
I was wondering if anyone could point out what is causing the problem in the screenshot attached. It has happened a couple of times with different images. I can't see what is causing it.
The machine is my development machine.
I was hoping to post this on serverfault but I can't add the image I need.
Not enough info yet, so just some debugging steps.
Try uploading it to a different machine and see if you get these same messages.
Check you don't have any Javascript doing anything with image urls - to me it looks like some loop somewhere might be going 'wacko', but could be client or server side.
Use tail -F on it in the terminal and refresh the page to see if the appearance of those entries coincides with the loading of the page.
Edit: maybe also have Firebug/etc open when you refresh the page with their Network panels open to see if you really are sending those requests. Really just want to find if it's a client or server issue to begin with.