mikel1024@verizon.net

On Oct 9, 9:00 pm, mikel1...@verizon.net wrote:
> On Oct 9, 12:25 pm, Matt Twombly
>
>
>
> <MattTwom...@discussions.microsoft.com> wrote:
> > The crash is due to a problem with too many characters in a file name(s) in
> > the Recent File List. Two solutions for now until its fixed:
>
> > 1. Create a Reg file with the following and run it each time the problem
> > happens:
>
> > Windows Registry Editor Version 5.00
>
> > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
>
> > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
>
> > 2. Disable the Recent File List
>
> > At least we don't have to reinstall Office!
>
> > Good Luck to everyone.
>
> > -Matt
>
> > "Matt Twombly" wrote:
> > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > other menu items work except File. If I save the file, open the file and
> > > crash Imaging, repeat this process, on the third iteration through the File
> > > menu will work. After rebooting the machine its back to crashing everytime.
> > > Here is the error as logged in the event viewer:
>
> > > Event ID: 1000
>
> > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > fault address 0x00016537.
>
> > > This is happening on several local workstations running WinXP SP2 as well as
> > > on my Terminal Server running Windows 2003 Server.
>
> > > Any ideas would be appreciated greatly.
>
> > > Thanks!
>
> > > -Matt- Hide quoted text -
>
> > - Show quoted text -
>
> Deleting the recent files list via the registry and disabling recent
> files doesn't work our my machines. We still get the "...encountered
> an error and must close..." error pop up.- Hide quoted text -
>
> - Show quoted text -

To get this to work on our machines using 'Microsoft Office Document
Scanning', we went into 'My Computer' from the desktop and under
'Scanners and Cameras' shortened the scanner's filename to 26
characters. Also put the recent file history settings that were
deleted previously from the registry back in place (couple of them had
really long filenames). It still works. For us it appears the
presence of recent file history with long filenames had nothing to do
with the '...Document Scanning' not working.

Zsolt Vasvari

That does work! Thanks. I was going crazy. I can just imagine how many
people will have this problem. The 26 character limitation is very easy to
exceed with a manufacturer name such as "Hewlett-Packard." That's 15 right
there.

Zsolt


"mikel1024@verizon.net" wrote:

> On Oct 9, 9:00 pm, mikel1...@verizon.net wrote:
> > On Oct 9, 12:25 pm, Matt Twombly
> >
> >
> >
> > <MattTwom...@discussions.microsoft.com> wrote:
> > > The crash is due to a problem with too many characters in a file name(s) in
> > > the Recent File List. Two solutions for now until its fixed:
> >
> > > 1. Create a Reg file with the following and run it each time the problem
> > > happens:
> >
> > > Windows Registry Editor Version 5.00
> >
> > > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > > 2. Disable the Recent File List
> >
> > > At least we don't have to reinstall Office!
> >
> > > Good Luck to everyone.
> >
> > > -Matt
> >
> > > "Matt Twombly" wrote:
> > > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > > other menu items work except File. If I save the file, open the file and
> > > > crash Imaging, repeat this process, on the third iteration through the File
> > > > menu will work. After rebooting the machine its back to crashing everytime.
> > > > Here is the error as logged in the event viewer:
> >
> > > > Event ID: 1000
> >
> > > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > > fault address 0x00016537.
> >
> > > > This is happening on several local workstations running WinXP SP2 as well as
> > > > on my Terminal Server running Windows 2003 Server.
> >
> > > > Any ideas would be appreciated greatly.
> >
> > > > Thanks!
> >
> > > > -Matt- Hide quoted text -
> >
> > > - Show quoted text -
> >
> > Deleting the recent files list via the registry and disabling recent
> > files doesn't work our my machines. We still get the "...encountered
> > an error and must close..." error pop up.- Hide quoted text -
> >
> > - Show quoted text -
>
> To get this to work on our machines using 'Microsoft Office Document
> Scanning', we went into 'My Computer' from the desktop and under
> 'Scanners and Cameras' shortened the scanner's filename to 26
> characters. Also put the recent file history settings that were
> deleted previously from the registry back in place (couple of them had
> really long filenames). It still works. For us it appears the
> presence of recent file history with long filenames had nothing to do
> with the '...Document Scanning' not working.
>
>

mikel1024@verizon.net

I wouldn't say that 26 is the limit. We didn't experiment with the
number of characters in the name. We just abbreviated something
really long to something shorter, that still made naming sense, and it
happened to be 26 characters. Names with a few more characters than
26 might be ok.

Zsolt Vasvari wrote:
> That does work! Thanks. I was going crazy. I can just imagine how many
> people will have this problem. The 26 character limitation is very easy to
> exceed with a manufacturer name such as "Hewlett-Packard." That's 15 right
> there.
>
> Zsolt
>
>
> "mikel1024@verizon.net" wrote:
>
> > On Oct 9, 9:00 pm, mikel1...@verizon.net wrote:
> > > On Oct 9, 12:25 pm, Matt Twombly
> > >
> > >
> > >
> > > <MattTwom...@discussions.microsoft.com> wrote:
> > > > The crash is due to a problem with too many characters in a file name(s) in
> > > > the Recent File List. Two solutions for now until its fixed:
> > >
> > > > 1. Create a Reg file with the following and run it each time the problem
> > > > happens:
> > >
> > > > Windows Registry Editor Version 5.00
> > >
> > > > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> > >
> > > > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> > >
> > > > 2. Disable the Recent File List
> > >
> > > > At least we don't have to reinstall Office!
> > >
> > > > Good Luck to everyone.
> > >
> > > > -Matt
> > >
> > > > "Matt Twombly" wrote:
> > > > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > > > other menu items work except File. If I save the file, open the file and
> > > > > crash Imaging, repeat this process, on the third iteration through the File
> > > > > menu will work. After rebooting the machine its back to crashing everytime.
> > > > > Here is the error as logged in the event viewer:
> > >
> > > > > Event ID: 1000
> > >
> > > > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > > > fault address 0x00016537.
> > >
> > > > > This is happening on several local workstations running WinXP SP2 as well as
> > > > > on my Terminal Server running Windows 2003 Server.
> > >
> > > > > Any ideas would be appreciated greatly.
> > >
> > > > > Thanks!
> > >
> > > > > -Matt- Hide quoted text -
> > >
> > > > - Show quoted text -
> > >
> > > Deleting the recent files list via the registry and disabling recent
> > > files doesn't work our my machines. We still get the "...encountered
> > > an error and must close..." error pop up.- Hide quoted text -
> > >
> > > - Show quoted text -
> >
> > To get this to work on our machines using 'Microsoft Office Document
> > Scanning', we went into 'My Computer' from the desktop and under
> > 'Scanners and Cameras' shortened the scanner's filename to 26
> > characters. Also put the recent file history settings that were
> > deleted previously from the registry back in place (couple of them had
> > really long filenames). It still works. For us it appears the
> > presence of recent file history with long filenames had nothing to do
> > with the '...Document Scanning' not working.
> >
> >

Mark Dowd

Folks,

I tried all the repair solutions offered in this thread but with no luck. I wasn't that keen on removing and re-installing Office, so I thought I would follow up on the mention of long file names in the MRU list as I recalled that I had been sent an e-mail with a .tif attachment with an unusually long file name just before I started to have the problem with MDI. I found two registry keys with what looked like the MRU file name list and deleted the text from the key values and bingo MDI is working properly again!

The keys are...

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\C ommon\Open Find\Microsoft Document Imaging\Settings\Save As\File Name MRU

and

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\C ommon\Open Find\Microsoft Document Imaging\Settings\Open\File Name MRU

Hope this helps.

Mark.

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Arthur Priver

How do we fix the association with TIF? I did not see the TIF entry in the
file table.
Second, where do we disable the Recent File List? This bug is very
annoying. Thanks.
--
Arthur Priver


"Matt Twombly" wrote:

> The crash is due to a problem with too many characters in a file name(s) in
> the Recent File List. Two solutions for now until its fixed:
>
> 1. Create a Reg file with the following and run it each time the problem
> happens:
>
> Windows Registry Editor Version 5.00
>
> [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
>
> [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
>
> 2. Disable the Recent File List
>
> At least we don't have to reinstall Office!
>
> Good Luck to everyone.
>
> -Matt
>
> "Matt Twombly" wrote:
>
> > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > lost the association with TIF but I quickly fixed that. Now, when I open a
> > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > other menu items work except File. If I save the file, open the file and
> > crash Imaging, repeat this process, on the third iteration through the File
> > menu will work. After rebooting the machine its back to crashing everytime.
> > Here is the error as logged in the event viewer:
> >
> > Event ID: 1000
> >
> > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > fault address 0x00016537.
> >
> > This is happening on several local workstations running WinXP SP2 as well as
> > on my Terminal Server running Windows 2003 Server.
> >
> > Any ideas would be appreciated greatly.
> >
> > Thanks!
> >
> > -Matt
> >

TaurArian [MS-MVP]

After you install Office 2003 SP3, the Microsoft Office Document Imaging program may not
work as expected.
http://support.microsoft.com/kb/938813

--
====================================
TaurArian [MS-MVP] 2005-2008 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Defending your machine: http://defendingyourmachine2.blogspot.com/
http://taurarian.mvps.org/index.htm

Emails will not be acknowledged - please post to the newsgroup so all may benefit.


"Arthur Priver" <ArthurPriver@discussions.microsoft.com> wrote in message
news:5052E937-A3CF-4A65-B43B-AA859E0DC5D0@microsoft.com...
| How do we fix the association with TIF? I did not see the TIF entry in the
| file table.
| Second, where do we disable the Recent File List? This bug is very
| annoying. Thanks.
| --
| Arthur Priver
|
|
| "Matt Twombly" wrote:
|
| > The crash is due to a problem with too many characters in a file name(s) in
| > the Recent File List. Two solutions for now until its fixed:
| >
| > 1. Create a Reg file with the following and run it each time the problem
| > happens:
| >
| > Windows Registry Editor Version 5.00
| >
| > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
| >
| > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
| >
| > 2. Disable the Recent File List
| >
| > At least we don't have to reinstall Office!
| >
| > Good Luck to everyone.
| >
| > -Matt
| >
| > "Matt Twombly" wrote:
| >
| > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
| > > lost the association with TIF but I quickly fixed that. Now, when I open a
| > > TIF file and go to the File menu it crashes as soon as I hit File. All the
| > > other menu items work except File. If I save the file, open the file and
| > > crash Imaging, repeat this process, on the third iteration through the File
| > > menu will work. After rebooting the machine its back to crashing everytime.
| > > Here is the error as logged in the event viewer:
| > >
| > > Event ID: 1000
| > >
| > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
| > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
| > > fault address 0x00016537.
| > >
| > > This is happening on several local workstations running WinXP SP2 as well as
| > > on my Terminal Server running Windows 2003 Server.
| > >
| > > Any ideas would be appreciated greatly.
| > >
| > > Thanks!
| > >
| > > -Matt
| > >

mwallen

so how do we disable to the recent file list for the document imaging
program. i removed the long filenames from the registry and it fixed
the problem but as soon as a long file is opened agian it starts
crashing agian. can someone tell me how to diable the list all
together so it stops?


--
mwallen
------------------------------------------------------------------------
mwallen's Profile: http://www.citrixguide.com1848
View this thread: http://www.citrixguide.com/showthread.php?t=2475

mwallen

so how do we disable the recent file list. i deleted the items in it
through the registry and it fixed the problem, but as soon as i open a
longer file name it start having the same problem. so how do i diable
it from keeping the file names stored at all?


--
mwallen
------------------------------------------------------------------------
mwallen's Profile: http://forums.techarena.in/member.php?userid=33696
View this thread: http://forums.techarena.in/showthread.php?t=826981

http://forums.techarena.in

Arthur Priver

Has this Document Imaging problem been fixed yet?
--
Arthur Priver


"Arthur Priver" wrote:

> How do we fix the association with TIF? I did not see the TIF entry in the
> file table.
> Second, where do we disable the Recent File List? This bug is very
> annoying. Thanks.
> --
> Arthur Priver
>
>
> "Matt Twombly" wrote:
>
> > The crash is due to a problem with too many characters in a file name(s) in
> > the Recent File List. Two solutions for now until its fixed:
> >
> > 1. Create a Reg file with the following and run it each time the problem
> > happens:
> >
> > Windows Registry Editor Version 5.00
> >
> > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > 2. Disable the Recent File List
> >
> > At least we don't have to reinstall Office!
> >
> > Good Luck to everyone.
> >
> > -Matt
> >
> > "Matt Twombly" wrote:
> >
> > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > other menu items work except File. If I save the file, open the file and
> > > crash Imaging, repeat this process, on the third iteration through the File
> > > menu will work. After rebooting the machine its back to crashing everytime.
> > > Here is the error as logged in the event viewer:
> > >
> > > Event ID: 1000
> > >
> > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > fault address 0x00016537.
> > >
> > > This is happening on several local workstations running WinXP SP2 as well as
> > > on my Terminal Server running Windows 2003 Server.
> > >
> > > Any ideas would be appreciated greatly.
> > >
> > > Thanks!
> > >
> > > -Matt
> > >

Arthur Priver

Has this Document Imaging problem been fixed yet?
--
Arthur Priver


"Arthur Priver" wrote:

> How do we fix the association with TIF? I did not see the TIF entry in the
> file table.
> Second, where do we disable the Recent File List? This bug is very
> annoying. Thanks.
> --
> Arthur Priver
>
>
> "Matt Twombly" wrote:
>
> > The crash is due to a problem with too many characters in a file name(s) in
> > the Recent File List. Two solutions for now until its fixed:
> >
> > 1. Create a Reg file with the following and run it each time the problem
> > happens:
> >
> > Windows Registry Editor Version 5.00
> >
> > [-HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > [HKEY_CURRENT_USER\Software\Microsoft\MSPaper 11.0\Recent File List]
> >
> > 2. Disable the Recent File List
> >
> > At least we don't have to reinstall Office!
> >
> > Good Luck to everyone.
> >
> > -Matt
> >
> > "Matt Twombly" wrote:
> >
> > > I use Document Imaging to read our fax tiff files. After updating to SP3 we
> > > lost the association with TIF but I quickly fixed that. Now, when I open a
> > > TIF file and go to the File menu it crashes as soon as I hit File. All the
> > > other menu items work except File. If I save the file, open the file and
> > > crash Imaging, repeat this process, on the third iteration through the File
> > > menu will work. After rebooting the machine its back to crashing everytime.
> > > Here is the error as logged in the event viewer:
> > >
> > > Event ID: 1000
> > >
> > > Faulting application mspview.exe, version 11.0.8166.2, stamp 4616c203,
> > > faulting module mspview.exe, version 11.0.8166.2, stamp 4616c203, debug? 0,
> > > fault address 0x00016537.
> > >
> > > This is happening on several local workstations running WinXP SP2 as well as
> > > on my Terminal Server running Windows 2003 Server.
> > >
> > > Any ideas would be appreciated greatly.
> > >
> > > Thanks!
> > >
> > > -Matt
> > >