The exception unknown software exception (a.k.a. SysFader)
Update 7/10/07: kerwin left a comment about a new KB article and hotfix that Microsoft just released. We tested it yesterday on a machine with both 2003 and 2007 Office components and it seemed to fix the error. Note that although both the article and hotfix specify WSS 3.0 / MOSS 2007, it also should work with 2.0/2003 (which makes sense, this is a client issue). Thanks kerwin for the information and to all the other people who left helpful comments.
—
You have to enjoy that helpful IE7 error message right? This past Monday I started getting an error everytime I tried to open an Office document from SharePoint 2003 (to be specific, a WSS 2.0 Team Site).
The exact error was:
SysFader: iexplore.exe - Application Error : The exception unknown software exception (0xc06d007f) occurred in the application at location 0×7c812a5b.
After some searching, I found only one related link on SharePoint University that was close to what I was seeing. It wasn’t much help and basically said to reload XP, not the solution I was looking for. I then started looking into the IE7 add-ons (Internet Options -> Programs -> Manage add-ons) and disabled the SharePoint ones I found. That fixed it! Seems like the SharePoint OpenDocuments Class was causing the error. With it disabled I was able to open the document, however it reduced the functionality of the drop down by removing the “Edit with…” option.
After a search for SharePoint OpenDocuments Class I found the answers in several blogs (Outlook by the sound, Shaune Donohue, and Michael Becker). The issue is conflicting versions of the OWSSUPP.DLL file because you have both Office11 and Office12 installed. You can check for these two folders in C:\Program Files\Microsoft Office. I had both because I had installed Visio and Project 2007 while still running 2003 for the rest of the suite. I renamed the Office12 version (once I am off of Office 2003 I will change this back) and enabled the add-on and everything works great.
The funny part is none of these blogs mentioned the error message (maybe they were getting a different one?), so I couldn’t find them on my initial search. Hopefully this post will be the “bridge” for others who get this annoying error message so that you can find the easy fix. The only question that remains is what changed to start causing this (I’ve had Visio 2007 installed for at least five months). If I find the answer to that I will update this or if you know please leave a comment.
- Posted by Kale at 12:01 pm
- Permalink for this entry
- Filed under: Office, SharePoint
- RSS comments feed of this entry
- TrackBack URI
Thanks so much for posting the info on the IE error 0xc06d007f. I’ve been struggling with this problem for a couple of months, and your tip corrected it immediately. Thanks again!
Dido! I had the same problem, had Office 2003 and Visio 2007 installed and when attempting to Check Out a document from share point I would get the same error message. Removed Office 2003 and installed Office 2007 and problem went away. Frontpage 2003 is still installed but does not seem to cause a problem like other Office components.
Bob/Mike, glad I was able to help. I was surprised how much traffic this post received…it has to be pretty common issue, yet I haven’t seen much else written on it.
The trigger was probably an Office 2003 update. Applying the 2003 update probably overwrote the registry to indicated that the MSO.DLL from the Office 11 folder was the preferred version. Sometimes a repair of the 2007 app fixes the problem. Currently the Windows Sharepoint Support feature of Office 2007 doesn’t play well with the Office 2003 apps. Unless you really need it (like for Sharepoint Designer) the best answer is to remove the Windows Sharepoint Support feature of Office 2007 through the Change button of add remove programs.
hth
I am getting this same error when trying to view files on a sharepoint site. I have Office 11 and Office 12 folders, but the Office 12 folder does not have OWSSUPP.DLL. The only thing in it is an Office Outlook Time Zone Data Update Tool.
The only Office 2007 file that I can find on my computer is Microsoft Office 2007 Language Settings.
Does anyone have any ideas about what I should try to do?
Nevermind, I figured it out. I had installed microsoft expression 2007 a few months back. The offending Office 12 folder with OWSSUPP.DLL was in the Expression folder. I am able to get files off of sharepoint now.
I just did the first part, disable the add-ons.
Thank you!
So glad I found this post, Kale. I started experiencing the same problem a week ago and I too had several Office 2007 components coexisting with 2003. Your post saved me alot of frustration. Thanks!
We had the same issue here, right down to offset in the SysShader.dll.
This MS KB article addresses the issue.
http://support.microsoft.com/kb/929360/
There’s also a hotfix available, but I’ve not tested it. The workaround, that’s worked for us everytime, is to open an Office 2007 product, like SP Designer, go to Help, then run the rapair. Sometimes Office 2003 also needs to be repaired, which can be done via Control Panel. I get nailed everytime an Office 2003 patch is pushed onto my desktop, so I’m getting pretty practiced at running the repair.
Thank you so much for sharing this information. It saved me a lot of time trying to contact MS and trying to get free support from them.
Thank a LOT.
Emil
Thanks for the input…it helped! This issue began on my machine last week…turns out the MS Compatibility pack was the cause. I’ve had SharePoint Designer 2007 for several months, running on XP with Office 2003…no problems at all using my SharePoint sites….till last week apparently when I installed the compability pack…the OWSSUPP.DLL associated with the MS compability pack was the culprit…I repaired SP Designer 2007 and was good to go…that was two days ago…still working well.
Hi Folks. Thanks for me doing my job again as i needed! I’ve Office 2007 and some Office 2003 (Visio, Project) running parallel. Renaming OWSCLT.DLL and OWSSUP.DLL in the Office11 directory helped.
In my case I had Office 2003 and Expression Web so I repaired Expression Web and Voila! it worked! Thank you so much.
Hi, I get this message when I try to open some internet pages. I have done all that you have written up there but it didn’t work for me. I have XP on my PC and MS Office 2003 with MSCompatibility pack for 2007. I do open sometimes Office documents on share points at our university. Does anybody have any idea about I’m suppose to do?
Thanks!
Ifa
Thanks! Was running into this problem on SharePoint myself and this fixed a VERY annoying and persistent error.
Thanks for the write up - I have a feeling that you are going to save myself and a number of users alot of time.
Thanks once again.
Thank you! Fixed problem instantly!
[...] I had a hard time finding the solution and finally came across this blog by Kale Davis [...]
Excellent that fixed my problem
Thanks for this. It really helped. I ended up doing the workaround found here that Kerwin submitted: http://support.microsoft.com/kb/929360/
I believe the cause was the MS Compatibility Pack. She had Visio 2007 and Office 2003 installed.
Thanks
Thanks so much for this. I could not figure out what the fix was, your info really helped!