Friday, April 16, 2010

Microsoft Office Document Imaging.... Error with Office Service Pack 3... is there a known fix??

I'm trying to assist an employee who uses the Microsoft Document Imaging tool to print and send files to other clients who don't have MS Word or Excel installed. The problem we get is, whenever clicking on the file menu in the document Imaging software, we receive an error message:


AppName: mspview.exe MSPView Failure. Apparently, there is a known issue with Microsoft Office Service Pack 3 causing the problem, as this occurs only when SP3 is installed. This occurs only when viewing a .MDI file in the document imaging application. The error message causes the application to close completely.


The problem we have with this is, this employee already has several files in the .MDI format that he works with. Before he has me convert them all to .PDF (which would probably be the best solution), we was wondering if there was any known fix for this problem. Dont try searching google or support.microsoft.com, as there is very little relevant info google, and absolutely nothing on MS Technet.

Microsoft Office Document Imaging.... Error with Office Service Pack 3... is there a known fix??
Maybe instead of using a .mdi file, you can save it as a .tiff file. It is still a tagged image, compatible with more (and by more i mean less recent) releases of Microsoft Office, and I believe you can still import them into a .pdf file. The last source gives you step-by-step instructions on how, in six Microsoft Office 2003 programs including Word and Excel, to save a document as a .tiff file.
Reply:The real problem is caused by a long file name in recent files of Microsoft Document Imaging.


To resolve:


HKEY_CURRENT_USER\Software\M... 11.0\Recent File List]


HKEY_CURRENT_USER\Software\M... 11.0\Persist File Name] Report It

Reply:Try looking in the event viewer and posting the error codes with your question or better still, search Google and technet with the same error codes and events instead of the basic messagebox errors


No comments:

Post a Comment