SharePoint is blowing up with Unhandled exception

Good day,

I have a number of sites running on my WSS 3.0; with MS SQL 2005 Std;
installation that have been working just fine for the past three months...
but latley, if a user attempts to checkout a document or open a document in
read-only mode, IE crashes.

I am prompted if I want to debug the application using Visual Studio, and
this is the error I see:

Unhandled exception at 0x7c812a5b in iexplore.exe: 0xC06D007F: Procedure not
found.

This only started to happen a few days ago.  Nothing has changed ( to my
knowledge ), and it doesn't happen on all documents.

Any suggestins?

Does this occur on only one (or some) client system?

Does this occur on only one (or some) client system?

If so check that no Office 2003 updates have been made on a client
running Office 2007 applications - or vice versa.

Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please

I am seeing this behavior after the latest round of updates from MS.

I am seeing this behavior after the latest round of updates from MS.  I will
try to unistall the most recent batch of updates to see if they are truely
the issue.

I am seeing this mainly on IE7 clients, and after the latest patches were

I am seeing this mainly on IE7 clients, and after the latest patches were
applied -- but I do I have a two IE 6 clients that show the same behavior.

I stopped getting the error after removing the two most recent XP security

I stopped getting the error after removing the two most recent XP security
errors.  I am currently using IE6 because of conflicts with other software.
I then reinstalled the two security updates and now it works just fine.  I
think it must be related to the order in which some of the most recent
updates are installed.

SharePoint is blowing up with Unhandled exception

We saw this behavior on one client within our org. Never did figure
out the root cause except that it was a client side issue.
Re-installed Office on the client and the problem was resolved.

Okay, it looks like its a conflict between Office 2003 and Office 2007.

Okay, it looks like its a conflict between Office 2003 and Office 2007.  All
the clients that are having the issue have Office 2007 installed, except for
MS Access, which is Office 2003 -- we have to use Access 2003 because of a
custom application...

So, I am guessing the solution will be to move to all 2003, or all 2007 but
not a combination of both....

It's the solution I've used for myself ever since I experienced problems

It's the solution I've used for myself ever since I experienced problems
with having OneNote 2007 Beta on a client otherwise running Office
2003 products.

I.e. I have one machine running Office 2003 and FP 2003 and another with
Office 2007 (and SPD 2007).

The problem is that if you have both (even only one Office 2003 product
and all the rest Office 2007), you will in some cases automatically
upgrade key files needed for Office 2007 with an Office 2003 version.

I rather suspect that this particular problem is to do with a single
file being changed in this way. (A file whose name I can never remember
off-hand)


Mike Walsh