Stupid bloody owssupp.dll

I am suffering a common problem still, despite uninstalling Project 2003 previously to try to fix a dll clash.

My system was working fine. I could open and edit documents from SharePoint just fine. Something broke it – and I believe (as in the article at the start) that that was Windows Update.

Now when I try and edit a document, I get the error

‘Edit Document’ requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater.

Which is annoying, as I have this. I looked up the knowledgebase article, followed the instructions, and ended up trying to register/unregister the dll. Except that I can’t. When I try, and I get the error

The module “owssupp.dll” was loaded but the call to DllUnregisterServer failed with error code 0x80070716.


This exit code means that “the resource name specified cannot be found in the image file”.

Ooookaaay. Risking my geek credentials, that is gibberish to me. Uninstalling and reinstalling SharePoint Support in the Office features did not fix the problem for me.I think I’m looking at a full Office reinstall. What a load…

Stupid bloody owssupp.dll

22 thoughts on “Stupid bloody owssupp.dll

  1. Casey says:

    So after trying all suggestions, uninstalling and reinstalling Office 03, etc etc; I noticed the user had IE7 installed. Uninstalled IE7 and rebooted, now the user is able to edit sharepoint documents normally.

  2. Weird. Had the user installed any ActiveX controls – e.g. Project Server support? I think that might have been what screwed up my system.

  3. Kyle says:

    I have tried absolutely everything to get this to work, short of uninstalling IE7 like Casey suggested. I went into IE7, to the Internet Options, then to the Advanced tab, and clicked Reset. After IE7 was reset to default, it FINALLY worked for me.

  4. Really weird. It’d be interesting to see what it is resetting. I might give that a go – although my system has mysteriously started working…

  5. Bill Anderson says:

    Well I wish mine would mysteriously START working the same way it stopped. F*ck I hate these MS updates. I am always having things that used to work stop working
    I have a 3 month old Windows 7 installation and sometime within the last month I can no longer edit shrepoint files. I get exactly the same messages as Andy


  6. mike m says:

    Not sure if this would be help for people or not, but here is some unsupported help….

    Problem here – IE crashing, control not displaying (i’m not the sharepoint guy here), general all around badness. Problem started when PC’s with Office2003 had Outlook 2007 installed.

    Did loads of software monitoring and found that the Office12 owssupp.dll file was getting loaded even though Office11 really had the dll’s that were needed.

    Decided to poke around in how it found the DLL’s and found the below registry key pointing to the Office 12 owssupp.dll, changed it to Office 11 (see key below) and so far (knock on wood), we seem to have the best of both worlds. I’m in the middle of trying to figure out if I broke something else, but haven’t found anything yet.


    I’m sure people all having different issues, but if you want to alter how that owssupp.dll loads, then that reg key is where IE manages to find it.

  7. Robert Kenney says:

    Just an FYI – I have also had a problem with using the SharePoint edit tools from IE on
    my new 64-bit Win 7 laptop.

    It turned out that I could use them from the 32-bit version of IE, but NOT from the
    64-bit IE. Before you throw the baby out with the bath water, try using the
    32-bit version of IE(assuming you’re on a 64-bit version of Win7 or Vista, etc.)

    32-bit in C:Program Files (x86)Internet Exploreriexplore.exe
    64-bit in C:Program FilesInternet Exploreriexplore.exe

  8. I feel like I’ve tried everything and this is still happening with a customer. So far, I’ve uninstalled Office 2k7 and reinstalled. Then I checked to make sure that I wasn’t a doofus and enabled SharePoint support. It was already enabled.

    Then I deleted the owssupp.dll file and ran a diagnostics. It automatically replaced that file and so I tried going to the page where they access that multiple docs area. It starts to load the blue link text for it and then after that it disappears.

  9. I’d like to give my resolution, if it helps anyone.

    Win7; Microsoft Office Professional Plush 2007; IE8 (32bit and 64bit)

    After trying a few of the things already mentioned in this post I ended up doing the following things that eventually got things working:

    – I “Reset Internet Explorer settings” in IE
    (Don’t think it does much to help, but just in case)

    – I did a Windows update; installed various updates and the big ‘Win7 Service Pack 3’
    (Again, I don’t think it does much to help, but just in case)

    – Repaired Office ’07 (through Programs and Features / Uninstall programs)

    – Restarted

    (Tried with IE8 64bit and didn’t work)

    – Tried with IE8 32bit (“Program Files (x86)Internet Explorer”) –It worked!

    Good luck.

  10. Kumar says:

    General Fix:

    Start with trying IE 32 bit – Program Files (x86)Internet Explorer if your OS is 64 bit.

    If this fails, try registering owssupp.dll (I understand that, in your case this has failed)

    If this fails, try running the windows sharepoint services support.

    If this fails, try repairing the MS office.

    If everything fails, you know what to do, don’t you?

    Best Wishes

  11. Rich Van Rooyen says:

    Hmm… I just spent a pile of time messing with this…
    Little hint…
    Windows 7 64bit… Office 2010 32bit… Internet Explorer 32bit.

    I don’t understand it, but I ran from the 64bit version of Internet Explorer and the “Connect To Outlook” options in the SharePoint Website worked fine…
    Thanks to Robert Kenney for the tip on x64 bit vs x32 bit.

  12. Larry W. Virden says:

    So. today this problem appeared on my work desktop. It is 32 bit, Win XP, and I am using the 32 bit IE 7 (where I am stuck for the moment). A few months ago, Office 2010 was installed. In the last week, out of the blue I first had a popup appear when I would try to use the SharePoint 2007 browse user widget. The popup from IE said that the page had a broken script. However, other people used the page just fine. Tracking down some action for that problem led me to a note on a web site suggesting that one run ie with all add-ons turned off to see if the problem went away. It did. I tried disabling some of the add-ons and that too seemed to resolve the problem. Then today I noticed word started warning me that there was a security issue and that add-ons were turned off. Then I started getting the stupid message about needing a windows sharepoint compatible application. When I went into word’s file option, there was a button to check for issues. When I clicked it, it told me that there was a dll in the office 12 tree which had a signature that wasn’t approved. So I began a virus scan to check things out to see why suddently this dll would appear without a recognized signature.

  13. Tom King says:

    You guys will love this. Mine gives this error, but just sometimes. If I click on the document title, it loads into Word just fine. If I click the arrow next to the title and choose “edit in word” then I get this error. I also get the error if I try to edit the template in advanced settings. Makes no bloody sense.

    Running Win 7, SharePoint 2010, Word 2010.

    Is it my imagination, or do Microsoft products have an increasing number of weird pointless errors? I’m getting tired of it.

  14. Gavin Thomson says:

    This is mighty frustrating. I took delivery of a new laptop and this issue is causing no end of trouble as we store all our documention in Sharepoint.

    I’m running, Windows 7 Professional, 64 bit version, Office 2010.

    It just won’t give the option of opening in Edit or Read Only. Why is this so hard for Microsoft ?

  15. Morgan Thevarajan says:

    In a SharePoint web site, click Actions – “Connect to Outlook” and wait approx. 30 seconds for the fix to take.

    If the above fails, use OFFCLN.EXE to get rid of old MS Office files even if you are using Office 2010, etc. and then repair MS Office.

    The Office 2003 Editions Resource Kit (ork.exe) is available as a download and includes the same stand-alone Removal Wizard (Offcln.exe) that is included with Office 2003. You can find this downloadable file on the Office 2003 Resource Kit Downloads page.

    I would also uninstall any old versions of Java and then install the latest version although I don’t believe Java is the culprit.

  16. I know this post is ancient, but the information is still relevant and the problem still exists for IE 11 and Office 2010 (and probably later). Mike M triggered on the clue that I used to solve my problem:

    I opened REGEDIT and searched for all instances of OWSSUPP.DLL. Every reference to this file that was not in the Office14 folder was changed to the proper Office14 folder. I’m sure only one of the dozen or so entries I hacked this way made a difference, but it worked.


  17. Dan Nobles says:

    Well I’m at my wits end with this. I’ve tried everything listed here. We are running Office 2010, IE11 and Office365 for Outlook. I *suspect* that when the files were pushed out to upgrade to Office365 is when the issue started. I was able to edit the registry entries as shown above…this was actually the gold goose I was looking for. It FORCED IE11 to pull the OWSSUPP.DLL from ver. 14 instead of 15 which I thought would do the trick, but no luck. Maybe I will try to change all the entries to 15 instead of 14 and see if that helps. White flag about to go up…this is stupid.

  18. Read says:

    If you are using a “64-bit” version of XP/Vista/Windows7 then there will be two Office12 directories:

    1) C:\Program Files\Microsoft Office\Office12\


    2) C:\Program Files (x86)\Microsoft Office\Office12\

    What I did was copy the owssupp.dll from 2) and put it in 1) and restarted the browser, and voila! Working sharepoint documents!

    I found a solution,it works,maybe you can have a try.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.