Microsoft Office Document Imaging

[Fred J]

This program has been running fine for years. Suddenly, I encountered
the following problem. The scan completes. I select DONE. OCR scanning
completes. I see the image in the windows. As soon as I select File I
get a window entitled Microsoft Document Imaging.
Microsoft Document Imaging has encountered a problem and needs to
close. We are sorry for the inconvenience. ... Send Error Report and
Don't Send buttons.

Was there a recent update that is interfering with Document Imaging?
Thank you,
Fred J.

 

[Fred J]

Additional information: Error Details Mspview Failure
Error Signature
AppName:mspview.exe AppVer: 11.0.81662 AppStamp:4616c203
ModName:mspsview.exe Mod Ver 11.0.8166.2 Mod Stamp:4616c203
fDebug:0 Offset: 00016537

 

[Fred J]

Additional Information:
I can select a tif file and "open with" Microsoft Office Document
Imaging. The document is displayed. Again, if i select File (before
the drop down fills) an exception occurs.

Thanks,
Fred J.

 

[Guest]

Same EXACT thing happens to me. I cannot figure out how to fix it.

 

[Pzkmac]

I have the same problem! I also have reinstailed it and the problem still
occurs. Does anyone know if this is fixable?

 

[Pzkmac]

I've also looked around and have not found any other advice or patches for
this program. I've tried other products, yet they still are not as good as
Microsoft imaging. It has become a big probelm for my office and I. Has
anyone found any ways to fix this or get around it?

 

[Roberto]

the discussion seems to be still actual and unsolved even now...?!
Roberto

 

[JasonB]

Must be, a user of mine just had this happen yesterday when he scans and
e-mails stuff daily. This is a major problem.....

 

[daryl]

I too am having this problem.. It started yesterday. Is anyone from
Microsoft monitoring this?? Does microsoft not have a solution for this? I
have searched there website and this thread was the only thing I found
regarding this... Yet there is no solution or a fix!!

daryl

 

[semper-fido]

rsc's advice was a lifesaver. It helps if you have the 2003 file available.
I have it and if I can I will attach it to my blog
http://semper-fido.blogspot.com/

When you get to my blog search for "Microsoft document imaging error" or
"mspview.exe". I don't know if it will stick onto my blog.

 

[Fred J]

Interesting development now just popped up. Imager stopped working
again, even when I unininstalled and reinstalled Office 2003. This
happened after I had to make a new user because of what appeared to be
corruption of the user account file by NIS. Now the fax wouldn't show
my fax files!. The imager, which was repaired in the process would show
mdi (microsoft document imager) files but not tif or tiff files. I
changed the viewer for those (the tif and tiff files) to Windows
Picture and Fax Viewer. Most of the functions in imager can be used in
it such as underlining etc. Not sure what is happening but wanted to
keep people abrest of the continuing saga. BTW, anybody had problems
after having installed XP SP3. That is next. One thing, according to
the blogs, make sure you uninstall NIS before hand and reinstall after.

--
rsc
------------------------------------------------------------------------
rsc's Profile:http://forums.techarena.in/member.php?userid=48129
View this thread:http://forums.techarena.in/showthread.php?t=847192

http://forums.techarena.in

I may have read this somewhere, but I think the problem has to do with
what is contained on the most recently used file list. When you click
on FILE, the list of the most recently used files is built. Find the
entry in the registry that contains those files and remove those
entries.
Fred J.

 

[Freud II]

I may have read this somewhere, but I think the problem has to do with
what is contained on the most recently used file list. When you click
on FILE, the list of the most recently used files is built. Find the
entry in the registry that contains those files and remove those
entries.
Fred J.

But. Please.¿Where is it????

 

[Malbone]

I also had major problems with MODI 2003 after doing the WinXP SP3 update.
The scanner wouldn't scan, instead reporting a misfeed every time; and the
OCR program reported no text on any page given to it.

Turns out I still had the old, "correct" versions of the software. However,
a further bit of mucking around led me to Data Execution Prevention, which
had been turned on in the course of the SP3 update. I created exceptions for
the 3 executables in the MODI directory (scan, view and OCR), and the entire
package now works fine.

Malbone

 

[Malbone]

I'm hardly an expert. There is a technical discussion at

http://support.microsoft.com/kb/875352

and a less technical article at

http://en.wikipedia.org/wiki/Data_Execution_Prevention

After becoming familiar with what DEP does, you can access its settings as
follows:

1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. On the Advanced tab, under Performance, click Settings.
3. On the Data Execution Prevention tab, use one of the following procedures:
• Click Turn on DEP for essential Windows programs and services only to
select the OptIn policy.
• Click Turn on DEP for all programs and services except those I select to
select the OptOut policy, and then click Add to add the programs that you do
not want to use the DEP feature.
4. Click OK two times.

The Add feature works as you might expect -- you have to browse through the
Program Files directory to find the executable you want to exclude.

Malbone

 

[Gorwen]

I may have read this somewhere, but I think the problem has to do with
what is contained on the most recently used file list. When you click
on FILE, the list of the most recently used files is built. Find the
entry in the registry that contains those files and remove those
entries.
Fred J.

try KB952002
http://support.microsft.com/?kbid=952002

 

[Bookman]

I just encountered this error in Office 2007 and the easiest fix I could come
up with was to clear the recently used files. All I did was opened four
different .mdi files. Since you can't go to File, Open, etc. you will have
to find them and double click on them using My Computer, etc. It is
important you use four DIFFERENT files. These "replaced" the four recently
used files on the Document Imaging File menu. After you've opened up the
four files, you should be able to click on file and it won't crash. I think
the problem starts when saving files with more than 55 characters, so be sure
to use smaller file names.

At least this way you don't have to mess with the registry.

 

[Tasso P.]

Answer: http://support.microsoft.com/kb/952002/
then, click on the words at the top left hand corner of page: "View
and request hotfix downloads" which you'll find next to the pic of the
screwdriver and wrench...

This hotfix fixes the following issue that was not previously documented in
a Microsoft Knowledge Base article:

* You install [[Microsoft Office 2003 Service Pack 3.]] Then, in
Microsoft Office Document Imaging (MODI), you click the File menu. In this
situation, MODI may crash. This problem occurs when the following conditions
are true:
o You open a file that has more than 55 characters in the file name.
o The file name entry appears in the most recently used (MRU)
files list on the File menu.

:

This program has been running fine for years. Suddenly, I encountered
the following problem. The scan completes. I select DONE. OCR scanning
completes. I see the image in the windows. As soon as I select File I
get a window entitled Microsoft Document Imaging.
Microsoft Document Imaging has encountered a problem and needs to
close. We are sorry for the inconvenience. ... Send Error Report and
Don't Send buttons.

Was there a recent update that is interfering with Document Imaging?