Windows Client TechCenter > Windows Vista IT Pro Forums > Windows Vista IE > Vista and Sharepoint 2003 Causing IE to Crash
Ask a questionAsk a question
 

QuestionVista and Sharepoint 2003 Causing IE to Crash

  • Tuesday, January 09, 2007 4:37 PMBrotherDeeJ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Everytime I try to open a file from a document library in SPS2003 my browser crashes and restarts without opening the document.  I am using Vista RTM, Office 2007. Anyone got any ideas on what is causing this?

All Replies

  • Wednesday, January 17, 2007 5:16 PMscottyroz Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We had the same issue, remove project 2003. If you figure out the cause I would love to know...
  • Friday, January 19, 2007 1:34 AMAdrian DuPre Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Another data point here...

    We've been running Sharepoint 2003 for a while now with WinXP and Office 2003.

    So far, we have 3 users with consistent IE crashes when trying to open an Office document from a Sharepoint document library.  Here are the configs:

    Windows Vista RTM, IE7, Office 2007

    Windows XP, IE7, Office 2007

    Windows XP, IE6, Office 2007

    I'm guessing this is an Office 2007 "Feature" that hasn't been tested/discovered by Microsoft yet.  I found a thread in the Sharepoint community forums on this issue, but no resolution.

     

    Why do you suggest removing Project 2003?  Did this clear up the issue?  Could it possibly be related to having some apps of each version loaded concurrently?  (i.e. Office 2007 Pro + OneNote, Visio or Project 2003?)  Enquiring minds want to know!

     

  • Tuesday, January 23, 2007 11:42 PMTheSASMan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We are having an identical issue...it is severly affecting our business. There seems to be a difference between documents with extension doc vs docx. Nothing more to add.
  • Thursday, February 01, 2007 4:17 PMSemicon IT man Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We are seeing this issue pop up in my organization as well.  I have been testing the removal / repair of my office 2003 and Office 2007 Select applications (Visio, Project,...).  No linkage found yet.
  • Wednesday, February 07, 2007 12:22 AMCory DelamarterMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I just responded in another thread about steps that I took that appear to have fixed this issue for me on my workstation.  I hope this helps.

    http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1197148&SiteID=17&mode=1

  • Thursday, February 15, 2007 11:10 PMTheSASMan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    All,

    I opened a case with Microsoft to resolve this and they have this now as a documented problem, incompatibility, which will not be fixed. Basically, you need to upgrade to SharePoint 2007. That's the word...

  • Friday, February 16, 2007 5:01 AMSemicon IT man Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    For me Corband's solution solved my issue:

     

    ·         Go to “C:\Program Files\Microsoft Office\Office12”

    ·         Delete “OWSSUPP.DLL”

    ·         “Start” -> “All Programs” -> “Microsoft Office” -> “Microsoft Office Tools” -> “Microsoft Office Diagnostics”

    ·         Run the diagnostics and it should fix 1 issue in its last step.

     

    I'm running Windows XP SP2, IE 6, Office 2003 PRO with Sharepoint 2003.

  • Friday, February 16, 2007 2:44 PMfblin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    I have WIndows XP SP2, Office 2007, IE 7, Sharepoint 2003.

    I could make it "work" by passing IE and going directly through Open/Save Document in Word to my sharepoint repository.

    At least I can read document and publish them.

    Felipe Blin

     

  • Tuesday, February 20, 2007 7:35 PMcjbarth Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    In our case we had installed Office Enterprise 2007 and then Front Page 2003 afterward on a Vista Enterprise machine. We tried the OWSSUPP.dll fix and that didn't work. We were able to get things working after we removed Front Page 2003. It appears that Office 2007 doesn't play nicely with Office 2003 applicaions. I don't know if it would have made a difference if we installed Front Page 2003 before installing Office 2007. It might have, given that Office 2007 would then have over-written the IE plugins for opening different MIME types.

     

    Chris

  • Monday, March 05, 2007 11:04 PMJonnyFreeze Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I was having the same result: any attempt to open a document from Sharepoint 2003 would crash IE6. I had Office 2007 Professional Plus and then installed Front Page 2003 (all on Windows XP SP2). I didn't bother with the OWSSUPP.dll fix, though. I uninstalled Front Page 2003 and that fixed the problem. Interestingly enough, I already had some 2003 applications (including Project Pro 2003) before I installed Office 2007. So, I would surmise that installing an Office 2003 app after Office 2007 doesn't work very nicely with Sharepoint.
  • Tuesday, March 06, 2007 10:31 PMPaul Kleuver Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi there,

    Same happens here, also with Windows XP and IE 7 when you try to open a document on Sharepoint 2006. It is fixed when you "repair" your Office 2007.

    1. Control Panel, Add/Remove Programs
    2. Select "Microsoft Office (Professional) 2007" and select "Repair"
    3. Will take a while, but then your problem is gone (solved mine twice)

    Seems to happen when using Office 2007 together with some other Office 2003 components like Project 2003 or Infopath 2003. I installed those (again) after Office 2007 because I can't use the 2007 versions.

     

    Good luck!

     

    Paul

  • Friday, March 23, 2007 11:41 AMThanksThisWorked4Me Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    It looks like a variety of cocktail mixes of Office component products on a client machine has the potential to cause this issue ( Internet Explorer 6.0 crashing when accessing SharePoint Lists or Libraries) which - according to the threads in the link http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1090561&SiteID=17

    is sometimes successfully fixed by using the OWSSUP.DLL solution . . and sometimes not.

    My Environ = WinXP SP2, IE 6.0 SP2 - Had full Office XP originally, that was uninstalled by the desktop team who did a full Office 2003 install, I have subsequently installed Sharepoint designer 2007. What is noticeable is that the XP version of office had not entirely been uninstalled, there was a non-working (unassociated) XP Access icon left on my machine. So my machine in theory had a mix of Office XP, 2003 and 2007 components.

    Problem Fixed immediately.

    thanks

  • Tuesday, March 27, 2007 8:36 PMWilliam9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Currently we have SharePoint 2003 SP2 / Vista / Office 2007 / Project 2003.  When I opened documents in SharePoint by just clicking on the file my IE would crash.  The steps you (Semicon IT man ) provided, resolved that issue.  I have another issue and not sure if it's related. 

     

    If I checkout the document and then try and open the file I get the following error.

     

    " <filename> is locked for editing

     

    Open 'Read-Only' or click 'Notify' to open read-only and receive notification when the document is no longer in use. "

     

    So, now if I have it checked out, I'm unable to save changes made to the file.

     

    What do you think?

  • Thursday, May 31, 2007 3:17 PMLarryAW Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Wow, this worked for us!

     

    I always wonder, however, how does one come to think, "hmmm, I think I'll just delete owssupp.dll and see if that fixes it..."?  I mean, why didn't I think of that?  What vital piece of information in my mental computerbank am I missing that prevents me from ever thinking of this?

  • Monday, July 23, 2007 8:08 AMmacnetone Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Cheers this worked for me with Office 2003 and Portal 2003, appreciate the effort to relay the fix to folk Smile

     

    Mac

  • Wednesday, October 17, 2007 6:53 PMCFee Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    That worked for me - thank you so much.  I've been struggling with this for months.  I am running exactly the same -

    Windows XP SP2, IE 6, Office 2003 PRO with Sharepoint 2003
  • Monday, November 19, 2007 3:29 PMPowerHydro Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I certainly share your confusion ... 'why did I not think of that' ??

     

    We are running SharePoint Services 3, Windows XP SP2, Office 2003 and IE 6.  I am the only one in my office who has experienced this problem.  I am also the only one who has installed SharePoint Designer.  I tried the fix and it WORKS !

     

    Thank you to the one who came up with the fix - regardless of how it was derived.

     

  • Friday, July 11, 2008 9:55 PMEd Tittel Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    I, too, suffered this problem on Vista SP1 machine just after a CPU upgrade (?!). Every time I visited the TechNet Library, IE would freeze and I would have to jump into Task Manager to kill the app, then restart. Of course, this played hob with my Reliability Index. I, however, may have provoked this problem by turning off GrooveMonitor.exe using StartupCop3: I figured "I don't use SharePoint, why do I need this?" forgetting that MS uses the heck out of SharePoint and it's only natural to encounter it on the MS Web pages, especially in the TechNet Library. Live and learn, I guess.

     

    --Ed--

  • Monday, July 14, 2008 5:30 AMSteelfire75 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Guys guys. The dll fix works quite well, however we picked up the following as well:

     

    Had the same issue with all files.

    Vista Ent. SP1, Office 2k7sp1 Pro plus, Adobe Reader 8.1.

    Sharepoint 2k7.

    Did the dll fix, moderate success.

    Still crashing when opening PDF's.

    Uninstalled Adobe Products.

    Installed Foxit Reader -- Problem solved.

    Uncomfirmed report of a colleague who did the same but had Adobe 9 installed.

    Removed Adobe and installed Foxit Reader -- no more problems.

     

    This is for everyone for whom the dll fixed the office portion but Adobe is still a problem. I have done this on 3 other machines belonging to colleagues with Os mix of Win XP pro Sp2 and Vista Ent SP1, this has worked succesfully in all instances.

    Hope this helps guys.