Document Imaging exe crashes on File menu clicks

[Lester Lane]

What is wrong with this program. If I open a Tiff file in the Office
Document Imaging program and then click on File it crashes. All the
other menus drop down correctly. I have sent the Error Report to MS
but nothing for years. Do they even know of this issue? Is there a
work around or setting that needs changing please. Have Office Pro
2003 SP3 running on XP Pro SP3.

 

[Geoff]

What is wrong with this program. If I open a Tiff file in the Office
Document Imaging program and then click on File it crashes. All the
other menus drop down correctly. I have sent the Error Report to MS
but nothing for years. Do they even know of this issue? Is there a
work around or setting that needs changing please. Have Office Pro
2003 SP3 running on XP Pro SP3.

I have the same problem. I don't think the file type matters. from what I
have seen elsewhere, this issue has been affecting some (all?) since
installing SP3. Also, shortcut keys under the file menu (e.g. cntl-p) crash
it too.

Help!!!

 

[Lester Lane]

I have the same problem. I don't think the file type matters. from what I
have seen elsewhere, this issue has been affecting some (all?) since
installing SP3. Also, shortcut keys under the file menu (e.g. cntl-p) crash
it too.

Help!!!

This only happens if I have not scanned a document first. It's good
to know that MS care so much. Clearly this is an obvious error yet I
doubt it will ever be fixed. I have tried to get through the knitting
on their website to log this issue but to no effect. I strongly
believe in KISS and I therefore am shying away from MS products as
they are now too complicated even for them.

 

[Geoff]

This only happens if I have not scanned a document first. It's good
to know that MS care so much. Clearly this is an obvious error yet I
doubt it will ever be fixed. I have tried to get through the knitting
on their website to log this issue but to no effect. I strongly
believe in KISS and I therefore am shying away from MS products as
they are now too complicated even for them.

Well, to the credit of the folks here, I have always gotten great support
and no question has gone unanswered. Curiously, no takers yet on this one.

I don't scan any documents, but I use MS Document Imaging to "print" out
documents much as I used to with PDF's (and much more compact - a 1 MB PDF is
about a third the size as an MDI). It preserves the format but it's only an
image. As such, it cannot be edited easily and important metadata are
removed.

I sure hope someone finds a fix!

 

[Bob I]

This only happens if I have not scanned a document first. It's good
to know that MS care so much. Clearly this is an obvious error yet I
doubt it will ever be fixed. I have tried to get through the knitting
on their website to log this issue but to no effect. I strongly
believe in KISS and I therefore am shying away from MS products as
they are now too complicated even for them.

No such problem with Microsoft Documnent Imaging here. Perhaps you have
a problem with your scanner software interface.

 

[Geoff]

No such problem with Microsoft Document Imaging here. Perhaps you have
a problem with your scanner software interface.

Are you running Office SP3? At first blush, that seems to be the bugbear.
For myself, the issue has nothing to do with scanning.

 

[Lester Lane]

Are you running Office SP3? At first blush, that seems to be the bugbear.
For myself, the issue has nothing to do with scanning.

I agree with Geoff and as he states earlier Ctrl+P will cause a
crash. Though I have a feeling this might have been around before SP3.

 

[Bob I]

No, Office 2007 only has SP1

:




Are you running Office SP3? At first blush, that seems to be the bugbear.
For myself, the issue has nothing to do with scanning.

 

[Lester Lane]

No, Office 2007 only has SP1

Please read the issue clearly. We are talking about Office 2003.

 

[Bob I]

Please read the issue clearly. We are talking about Office 2003.

Try uninstalling the SP3, and see if it continues?

 

[Bob Buckland ?:-\)]

Hi James,

I'm not clear on your reference to having sent an error report spanning '...years'.

When you go to send the error and click on the detailed information button in the dialog what is the content of that dialog?

What Scanner brand/model are you using?

Are these TIFFs you created yourself? If so, what approach did you use and what TIFF settings are you using?

=============
What is wrong with this program. If I open a Tiff file in the Office
Document Imaging program and then click on File it crashes. All the
other menus drop down correctly. I have sent the Error Report to MS
but nothing for years. Do they even know of this issue? Is there a
work around or setting that needs changing please. Have Office Pro
2003 SP3 running on XP Pro SP3. <<
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Lester Lane]

Hi James,

I'm not clear on your reference to having sent an error report spanning '....years'.

When you go to send the error and click on the detailed information button in the dialog what is the content of that dialog?

What Scanner brand/model are you using?

Are these TIFFs you created yourself?  If so, what approach did you useand what TIFF settings are you using?

=============
What is wrong with this program. If I open a Tiff file in the Office
Document Imaging program and then click on File it crashes.  All the
other menus drop down correctly.  I have sent the Error Report to MS
but nothing for years.  Do they even know of this issue?  Is there a
work around or setting that needs changing please.  Have Office Pro
2003 SP3 running on XP Pro SP3. <<
--

Bob  Buckland  ?
MS Office System Products MVP

  *Courtesy is not expensive and can pay big dividends*

Bob, thanks for responding. You are my first MS guru on this matter!
To answer your questions...

1. I've been sending the error stats for years - they don't span
years.
2. It's full of all sorts of tech data that I can't copy but starts
with mspview failure - is there any specific bit I can type out for
you?
3. I'm using the HP8200 scanner, I also have the HP6300 installed as
this is another scanner I have at home (laptop used at both sites)
4. Tiff files are my own created using B&W settings using OCR to auto
rotate and straighten. 300 dpi and monochrome. They are generally
multipaged too.
Thanks again - I await your response with great anticipation!

 

[Lester Lane]

Bob, thanks for responding. You are my first MS guru on this matter!
To answer your questions...

1. I've been sending the error stats for years - they don't span
years.
2. It's full of all sorts of tech data that I can't copy but starts
with mspview failure - is there any specific bit I can type out for
you?
3. I'm using the HP8200 scanner, I also have the HP6300 installed as
this is another scanner I have at home (laptop used at both sites)
4. Tiff files are my own created using B&W settings using OCR to auto
rotate and straighten.  300 dpi and monochrome.  They are generally
multipaged too.
Thanks again - I await your response with great anticipation!

I can hardly believe it. Last night a few Automatic MS updates (not
sure what they were) got installed and one of them seems to have fixed
this issue. At last MS - well done!

 

[LBit]

Not done quite so well - I'm searching the posts because my users started
with this same issue yesterday. Worked without error until then. Files that
previously were fine to print now crashes with Mspview failure when clicking
'file' or ctrl-p. Works fine if you click the print icon. Can open and
print same docs with picture viewer or other software, but those don't work
as well for us (these are blueprints in tif format).

MS guru....help!

 

[mwilg]

Bob, or someone else from MS...come on! This is still ongoing! I've also had
this fundamental error in MDI for a while now, and it's bloody annoying!!
Apparently this is as a result of an 'update' that again caused more problems
than it ever fixed, something for which MS is getting way too good at doing!!
The last official response to this was over three months ago in Sept, and
there is now a new post, about the same issue, from earlier this month that
has apparently gone completely unanswered, which does nothing but validate
the original complaint that this is being ignored!
It also validates my decision of a couple of years ago to completely desist
from downloading *any* MS updates whatsoever after the DST corrections
screwed up all the Outlook appointments without actually 'fixing' the DST
date changes! Apparently, that same philosophy should now be applied to all
office updates with the possible exceptions of the junk eMail filter updates;
although even then how much can we trust?
Is this what we are to assume? You tell me!

 

[mwilg]

Ok folks. Here's the fix from some helpful people out there showing personal
initiative. Do note that this will revert these files to their earlier
versions supposedly making them 'vulnerable', but you may, like others of us
decide, that it's more preferrable to have the damn thing work properly in
the first! place!

Fixing File Menu screwup in MDI:

NB: For just the File Menu, you may only need to replace the MSPVIEW.EXE file

SP3 changed a number of files in the MODI folder to April 2007 versions.
From the original Office XP 2003 CD's, the files are located in a Cab folders:

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

Extract the following files from the CAB folders on the Office CD

MO561405.CAB:

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

M4561414.CAB:

MSPFILT.DLL
MSPSCAN.EXE

Replace the updated version of the files in:
C:\Program Files\Common Files\Microsoft Shared\MODI\11.0\

The following may, or may not, be necessary. In my case, the above fix was
more than enough to restore the File Menu, but the original creator of this
fix says that he replaced all these as well. Your call.
(NB: Depending on when you got it, the CD probably does *not* have the 2004
version of the MSPLCRES.DLL file)
Some of these files are in the CAB folders listed above, others maybe
elsewhere. You’ll just to have open each CAB folder on the CD as/if
necessary:

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

Just a final note; although I know the MS people will not be happy to read
this: The creator of this fix also completely stopped downloading anymore of
MS's 'updates' after this, just as I did about a year ago after the nonsense
with the DST stuff (both for OS's as well as Office). To date, I have yet to
be infected or hacked by anything. There are other ways of protecting oneself
from that stuff rather than having to enduring hours of wasted time due to
MS's incompetence or indifference! Just a suggestion.

 

[Beth Melton]

Just a final note; although I know the MS people will not be happy to read
this: The creator of this fix also completely stopped downloading anymore
of
MS's 'updates' after this, just as I did about a year ago after the
nonsense
with the DST stuff (both for OS's as well as Office). To date, I have yet
to
be infected or hacked by anything. There are other ways of protecting
oneself
from that stuff rather than having to enduring hours of wasted time due to
MS's incompetence or indifference! Just a suggestion.

FWIW, these are peer-to-peer support forums, Microsoft doesn't support them.
Occasionally you'll see a question answered by the MS support folks but
that's only because the individual is a MSDN subscriber and they posted
through the managed newsgroups.

IOW, Microsoft won't see your feedback and the answers found in the
newsgroups are from those who show personal initiative -- and now you are
one of them since you shared what you found to help out others encountering
same difficulty. ;-)

 

[Steve Rindsberg]

Bob, or someone else from MS...come on!

Frustrating, I know. But ...

You should understand that the people who respond here are not MS employees,
and MS employees do not offer tech support here. You're not talking to MS
here, just to others like you. In the same boat. Same rusty bucket to bail
with.

You might be better off calling MS' support line.


This is still ongoing! I've also had