“No such interface supported” error in IE9 RRS feed

  • Question

  • We have a web application which sometimes displays error "No such interface supported". Error occurs irregularly at various parts of application and it seems impossible to reproduce it when testing. This issue persists for several months now, initially there were a few errors a month, but frequency keeps increasing and now we get a few errors a day.

    Clients use Windows Server 2008 and IE9 (9.0.8112.16421).

    We have tried installing updates, reinstalling IE, registering several dll libraries and also running script from , but none of those solutions has worked so far.

    Does anyone have any idea what could be cause of this problem and how we could solve it?

    I have already asked this question on stack overflow (, but without any success.


    Tuesday, March 14, 2017 9:12 AM

All replies

  • Hi,

    Lukas, nobody can help you without a reproduction url or at least the error message text.

    If possible, please include links to any website you are having problems with your questions, also the full text of any error messages you receive (IE9 includes a Copy button on the message). The scripting error message also includes the module name and the line number where the error occurred. Ask/instruct your users to take a screen shot when the error occurs.


    irregularly at various parts of application and it seems impossible to reproduce it when testing.</quote>

    The fist step in troubleshooting web browser issues is to test in noAddons mode (Start>Run>iexplore.exe -extoff )



    If you have an oldish version of Office installed, you could try disabling the Office Discussion bar and the Office Research Explorer bar, from Tools>Manage Addons>Show All Addons.
    Tuesday, March 14, 2017 8:12 PM
  • "No such interface supported".

    Did you try a search at StackOverflow too?

    (search there for
        "No such interface supported" javascript

    I guess that's where you got the idea to do some regsvr32 commands.  However, none of those commenting seem to understand how critical it is to be doing this elevated (e.g. in an Administrator Command Prompt), doing it with the correct switches and doing it for both platforms.   These points are covered in both Kai's instructions for applying ie-rereg and in a Support article (which is always extraordinarily difficult to find)...

    OMG.  BING is learning!

    (BING search for
        blank tab regsvr32 ieproxy

    It's interesting that ieproxy is mentioned by the StackOverflow posters for this other symptom.

    Otherwise, try to figure out if you can get some better diagnostics somehow for your incident reports.  E.g. in earlier versions of IE there used to be a UI available to end users to do this.  Lately that feature has been removed but I think equivalent functionality is still possible via the Developer Tools.  Otherwise perhaps you will have to ask interested users to look for system logging or even activate tracing in order to get a better symptom description for you.

    Good luck

    Robert Aldwinckle

    Wednesday, March 15, 2017 10:07 PM