Microsoft Office Document Imaging Problem after installing SP 3

After installing SP 3 for Office 2003, Microsoft Office Document Imaging is
demonstrating the following behavior:

The icons on the tool bar work fine, but any attempt to pull down a menu
(whether with the mouse or with keystrokes), such as the <file> menu causes
the following error message:

"Microsoft Office Document Imaging has encountered a problem and needs to
close. We are sorry for the inconvenience."

The program then shuts down.

Is there a patch or anything else available which will enable us to get the
menus to properly function?

If not, is it possible to uninstall office 2003 and re-install it without SP
3. I'd rather have a fully functioning Microsoft Office Document Imaging
program than whatever improvements are associated with SP 3.


Is anyone else experiencing this problem?

I'm also experiencing this problem with one of my users machines and have
been looking for a solution, but haven't come up with anything yet. The
information in the KB article posted above really doesn't apply to this
situation.

I'm going to attempt to uninstall/reinstall MODI, but if that doesn't work,
I suppose I'll have to uninstall/reinstall Office 2003 SP2 as this particular
user uses MODI on a regular basis.

Thankfully we haven't deployed Office SP3 to any other machines yet.

Clicking the Reset button in the Tools Menu only sets MODI as the default
application for opening TIF files. Unfortunately, this doesn't resolve the
issue of the error message that you get when you click on the <file> menu. I
tried it yesterday and it didn't work.

I am having the same problem. (I have XP home edition) And on one of my
computers, it was definately related to the office update released in
September 2007. Everyting was working fine until the upgrade. After the
upgrade microsoft imaging was not working.
I checked the message that you send to Microsoft and in that message, were a
bunch of stuff I did not understand, but there was a reference to a file:
mspview.exe.

I then did a search on my computer and found where the file was located. I
had one mspview file from 2003 and one from 2007 located in different
folders. I checked another computer where miscrosoft document imaging was
working fine and that computer's mspview application was from June 2003 in
both folders.

I went back to my computer with the imaging probem, and clicked on the file
mspview.exe from 2003, an icon called MSPVIEW popped up. When I clicked this
I opened up microsoft document imaging program and then I could go to file
and click and then I could print......So I deleted the mspview.exe 2007
version and moved the MSPVIEW to that spot. Now I can print. I have
probably violated every protocol in world when it comes to computer speak but
it works for now.

So probably all you need to do is to reinstall Office 2003 and DO NOT DO THE
AUTOMATIC UPDATE until microsoft fixes this. I also put my automatic updates
on 'notify me' because I am not installing office updates until there is a
fix for this imaging problem available. It is a pain to have to reinstall
Office 2003 everytime they update Office.

I get the same error. Microsoft's error reporting sends the following
information back to Microsoft:

AppName: mspview.exe AppVer: 11.0.8166.2 AppStamp:4616c203
ModName: mspview.exe ModVer: 11.0.8166.2 ModStamp:4616c203
fDebug: 0 Offset: 00016537

I have no idea how to solve this problem, but it is absurd that Microsoft's
supposed service update has ruined the ability to use one of the main Office
applications. This has to be fixed.

Hi,

I was having the same problem as described above after installing
service pack 3 for office. However, I had a different computer that
did not have SP 3 installed yet.
Here's what I did:

1. On the computer that is experiencing the error: Go to C:\Program
Files\Common Files\Microsoft Shared\MODI. Inside
is a folder called 11.0.
2. Rename that folder to 11.0new (or whatever you want to call it).
3. Find a computer that does not have service pack 3. Go to C:
\Program Files\Common Files\Microsoft Shared\MODI and copy the folder
called 11.0
4. Paste the folder 11.0 into C:\Program Files\Common Files\Microsoft
Shared\MODI on the computer that was experiencing problems.

This solved the problem for me.

Here is the reg hack to fix the issue associate. I created a script to push
this remotely to a list of computers:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.tif]
"Content Type"="image/tiff"
"PerceivedType"="image"
@="MSPaper.Document"

[HKEY_CLASSES_ROOT\.tif\MSPaper.Document]

[HKEY_CLASSES_ROOT\.tif\MSPaper.Document\ShellNew]

[HKEY_CLASSES_ROOT\.tif\OpenWithList]

[HKEY_CLASSES_ROOT\.tif\OpenWithList\MSPVIEW.EXE]
@=""

[HKEY_CLASSES_ROOT\.tif\OpenWithProgids]
"TIFImage.Document"=hex(0):

Just copy and paste this in to a text file and save with a name of your
choice, change the extention to .reg and your good to go.

Ann absolutly has the work around. Search for the old (2003) Msview.exe. It will probably be in a cache some place. Use that
[QUOTE=Ann;3287761]
I then did a search on my computer and found where the file was located. I
had one mspview file from 2003 and one from 2007 located in different
folders. I checked another computer where miscrosoft document imaging was
working fine and that computer's mspview application was from June 2003 in
both folders.

I went back to my computer with the imaging probem, and clicked on the file
mspview.exe from 2003, an icon called MSPVIEW popped up. When I clicked this
I opened up microsoft document imaging program and then I could go to file
and click and then I could print......So I deleted the mspview.exe 2007
version and moved the MSPVIEW to that spot. Now I can print. I have
probably violated every protocol in world when it comes to computer speak but
it works for now.

So probably all you need to do is to reinstall Office 2003 and DO NOT DO THE
AUTOMATIC UPDATE until microsoft fixes this. I also put my automatic updates
on 'notify me' because I am not installing office updates until there is a
fix for this imaging problem available. It is a pain to have to reinstall
Office 2003 everytime they update Office.


"

Actually, the msview will get it working, however, part of it would be impaired this way. Whenever one tries to reinstall if SP3 has been installed, the SP3 version will be installed instead of original. However, I got it working again in its new form (for now) by running repair out of Word (not the install disk), it replaced the msview with the 2007 version and seems to have fixed the registry entries. The root cause and its appropriate fix still remains a mystery. I do know the problem came after I made an annotation using the updated version and tried to make it permenant. That's when it started to screw up and cause problems. I hestitate to make an annotation and try to make it permenent for that reason now!

I have just had that error pop up today. It worked - scanned fine this morning. Then I went ahead and set up the FAX Console using the Fax Wizard on my machine. Then later went to scan something and got this error for the first time. So, right after installing the Fax Console using the Fax Wizard is when I started getting the MSPView.exe error (after opening up the program and clicking on File). I hope this little bit more of information can be used to help narrow down the problem and find a fix.

Same problem. Here is the solution:

SP3 changed a number of files in the MODI folder to April 2007 versions. If you have a computer with Microsoft Office 2003 on it prior to the SP3 update, copy the MODI Folder, change the folder on the SP3 updated computer to MODI.OLD and paste the copied MODI Folder in the same place: Path: C:\Program Files\Common Files\Microsoft Shared\MODI.

Other alternative:

If you have the original Office XP 2003 CD's, the files are located in a Cab folder called: D:\ M4561414.CAB

Extract the following and paste accordingly. There is a CAB file extractor available on a trial basis and this will do the trick. Google "CAB file extractor.”

All files are dated 2003 except for one noted below dated 2004. Replace all the 2007 files with these:

Path: C:\Program Files\Common Files\Microsoft Shared\MODI\11.0\

MDIINK.DLL
MDIVWCTL.DLL
MSPCORE.DLL
MSPFILT.DLL
MSPGIMME.DLL
MSPSCAN.EXE
MSPVIEW.EXE


Path: C:\Program Files\Common Files\Microsoft Shared\MODI\11.0\\Drivers

MDIGRAPH.DLL
MDIMON.DLL
MDIPPR.DLL
MDIUI.DLL

Path: C:\Program Files\Common Files\Microsoft Shared\MODI\11.0\1033

MSPFLTRS.DLL
MSPLCRES.DLL 2004


You may not need all of these but I used them anyway and everything works fine.

As for the problem, it is just another screw-up by Microsoft. This is the third one for me in three months. I've shut all auto updates off and refuse to do any more. In fact, someone should launch a class action lawsuit against Microsoft because this kind of irritation is a regular occurrence resulting in vast amounts of inconvenience and wasted time. One update on my computer trashed several functioning programs when it updated Microsoft.NET version 2.

If a program stops working, it is almost always attributable to a so-called Microsoft improvement or security update. Lawyers unite! Sue, Sue, Sue!

Shenan Stanley is wasting bandwith by not regading the thread, which is very specific! Thanks Shenan for the useless lecture about what the newsgroup is oriented toward.

The issue by the way has NOTHING to do with the reply about long file names to which Shenan was responding. It has to do with file changes that SP3 so "helpfully" made.

The Microsoft Imaging issue is related to a major screwup with the new 2007 files, which SP3 included. Simply replace them with the original 2003 files found on the Office 2003 CD (M4561414.CAB) Extract the files and replace everything in the MODI\11 folder.

I'm just an ordinary computer user - not a techie or an MS-MVT and I figured it out.

As an added point

The tif files would open in MODI but the mdi files would not. Today I made and ran the vbs script file mentioned in the KB article at
http://support.microsoft.com/kb/938813
and now I can double click on a mdi file and it works. I don't know if the annotation part still screws up a file but I do know that repairing from Word or control panel has got me working again and with this double click ability it seems to be back to normal. (Wonder if the reference to Hive in the kb article means it will prevent it from happening again?)