Microsoft JScript runtime error: Invalid origin: https://s-static.ak.fbcdn.net

Question

0.00/5 (No votes)

See more:

C#

ASP.NET

Javascript

, +

when I run my program that I write sometimes visual studio gives me this error:

HTML

Microsoft JScript runtime error: Invalid origin: https://s-static.ak.fbcdn.net

what should I do?

It shows me some code and part of that is :

$(window).bind("message",function(e){if(!e||!e.originalEvent){return}if(e.originalEvent.origin!=="chrome://browser"){throw new Error("Invalid origin: "+e.originalEvent.origin)}var f=JSON.parse(e.originalEvent.data)

Posted 10-Dec-11 20:36pm

kitykity

Updated 11-Dec-11 2:33am

v5

Add a Solution

Comments

Member 8604353 29-Jan-12 7:57am

Microsoft JScript runtime error: Invalid origin: https://s-static.ak.fbcdn.net

what should I do?

It shows me some code and part of that is :

$(window).bind("message",function(e){if(!e||!e.originalEvent){return}if(e.originalEvent.origin!=="chrome://browser"){throw new Error("Invalid origin: "+e.originalEvent.origin)}var f=JSON.parse(e.originalEvent.data)

Nolensville 27-Nov-12 12:47pm

Did you ever get an answer?? I just updated to visual studio 2010 and am getting this error too.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nolensville · Answer 1 · 2012-11-27T08:37:00

After a long day of googling on the issue, I was able to get rid of the java script by disabling the ask toolbar in internet explorer. I don't know if that will be the solution for everyone but from researching the problem it does seem that most had the error coming from dynamic java script created by the browser and not a java script for the application that they were working on.

To disable the ask toolbar go into internet explorer. On the internet explorer menu choose tools and then choose manage add ons. Once the wizard opens choose the toolbars and extensions I choose the Ask.com toolbar in the list of items and disabled it.

Details for those that may have a different widget causing the error:

How I got to that is I found out that static.ak.fbcdn.net stands for static akamai facebook content delivery network. For even big webservers, many times it isn't efficient to have common items like the facebook logo or ads from facebook.com. Akamai (and others) have built efficient content caches all over the world that route to the closest to you (network wise) cache. This in theory makes things faster as you hit a local cache, and lowers the hits on facebook.com, making it faster too. The domain fbcdn.net is actually run by Akamai, on facebook's behalf.Other websites probably have a bit of HTML/Javascript code hitting 'facebook' but in reality hits facebook and the facebook akamai servers as well.

In googling on the issue today, I had come across this:
"Running a multisite and for some reason the widgets do not work in Internet Explorer however they work fine for Firefox.
I just updated everything to see if that would fix and still no luck.
Any ideas on what to do?"
The solution for that problem was:
"Sounds like a javascript issue (which IE is notorious about anyway). Try deactivating the plugins one at a time until things begin working and you'll have found the culprit.
You can also quickly deactivate all plugins and see if everything works - then you'll know it's a plugin and can go one at a time to find it."

In the visual studio 2010 when the debugger broke for the error. I notice that the "https://s-static.ak.fbcdn.netcdn.net" was part of widget being created by Internet Explorer. Clicking on the widgets properties in debugger revealed the URL: "http://apnwidgets.ask.com/widget...." Since I don't use the toolbar, I went in and disabled it. This stop the widget from being made which also stopped the offending javascript "ticker_37.js?build=202" from being built and executed.

Cheers and Hope this works.