JavaScript Error: No Such Interface Supported Solved

Friday, January 19, 2007 9:00 AM

Posted by Jonathan Danylko | Tag: JavaScript | Comments: 7 | View blog reactions

For everyone who has had problems with this JavaScript issue, I've found a solution!

If you've used JavaScript with Internet Explorer extensively, you know that there is a nasty little dialog box that shows its ugly head once in a while called "No Such Interface Supported" (NSIS).

Really informative error message, isn't it?

I was attempting to open a window using the window.open() method in JavaScript. Every time it tried to use the window.open() method, it displayed the NSIS error message. Grrrr.

Well, after ripping more hair out of my head, I came across a simple solution to the problem. The site isn't anything elaborate, but it solved my "No Such Interface Supported" problem completely.

Register two DLL's using RegSvr32: actxprxy.dll and shdocvw.dll. After you register those two DLL's, reboot your computer and try it again. The message should disappear.

Those of you who are getting this same error message, I hope the search engines pick this up and announce it wildly. It's an easy fix to a not-so-common problem.

 

Technorati Tags: , , , , ,

RSS LogoLike this article? Link to the RSS feeds to always get the latest posts.
What is RSS?

Related Articles:

Chatterbox - 7 Comments

1.  whalehead on Monday, January 29, 2007 5:48 AM said:

I guess I don't see how this is a real fix for a developer creating sites for the general public.  Sure, I can fix the issue on my local machine, but if I am developing sites for the public I cannot be sure they have these DLLs registered, nor can I realistically recommend they do it.

2.  architect.zero on Monday, January 29, 2007 7:24 AM said:

Very true, Jim.

I wouldn't recommend this option for public web sites, either.

I ran across this problem when I was developing an intranet application and I kept receiving this error locally, but not on the remote machine. The other developers were able to debug and run on their local machines without receiving this error. Everyone except me.

Thanks for the comment and sorry for the misunderstanding. :-)

3.  Jim on Monday, January 29, 2007 7:44 AM said:

Jonathan,

Thanks very much for the explanation of your scenario.  I can see the validity of the solution in the situation you describe.

Jim

4.  Stephen on Monday, January 29, 2007 12:45 PM said:

An easier fix for the local machine is to install and use Firefox.  It solves more problems too.

I've gone one step further, and installed Linux.  Then, Firefox is already installed, and even more problems are solved.  For one thing, I don't need a firewall.  For another, I don't need to constantly download virus definitions.

5.  Paul on Thursday, February 21, 2008 8:28 PM said:

Thanks - saved my butt after our company rolled out Microsoft Communicator to our machines and broke the javascript in our apps.

6.  Dennis on Tuesday, February 26, 2008 9:37 AM said:

I tried your fix and still have the same problem. I will try Firefox next as I am loosing my hair in clumps. For some reason I cannot explain I am getting no communication between Java and Windows.

7.  Philip Buendia on Friday, May 23, 2008 1:25 PM said:

Thanks for the fix.

 

Posting anonymous comments requires approval
and will not appear immediately.

Please Register or Login to post a comment.

 Post a Comment