I am having a problem accessing Windows SharePoint Services site. My Internet Explorer crashes and also several, but not all, computers in the office also do. This is the error in Event Log: Event Type: ErrorEvent Source: Application ErrorEvent Category: NoneEvent ID: 1000Date: 1/19/2007Time: 11:48:13 PMUser: N/AComputer: MARTODescription: Faulting application iexplore.exe, version 6.0.2900.2180, faulting module unknown, version 0.0.0.0, fault address 0x00000000. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat0008: 69 6f 6e 20 46 61 69 6c ion Fail0010: 75 72 65 20 20 69 65 78 ure iex0018: 70 6c 6f 72 65 2e 65 78 plore.ex0020: 65 20 36 2e 30 2e 32 39 e 6.0.290028: 30 30 2e 32 31 38 30 20 00.21800030: 69 6e 20 75 6e 6b 6e 6f in unkno0038: 77 6e 20 30 2e 30 2e 30 wn 0.0.00040: 2e 30 20 61 74 20 6f 66 .0 at of0048: 66 73 65 74 20 30 30 30 fset 0000050: 30 30 30 30 30 0d 0a 00000.. I have traced the exception down to this method: 75C5D34F call COleScript::ExecutePendingScripts (75C5AF3Ch) And this is the stack trace: kernel32.dll!_RaiseException@16() + 0x52 bytes OWSSUPP.DLL!35959807() [Frames below may be incorrect and/or missing, no symbols loaded for OWSSUPP.DLL] MSO.DLL!30cd1abb() MSO.DLL!30ccf0ed() OWSSUPP.DLL!359583f6() OWSSUPP.DLL!35950612() OWSSUPP.DLL!35947008() oleaut32.dll!_DispCallFunc@32() + 0xc3 bytes oleaut32.dll!CTypeInfo2::Invoke() + 0x20c bytes OWSSUPP.DLL!3594a4b0() jscript.dll!IDispatchInvoke() + 0x6f bytes jscript.dll!InvokeDispatch() + 0x72 bytes jscript.dll!VAR::InvokeByName() + 0x14e0b bytes jscript.dll!VAR::InvokeDispName() + 0x40 bytes jscript.dll!VAR::InvokeByDispID() + 0x54 bytes jscript.dll!CScriptRuntime::Run() + 0xfc9 bytes jscript.dll!ScrFncObj::Call() + 0x6a bytes jscript.dll!CSession::Execute() + 0xa1 bytes jscript.dll!COleScript::ExecutePendingScripts() + 0x14d bytes> jscript.dll!COleScript::ParseScriptTextCore() + 0x1a5 bytes jscript.dll!COleScript::ParseScriptText() + 0x2b bytes mshtml.dll!CScriptCollection::ParseScriptText() - 0xa bytes mshtml.dll!CScriptElement::CommitCode() - 0x3d6 bytes mshtml.dll!CScriptElement::Execute() + 0x8f bytes mshtml.dll!CHtmParse::Execute() + 0xc1ec bytes mshtml.dll!CHtmPost::Broadcast() + 0xd bytes mshtml.dll!CHtmPost::Exec() + 0x1d313 bytes mshtml.dll!CHtmPost::Run() - 0x381b bytes mshtml.dll!PostManExecute() + 0x51 bytes mshtml.dll!PostManResume() + 0x75 bytes mshtml.dll!CHtmPost::OnDwnChanCallback() + 0xc bytes mshtml.dll!CDwnChan::OnMethodCall() + 0x19 bytes mshtml.dll!GlobalWndOnMethodCall() + 0x66 bytes mshtml.dll!GlobalWndProc() + 0xe5 bytes user32.dll!_InternalCallWinProc@20() + 0x28 bytes user32.dll!_UserCallWinProcCheckWow@32() + 0xb7 bytes user32.dll!_DispatchMessageWorker@8() + 0xdc bytes user32.dll!_DispatchMessageW@4() + 0xf bytes browseui.dll!TimedDispatchMessage() + 0x33 bytes browseui.dll!BrowserThreadProc() + 0x336 bytes browseui.dll!BrowserProtectedThreadProc() + 0x50 bytes browseui.dll!_SHOpenFolderWindow@4() + 0x22c bytes shdocvw.dll!_IEWinMain@8() + 0x129 bytes IEXPLORE.EXE!WinMainT() + 0x2de bytes IEXPLORE.EXE!__ModuleEntry@0() + 0x99 bytes kernel32.dll!_BaseProcessStart@4() + 0x23 bytes I found out that the script that is loaded in ParseScriptTextCore is this one: <!--<script language="javascript">var ExpDatabase = null;var databaseBtnText = '';var databaseBtnDesc = '';var fDBInstalled = false;try{ExpDatabase = new ActiveXObject('SharePoint.ExportDatabase');if (ExpDatabase && ExpDatabase.IsDBProgramInstalled()){fDBInstalled = true;databaseBtnText = ExpDatabase.MenuTitle;databaseBtnDesc = ExpDatabase.MenuDescription;}} catch(e){}</script>//--> However this script does not crash my IE when it is run isolated from SharePoint site in a separate html file.I also disabled every BHO in IE, but the browser still crashes when I visit that specific page of the WSS site.Of course, with Mozilla it works. Any idea how can I get this fixed? This problem really makes WSS unusable for us. Thanks, -- Martin Kulovhttp://www.codeattest.com/blogs/martinMVP, MCT, MCSD, MCPD

I have been running into this issue and I found that if you remove the OWSSUPP.DLL file from the Office11 or Office12 (if running 2007) and then go to programs->microsoft office->microsoft office tools then run microsoft diagnostics (takes about 5 mins). the last step it will fix one error. After doing this the three pc's that were no longer able to open office documents from within sharepoint are again able to. I cannot take the credit for finding this as after searching many hours for some type of help I found this link http://www.experts-exchange.com/Networking/Sharepoint/Q_21763091.html

Thanks jastoto, I found out that if I uninstall SharePoint Designer 2007, the problem goes away. It is some incompatibility with SPD 2007 and WSS 3.0, IMHO. Thanks for your response, I will give it a try next time that we have this problem. Martin http://www.codeattest.com/blogs/martin

The problem is Office 2007 and Office 2003 on the same pc. I'm using office 2003 with Sharepoint Designer. - Open add/remove program- Click change on Office 2007, Sharepoint designer 2007 or any office 2007 app.- Choose add/remove function- In the treeview open the one in the bottom, and there you have Sharepoint bla bla bla...... Choose, not to install. /Tomas Lundgren

The problem is Office 2007 and Office 2003 on the same pc. I'm using office 2003 with Sharepoint Designer.- Open add/remove program- Click change on Office 2007, Sharepoint designer 2007 or any office 2007 app.- Choose add/remove function- In the treeview open the one in the bottom, and there you have Sharepoint bla bla bla...... Choose, not to install. /Tomas LundgrenTomas,I do not believe the problem is both 2003 and 2007 office or sharepoint.I have this problem, do not have 2007 office or sharepoint and do have 2003 office only installed.For myself this began immediately after allowing an ACTIVE-X control, labled as coming from microsoft, while setting up the office live workspace. I never allowed sharing of documents. As soon as I clicked the control the application crashed.I went into office11 folder and renamed the OWSSUPP.DLL mentioned above (system would not allow removal) and ran the DETECT and REPAIR option under HELP in Office 2003. Now I am able to go into office live workspace with no problem and hopefully this resolved the issue.Microsoft should be the ones to tell us what is wrong with their software, isn't that partly why we pay them to begin with? Of course I could be wrong we may be paying them for DIRTY CODE.Monty

Have you tried this? http://support.microsoft.com/kb/938888http://sharepoint.nauplius.net