msonsext.dll makes explorer.exe crash

The dll lives here - Program Files\Common Files\Microsoft Shared\Web Folders. It is currently said to be associated with Sharepoint - <<msonsext.dll is a module associated with SharePoint Portal Server from Microsoft Corporation>>, although it exists on my XP machine which has never had Sharepoint installed, so it has other applications also. It is also described as <<Microsoft Office Name Space Extension>> so it may be installed with Office 2003 but is not installed with O2007.

Have a look at the installed date. If this coincides with the install date on Sharepoint, and that application is removed, rename it and see if the problem goes away.

By the way, the replacement for FrontPage is Microsoft Expression. Sharepoint is a different beast entirely.

Chris B

Well, I guess it's installed with Office 2007 because on this machine (witch is a fairly new install) we only installed Office 2007. There was no Office 2003 or whatsoever. So I guess : A- it comes with Office 2007 and as you stated burrcm it is used by something else. B - it comes with some other Windows component altrought I didn't install Office Live or something else.

unfortunately I can't confirm SharePoint installation date. I can confirm that as of yesterday when I uninstalled Sharepoint and Visio there was no problem. As soon as i reinstalled Visio the problem camed back. I also found the dll and I rename it and I saw no problem in running any of the Office programs installed. Because I can't confirm what exactely this DLL does I am a little bit unconfortable with this solution and I consider it just another step in my debugging routine.

Optoma I will try later your sugesttions,. As I understand it sfc is a command that helps verify the integrity of the dll system files in a manner witch fixes problems we had with previous versions of Windows when 3rd party software could overwrite system dll files and thus cause corruption of some programs or all the system as a whole. As for the ms update suggested this update doesn't seem to adress in any kind of way the issues I have with my computer altrought at some point I might try it as I am slowly but surely running out of options.

Will keep everyone posted. Thnkz for the help.

Sardaukarx,
Your understanding is correct.
Heres fully about sfc. It explains the switches
http://support.microsoft.com/kb/310747

About the MS update:
It dosnt address the issue but worth a try.
It does list the dll in question, although its probably the same version!

That file is apparently installed with windows... it (version 9.0.5318, dated 05/19/2001) exists on an XP SP3 machine I have here which has never had any part of Office (Visio is technically an Office module, like Project, et al) installed except the standalone viewer for powerpoint files (http://www.microsoft.com/downloads/details.aspx?FamilyID=048dc840-14e1-467d-8dca-19d2a8fd7485).

There again Darr I have never installed the stand alone viewer for Power Point files. I have installed Office 2007, Visio 2007 and SharePoint 2007. For the moment there is no computer available so I can make a fresh install from scratch. ( I will just in order to confirm at witch point the file appears). Will keep posting .

Well, none of the solutions as described above worked. Instead I have find a workaround. Instead of having a Favorites in Network I mapped a newtwork drive on the server

before :

\\server_name\share_name

\\server_name.fabrikam.com\share_name ---- in the login script on the AD.

As the problem ONLY occurs when u go to My network places and click on that specific share, this workaround is acceptable for the moment. So even if Expers-Exchange sends me mail about how this question is "abandoned" the solution to the problem was never find.

Close the question by accepting your own comment as the solution noting the reason as stated in your last comment.

Chris B

I can't do that the problem is back with a vengeance! Same problem all over again. I changed the machine and replace it by a brand new one, same model same config (we all have HP hardware in here). I just put the hard drive of the "old" machine in the new one so the problem is really software related as I knew all along.

OK. Delete the dll. Whatever needs it (if anything) will complain if it can't find it. Once this occurs, reinstall the program. This will reinstall the dll.

Chris B

Burrcm : did that didn't helped. I also tried to rename the .dll to name_of_file.dll.old That helped and no error occured for a while. I think I am going to use this workaround for the moment and investigate as I can get my hands on that machine For the moment, I can't take it away from the user because she really needs it and I have no other clean machine to give to her.