Skip Ribbon Commands
Skip to main content

Quick Launch

 

 Important Posts

 
 Complete MOSS Licensing Info
 SharePoint Speak Terminology Dictionary
 SPCAP - SharePoint Capacity Planning Tool
 Step-by-Step – A REAL world upgrade of a SharePoint Portal Server 2003 (SPS) farm to Microsoft Office SharePoint Server 2007 (MOSS)
 Best Practice - Determine if a SPUser has Admin rights to the SPWeb
 SharePoint 2010 - Good, Better, Best
Cornelius J. van Dyk's SharePoint Brain Dump > Posts > How do I – Fix the problem where IE crashes when opening Office documents on SharePoint?
June 18
How do I – Fix the problem where IE crashes when opening Office documents on SharePoint?

OK, this one has several pieces out there in the blogosphere and some more on the newsgroups, but I've not seen a comprehensive post that clearly stipulates why the problem occurs and how to fix it.

Why?
OK, so first the why. Why does IE (both 6 and 7) crash when I try to open an Office document (Word, Excel, PowerPoint etc.) on SharePoint (WSS or MOSS)?



When you try to use the "Edit in Microsoft…" option for a document it always blows up.
Sometimes this is also seen when you just simply click on the document which would then open in browse mode.
Either way, instead of seeing this:



Friendly little warning, you see this:



Ugly "The exception unknown software exception (0xc06d007f) occurred in the application at location 0x7c812a5b." error message.
When you click the "OK" button, you get another error message, the "The instruction at "0x30cb05e4" referenced memory at "0x00000000". The memory could not be "written." error.



Well the problem started when you installed a brand new shiny Office 2007 application. In my case, I was working on migrating us to MOSS 2007 from SPS 2003 and installed SharePoint Designer 2007… and that was enough to break my system.
The underlying problem occurs in the OWSSUPP.DLL file located in the C:\Program Files\Microsoft Office\Office12 folder.
After much research and debug tracing with Joe on a Microsoft Premier Support ticket I had opened for this, we discovered that OWSSUPP.DLL actually calls, down the line, the NAME.DLL which, installed with Office 2007 apps, are incompatible.
Anyway, to make a long story short, reverting back to the old version of OWSSUPP.DLL will solve the problem.

How?
OK, so here's how you fix it. NOTE: This fix will only work until you install another Office 2007 component at which point you will need to redo these steps again.

  1. Open Windows Explorer and navigate to C:\Program Files\Microsoft Office\Office12.
  2. Locate the OWSSUPP.DLL file and rename it to OWSSUPP.DLL.OLD.

  3. Now navigate to the C:\Program Files\Microsoft Office\Office11 folder.
  4. Locate the OWSSUPP.DLL file and copy it.

  5. Now navigate back to the C:\Program Files\Microsoft Office\Office12 folder.
  6. Paste the OWSSUPP.DLL file from the Office11 folder to here, the Office12 folder.
  7. Open a command prompt window with Start/Run/cmd.
  8. Chance directory to the Office12 folder with CD "Program Files\Microsoft Office\Office12".
  9. Now using REGSVR32 OWSSUPP.DLL re-register the DLL file.

  10. Now here's where the trick come in. You will receive an error message like this:

  11. Pay the error no heed. The registration worked. Go back and attempt to edit your Office document on SharePoint. It should work without any problems.

Later
C

Kick it Fave it Digg it Reddit Del.icio.us

Comments

dmckenzie@nfa.futures.ANTISPAM.org

We had this same problem running Office XP with FrontPage 2003 (or Visio 2003, or Outlook2003) and  WSS V2,
The reregister DLL did not work there... we would periodicly have to reinstall Office XP after any maintenence which touched Xp or 2003.
All 2007 with WSS V3 now and happy.
Sorry to hear that the multi level OWSUPP issues are still not resolved.
 on 6/19/2007 6:12 AM

http://www.cjvandyk.com/blog

Yeah, I'm disappointed that it is still around too.
The GREAT news is that I have a patch from Microsoft which we are testing right now.
If it tests OK and passes their internal regression testing, it will be available to the public by month's end! :-)

Later
C
Cornelius J. van DykNo presence information on 6/20/2007 1:39 AM

TJ@Chariot4BI.ANTISPAM.com

Worked like a charm - Thanks!!!

TJ Doherty
www.chariot4bi.com
 on 6/20/2007 2:53 PM

Roger Lamb

A simpler fix would be to goto Start->Office->Office Tools->Microsoft Office Diagnostics .. run the diagnostics and it should resolve this problem.
 on 6/20/2007 4:30 PM

http://www.cjvandyk.com/blog

Hey TJ,

Glad I could help out! :-)

Later
C
Cornelius J. van DykNo presence information on 6/21/2007 3:14 AM

http://www.cjvandyk.com/blog

Hey Roger,

Yeah, that works as well... sometimes.  The same as doing a Repair Install of Office 2007, yet another suggestion that's been made by MS Support.
The problem we ran into was that neither of these two fixed our problem every time... but this hack is yet to fail me. :-)

Later
C
Cornelius J. van DykNo presence information on 6/21/2007 3:18 AM

carol@preferredsales.ANTISPAM.com

Worked like a Charm!  You ROCK!
 on 6/21/2007 11:45 AM

http://www.cjvandyk.com/blog

You're welcome Carol! :-)

Later
C
Cornelius J. van DykNo presence information on 6/22/2007 2:42 AM

dave.chan@draftfcb.ANTISPAM.com

This worked like a charm after I performed a stupid patch of the Office product.  Now.. a question ..
How come I have to reboot my WSS or MOSS servers every so often when I am not able to open the file from the document library.  After the reboot, it is fine.
 on 6/29/2007 12:43 PM

http://www.cjvandyk.com/blog

Hey Dave,

I'm glad it worked for you.
As for you having to reboot your servers, how often is this happening for you?

Later
C
Cornelius J. van DykNo presence information on 6/29/2007 3:39 PM
1 - 10Next

PLEASE NOTE
Comments are moderated so posting your comment here, will NOT make it visible right away.  Once I've reviewed your comment, I will publish it for all to see.  This is unfortunately needed in order to deal with all the crapware and spambots that post to my blog on a regular basis.

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.

Your Email or Blog URL *


Body *


Attachments