Word cannot read temporary file

[Richard_Starling]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Over the last two months I have experienced a major problem with Word (12.2.4) when dealing with Word attachments opened from Lotus Notes (8.5.1). After opening Word attachments at some indeterminate time afterwards I will receive the message 'Word encountered an error reading xxxxx.doc. The file may be corrupt'. Clicking OK results in 'Word failed reading from this file'. The retry button here just loops back to the same message, pressing Cancel results on 'Word encountered an error reading xxxxx.doc. The file may be corrupt'. Pressing cancel here gives 'Word has lost data due to a bad network connection or missing floppy. Documents relying on this data are going to be saved and then closed'. Pressing OK results in 'The document may contain text which will be lost on conversion.....etc etc'. Pressing continue with save loops back to previous messages. The only way put is to kill Word from Activity Monitor and any unsaved work on other documents is lost.

This only occurs with Word, not Excel or Powerpoint and does not occur for documents loaded from the file system. I have tried the usual repair of disk permissions, deletion of Normal.dotm and even ensured any unconnected NFS shares are removed using NFS Manager. I am at a loss as to what to do next. I suspect this issue may have arisen when going to SL 10.6.3 or to Office 12.2.4 or perhaps to Notes 8.5.1 FP1 which all happened around the same time.

 

[CyberTaz]

I believe the solution may be relatively simple - stop opening the
attachments Seriously, Open the attachment only for the purpose of
reading it. If it's worth keeping, save the attached file to you local drive
then open that copy & work with it.

In simple terms, 'attachments' aren't Word docs, Excel files, etc. but are
more like sets of instructions to the recipient's system of what type of
program is needed to view them & what type of file should be created from
them. Since they don't really exist as a 'file' reusing the attachment will
eventually result in the type of behavior you describe.

It could go deeper than that, though, depending on what's actually happening
on the sender's end. Unfortunately you don't have much control over that,
but since it sounds like the attachments are OK when initially received I
don't believe that's the problem.

HTH |:>)
Bob Jones
[MVP] Office:Mac

 

[Richard_Starling]

Bob,

Sorry, this isn't feasible and neither has it been necessary for the six years I've been using Notes and Office 2004/2008. Many attachments don't need to be saved, but read and then discarded and saving to the file system and reloading is a real pain. Something has changed and broken what I believe is the vast majority of peoples workflow for dealing with mail and attachments.I'm not pointing the finger at Word, Notes or SL but as a group of products they are no longer working in the way they should, for me at least.

 

[John_McGhie_[MVP]]

Hi Richard:

Well, Bob is correct. Behind the scenes, Notes is creating a temporary file
that it hands to Word, pretending it is a document.

Word doesn't care, it opens the file handle it is handed. If you speak to
your Notes administrator, they may be able to tell you where the temporary
file is: it may be entirely in memory.

If Notes then decides to do a little house-keeping and remove the temporary
file, Word will indeed lock up. It's trying to give you the opportunity to
"Save As" the file to somewhere, so you do not lose data.

If you always save attachments to disk before opening, you won't get the
problem. You will also avoid the drive-by shootings from the malware
creators of this world

Microsoft has not recently made any changes to what Word does.

Cheers

Bob,

Sorry, this isn't feasible and neither has it been necessary for the six years
I've been using Notes and Office 2004/2008. Many attachments don't need to be
saved, but read and then discarded and saving to the file system and reloading
is a real pain. Something has changed and broken what I believe is the vast
majority of peoples workflow for dealing with mail and attachments.I'm not
pointing the finger at Word, Notes or SL but as a group of products they are
no longer working in the way they should, for me at least.

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]

 

[adamr]

You all might want to chalk this up to detaching attachments but I agree with Richard. I've been using Mac + Office for 4 years and only in the last 2 months have I had this exact same problem. It's also worth noting I don't edit the attachments. I simply open them and view them. Many times, I leave them open and come back to them (in some cases) hours later.. but still not editing them. And I get this error. I'm on 12.2.4 as well. Below is the log from the latest crash.

Maybe something changed with an OSX update.. who knows. But it's 100% different behavior now than before and is unbelievably annoying.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-06-01 21:47:53 -0400
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.2.4.100205
Crashed Module Name: Microsoft Word
Crashed Module Version: 12.2.4.100205
Crashed Module Offset: 0x002197d4
Blame Module Name: Microsoft Word
Blame Module Version: 12.2.4.100205
Blame Module Offset: 0x002197d4
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0021a7d4 in __mh_execute_header + 0x002197D4 (Microsoft Word + 0x002197d4)
# 2 0x01af7f1e in _LsCreateLine + 0x0000042A (MSLS3 + 0x00008f1e)
# 3 0x002072ed in __mh_execute_header + 0x002062ED (Microsoft Word + 0x002062ed)
# 4 0x0020d73c in __mh_execute_header + 0x0020C73C (Microsoft Word + 0x0020c73c)
# 5 0x0060d1f2 in _wdCommandDispatch + 0x002E88B6 (Microsoft Word + 0x0060c1f2)
# 6 0x00b79591 in _wdGetApplicationObject + 0x0043A9C7 (Microsoft Word + 0x00b78591)
# 7 0x00af71a1 in _wdGetApplicationObject + 0x003B85D7 (Microsoft Word + 0x00af61a1)
# 8 0x00adbbc9 in _wdGetApplicationObject + 0x0039CFFF (Microsoft Word + 0x00adabc9)
# 9 0x00add29c in _wdGetApplicationObject + 0x0039E6D2 (Microsoft Word + 0x00adc29c)
# 10 0x0057c464 in _wdCommandDispatch + 0x00257B28 (Microsoft Word + 0x0057b464)
# 11 0x0057f3ab in _wdCommandDispatch + 0x0025AA6F (Microsoft Word + 0x0057e3ab)
# 12 0x0057f4b2 in _wdCommandDispatch + 0x0025AB76 (Microsoft Word + 0x0057e4b2)
# 13 0x0035c50c in _wdCommandDispatch + 0x00037BD0 (Microsoft Word + 0x0035b50c)
# 14 0x0035d67d in _wdCommandDispatch + 0x00038D41 (Microsoft Word + 0x0035c67d)
# 15 0x0081bf6a in _wdGetApplicationObject + 0x000DD3A0 (Microsoft Word + 0x0081af6a)
# 16 0x0081c428 in _wdGetApplicationObject + 0x000DD85E (Microsoft Word + 0x0081b428)
# 17 0x008196be in _wdGetApplicationObject + 0x000DAAF4 (Microsoft Word + 0x008186be)
# 18 0x00819739 in _wdGetApplicationObject + 0x000DAB6F (Microsoft Word + 0x00818739)
# 19 0x00afd712 in _wdGetApplicationObject + 0x003BEB48 (Microsoft Word + 0x00afc712)
# 20 0x00b020cb in _wdGetApplicationObject + 0x003C3501 (Microsoft Word + 0x00b010cb)
# 21 0x00b02fc6 in _wdGetApplicationObject + 0x003C43FC (Microsoft Word + 0x00b01fc6)
# 22 0x006f4723 in _wdCommandDispatch + 0x003CFDE7 (Microsoft Word + 0x006f3723)
# 23 0x006f7533 in _wdCommandDispatch + 0x003D2BF7 (Microsoft Word + 0x006f6533)
# 24 0x006f76e7 in _wdCommandDispatch + 0x003D2DAB (Microsoft Word + 0x006f66e7)
# 25 0x00408016 in _wdCommandDispatch + 0x000E36DA (Microsoft Word + 0x00407016)
# 26 0x00409fff in _wdCommandDispatch + 0x000E56C3 (Microsoft Word + 0x00408fff)
# 27 0x0040a382 in _wdCommandDispatch + 0x000E5A46 (Microsoft Word + 0x00409382)
# 28 0x003945e2 in _wdCommandDispatch + 0x0006FCA6 (Microsoft Word + 0x003935e2)
# 29 0x0081d857 in _wdGetApplicationObject + 0x000DEC8D (Microsoft Word + 0x0081c857)
# 30 0x0081dd3b in _wdGetApplicationObject + 0x000DF171 (Microsoft Word + 0x0081cd3b)
# 31 0x02159ae6 in _MsoFCreateToolbarSet + 0x000011BE (MicrosoftOffice + 0x0033fae6)
# 32 0x016150af in _McpFCreateIMcpMRFssOffice10 + 0x00000D47 (MicrosoftComponentPlugin + 0x0002c0af)
# 33 0x016151ef in _McpFCreateIMcpMRFssOffice10 + 0x00000E87 (Micros

 

[John_McGhie_[MVP]]

Well, I am sure it is annoying, but I am not at all sure you have the same
issue as Richard.

And since Microsoft hasn't changed anything in the past couple of months, I
am not sure that this is their issue. From that log, certainly something is
throwing Word on the floor while it is working on a document. But I can't
tell what, or why.

Only the developers can read the logs well enough to take a guess at the
cause.

Cheers

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel
You all might want to chalk this up to detaching attachments but I agree with
Richard. I've been using Mac + Office for 4 years and only in the last 2
months have I had this exact same problem. It's also worth noting I don't
edit the attachments. I simply open them and view them. Many times, I leave
them open and come back to them (in some cases) hours later.. but still not
editing them. And I get this error. I'm on 12.2.4 as well. Below is the log
from the latest crash.

Maybe something changed with an OSX update.. who knows. But it's 100%
different behavior now than before and is unbelievably annoying.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-06-01 21:47:53 -0400
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.2.4.100205
Crashed Module Name: Microsoft Word
Crashed Module Version: 12.2.4.100205
Crashed Module Offset: 0x002197d4
Blame Module Name: Microsoft Word
Blame Module Version: 12.2.4.100205
Blame Module Offset: 0x002197d4
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x0021a7d4 in __mh_execute_header + 0x002197D4 (Microsoft Word +
0x002197d4)
# 2 0x01af7f1e in _LsCreateLine + 0x0000042A (MSLS3 + 0x00008f1e)
# 3 0x002072ed in __mh_execute_header + 0x002062ED (Microsoft Word +
0x002062ed)
# 4 0x0020d73c in __mh_execute_header + 0x0020C73C (Microsoft Word +
0x0020c73c)
# 5 0x0060d1f2 in _wdCommandDispatch + 0x002E88B6 (Microsoft Word +
0x0060c1f2)
# 6 0x00b79591 in _wdGetApplicationObject + 0x0043A9C7 (Microsoft Word +
0x00b78591)
# 7 0x00af71a1 in _wdGetApplicationObject + 0x003B85D7 (Microsoft Word +
0x00af61a1)
# 8 0x00adbbc9 in _wdGetApplicationObject + 0x0039CFFF (Microsoft Word +
0x00adabc9)
# 9 0x00add29c in _wdGetApplicationObject + 0x0039E6D2 (Microsoft Word +
0x00adc29c)
# 10 0x0057c464 in _wdCommandDispatch + 0x00257B28 (Microsoft Word +
0x0057b464)
# 11 0x0057f3ab in _wdCommandDispatch + 0x0025AA6F (Microsoft Word +
0x0057e3ab)
# 12 0x0057f4b2 in _wdCommandDispatch + 0x0025AB76 (Microsoft Word +
0x0057e4b2)
# 13 0x0035c50c in _wdCommandDispatch + 0x00037BD0 (Microsoft Word +
0x0035b50c)
# 14 0x0035d67d in _wdCommandDispatch + 0x00038D41 (Microsoft Word +
0x0035c67d)
# 15 0x0081bf6a in _wdGetApplicationObject + 0x000DD3A0 (Microsoft Word +
0x0081af6a)
# 16 0x0081c428 in _wdGetApplicationObject + 0x000DD85E (Microsoft Word +
0x0081b428)
# 17 0x008196be in _wdGetApplicationObject + 0x000DAAF4 (Microsoft Word +
0x008186be)
# 18 0x00819739 in _wdGetApplicationObject + 0x000DAB6F (Microsoft Word +
0x00818739)
# 19 0x00afd712 in _wdGetApplicationObject + 0x003BEB48 (Microsoft Word +
0x00afc712)
# 20 0x00b020cb in _wdGetApplicationObject + 0x003C3501 (Microsoft Word +
0x00b010cb)
# 21 0x00b02fc6 in _wdGetApplicationObject + 0x003C43FC (Microsoft Word +
0x00b01fc6)
# 22 0x006f4723 in _wdCommandDispatch + 0x003CFDE7 (Microsoft Word +
0x006f3723)
# 23 0x006f7533 in _wdCommandDispatch + 0x003D2BF7 (Microsoft Word +
0x006f6533)
# 24 0x006f76e7 in _wdCommandDispatch + 0x003D2DAB (Microsoft Word +
0x006f66e7)
# 25 0x00408016 in _wdCommandDispatch + 0x000E36DA (Microsoft Word +
0x00407016)
# 26 0x00409fff in _wdCommandDispatch + 0x000E56C3 (Microsoft Word +
0x00408fff)
# 27 0x0040a382 in _wdCommandDispatch + 0x000E5A46 (Microsoft Word +
0x00409382)
# 28 0x003945e2 in _wdCommandDispatch + 0x0006FCA6 (Microsoft Word +
0x003935e2)
# 29 0x0081d857 in _wdGetApplicationObject + 0x000DEC8D (Microsoft Word +
0x0081c857)
# 30 0x0081dd3b in _wdGetApplicationObject + 0x000DF171 (Microsoft Word +
0x0081cd3b)
# 31 0x02159ae6 in _MsoFCreateToolbarSet + 0x000011BE (MicrosoftOffice +
0x0033fae6)
# 32 0x016150af in _McpFCreateIMcpMRFssOffice10 + 0x00000D47
(MicrosoftComponentPlugin + 0x0002c0af)
# 33 0x016151ef in _McpFCreateIMcpMRFssOffice10 + 0x00000E87 (Micros

--

The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]

 

[jena.snyder]

The same thing has happened to me, but not in trying to open an attachment -- it's when I try to open Word.

I was working on a document yesterday, Word crashed, and now I can't open the program, let alone the document. Suggestions?