Some additional information:

I originally had the problem when I was working in a networked folder: I
tried to save the file and got a permission error. So I copied the file to
a local folder, opened it and did some editing. When I tried to save, same
problem. This time, though, after Word wrote rescue.asd, I tried to save
the file with another name. No problem.

So, I'm coming to the conclusion that the permission error occurs when Word
tries to rename or delete the old file. I can say that after the failure
the original file is gone, so it clearly deleted the original file.

This has happened 3 times now with one specific file; I've not seen it
happen with any others. This file contains a lot of graphics - could this
be the problem?
--
Regards,
Dean

Just for interest, can you open the bad file with the following procedure:
Open and Repair, in the File > Open dialog, there is a downward-pointing
arrow on the right end of the Open button. After choosing the file, click
that arrow to get a small menu. Click "Open and Repair" in that menu.
See what error fix it comes up with, if any.
DeanH

"DPM" wrote:

> Some additional information:
>
> I originally had the problem when I was working in a networked folder: I
> tried to save the file and got a permission error. So I copied the file to
> a local folder, opened it and did some editing. When I tried to save, same
> problem. This time, though, after Word wrote rescue.asd, I tried to save
> the file with another name. No problem.
>
> So, I'm coming to the conclusion that the permission error occurs when Word
> tries to rename or delete the old file. I can say that after the failure
> the original file is gone, so it clearly deleted the original file.
>
> This has happened 3 times now with one specific file; I've not seen it
> happen with any others. This file contains a lot of graphics - could this
> be the problem?
> --
> Regards,
> Dean
>
>
>

A popup declares: "Microsoft Office Word cannot open this file because it is
an unsupported file type."

Either the AutoRecovery backup file mechanism is broken or I don't
understand how it works. IMNSHO, if I can't point Word to a .asd file and
have it try to open that file, what good is it?

Based on my experience, if this happens to you ALWAYS try to save the file
with a different file name. Don't trust AutoRecovery - it's broken.

Dean

"DeanH" <DeanH@discussions.microsoft.com> wrote in message
news:A869F9BF-D127-4B1F-8BFA-7BA7C1146ADA@microsoft.com...
> Just for interest, can you open the bad file with the following procedure:
> Open and Repair, in the File > Open dialog, there is a downward-pointing
> arrow on the right end of the Open button. After choosing the file, click
> that arrow to get a small menu. Click "Open and Repair" in that menu.
> See what error fix it comes up with, if any.
> DeanH
>
> "DPM" wrote:
>
>> Some additional information:
>>
>> I originally had the problem when I was working in a networked folder: I
>> tried to save the file and got a permission error. So I copied the file
>> to
>> a local folder, opened it and did some editing. When I tried to save,
>> same
>> problem. This time, though, after Word wrote rescue.asd, I tried to save
>> the file with another name. No problem.
>>
>> So, I'm coming to the conclusion that the permission error occurs when
>> Word
>> tries to rename or delete the old file. I can say that after the failure
>> the original file is gone, so it clearly deleted the original file.
>>
>> This has happened 3 times now with one specific file; I've not seen it
>> happen with any others. This file contains a lot of graphics - could
>> this
>> be the problem?
>> --
>> Regards,
>> Dean
>>
>>
>>

I actually meant to try Open & Repair on the duff Word file that is having
the problem not the asd file. ie "fix the problem" not "fiddle with the
result".

"DPM" wrote:

> A popup declares: "Microsoft Office Word cannot open this file because it is
> an unsupported file type."
>
> Either the AutoRecovery backup file mechanism is broken or I don't
> understand how it works. IMNSHO, if I can't point Word to a .asd file and
> have it try to open that file, what good is it?
>
> Based on my experience, if this happens to you ALWAYS try to save the file
> with a different file name. Don't trust AutoRecovery - it's broken.
>
> Dean
>
> "DeanH" <DeanH@discussions.microsoft.com> wrote in message
> news:A869F9BF-D127-4B1F-8BFA-7BA7C1146ADA@microsoft.com...
> > Just for interest, can you open the bad file with the following procedure:
> > Open and Repair, in the File > Open dialog, there is a downward-pointing
> > arrow on the right end of the Open button. After choosing the file, click
> > that arrow to get a small menu. Click "Open and Repair" in that menu.
> > See what error fix it comes up with, if any.
> > DeanH
> >
> > "DPM" wrote:
> >
> >> Some additional information:
> >>
> >> I originally had the problem when I was working in a networked folder: I
> >> tried to save the file and got a permission error. So I copied the file
> >> to
> >> a local folder, opened it and did some editing. When I tried to save,
> >> same
> >> problem. This time, though, after Word wrote rescue.asd, I tried to save
> >> the file with another name. No problem.
> >>
> >> So, I'm coming to the conclusion that the permission error occurs when
> >> Word
> >> tries to rename or delete the old file. I can say that after the failure
> >> the original file is gone, so it clearly deleted the original file.
> >>
> >> This has happened 3 times now with one specific file; I've not seen it
> >> happen with any others. This file contains a lot of graphics - could
> >> this
> >> be the problem?
> >> --
> >> Regards,
> >> Dean
> >>
> >>
> >>
>
>
>

Sorry. I misunderstood.

The answer is: no can do. By the time Word has finished this debacle the
original file is gone. The only thing *LEFT* is the .asd. I'd love to "fix
the problem", but the only choice left is either "fiddle with the result" or
go back to a backup and start over.


"DeanH" <DeanH@discussions.microsoft.com> wrote in message
news:100A8319-2907-4389-B20C-EB429F7DCA59@microsoft.com...
>I actually meant to try Open & Repair on the duff Word file that is having
> the problem not the asd file. ie "fix the problem" not "fiddle with the
> result".
>
> "DPM" wrote:
>
>> A popup declares: "Microsoft Office Word cannot open this file because it
>> is
>> an unsupported file type."
>>
>> Either the AutoRecovery backup file mechanism is broken or I don't
>> understand how it works. IMNSHO, if I can't point Word to a .asd file
>> and
>> have it try to open that file, what good is it?
>>
>> Based on my experience, if this happens to you ALWAYS try to save the
>> file
>> with a different file name. Don't trust AutoRecovery - it's broken.
>>
>> Dean
>>
>> "DeanH" <DeanH@discussions.microsoft.com> wrote in message
>> news:A869F9BF-D127-4B1F-8BFA-7BA7C1146ADA@microsoft.com...
>> > Just for interest, can you open the bad file with the following
>> > procedure:
>> > Open and Repair, in the File > Open dialog, there is a
>> > downward-pointing
>> > arrow on the right end of the Open button. After choosing the file,
>> > click
>> > that arrow to get a small menu. Click "Open and Repair" in that menu.
>> > See what error fix it comes up with, if any.
>> > DeanH
>> >
>> > "DPM" wrote:
>> >
>> >> Some additional information:
>> >>
>> >> I originally had the problem when I was working in a networked folder:
>> >> I
>> >> tried to save the file and got a permission error. So I copied the
>> >> file
>> >> to
>> >> a local folder, opened it and did some editing. When I tried to save,
>> >> same
>> >> problem. This time, though, after Word wrote rescue.asd, I tried to
>> >> save
>> >> the file with another name. No problem.
>> >>
>> >> So, I'm coming to the conclusion that the permission error occurs when
>> >> Word
>> >> tries to rename or delete the old file. I can say that after the
>> >> failure
>> >> the original file is gone, so it clearly deleted the original file.
>> >>
>> >> This has happened 3 times now with one specific file; I've not seen it
>> >> happen with any others. This file contains a lot of graphics - could
>> >> this
>> >> be the problem?
>> >> --
>> >> Regards,
>> >> Dean
>> >>
>> >>
>> >>
>>
>>
>>

Hi DPM,

Have you installed Office 2007 Service Pack 1? There was an issue with Rescue.ASD overwriting the original file after trying to
edit the Rescue file in some cases that SP1 addressed.

What is the size of the Rescue.asd file? Is there also a Rescue.docx

If you rename either file to .doc and start Word while holding the control key can you open the file? If not then it may also be
corrupted.

============
<<"DPM" <dm@junk.com> wrote in message news:eRFLTpCiIHA.5820@TK2MSFTNGP04.phx.gbl...
Sorry. I misunderstood.

The answer is: no can do. By the time Word has finished this debacle the
original file is gone. The only thing *LEFT* is the .asd. I'd love to "fix
the problem", but the only choice left is either "fiddle with the result" or
go back to a backup and start over. >>
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Bob,

Thanks for responding...comments below:

"Bob Buckland ?:-)" <75214.226(At Beautiful Downtown)compuserve.com> wrote
in message news:O08$EEDiIHA.5968@TK2MSFTNGP04.phx.gbl...
> Hi DPM,
>
> Have you installed Office 2007 Service Pack 1? There was an issue with
> Rescue.ASD overwriting the original file after trying to
> edit the Rescue file in some cases that SP1 addressed.
>
No. I was unaware of SP1 until just recently. I'm behind a domain server
running WSUS, and I naively assumed that any Office updates would be pushed
down that way.

BTW, the original .docx file was on a networked drive folder; the rescue
file always ends up in My Documents. I thought the problem might occur when
Word is trying to rename the original file and then writing the new version.
There is a file with an apparently correct backup filename ("~$xxx.docx") in
the network folder, but it's only 1kb.

> What is the size of the Rescue.asd file? Is there also a Rescue.docx
>
Rescue.asd = 1082kb
No Rescue.docx.
Original .docx file: ~580kb

> If you rename either file to .doc and start Word while holding the control
> key can you open the file? If not then it may also be
> corrupted.
>
No. I get the same "unsupported file type" message.


> ============
> <<"DPM" <dm@junk.com> wrote in message
> news:eRFLTpCiIHA.5820@TK2MSFTNGP04.phx.gbl...
> Sorry. I misunderstood.
>
> The answer is: no can do. By the time Word has finished this debacle the
> original file is gone. The only thing *LEFT* is the .asd. I'd love to
> "fix
> the problem", but the only choice left is either "fiddle with the result"
> or
> go back to a backup and start over. >>
> --
>
> Bob Buckland ?:-)
> MS Office System Products MVP
>
> *Courtesy is not expensive and can pay big dividends*
>
>

On 3ÔÂ14ÈÕ, ÏÂÎç9ʱ54·Ö, "DPM" <d...@junk.com> wrote:
> Some additional information:
>
> I originally had the problem when I was working in a networked folder: I
> tried to save the file and got a permission error. So I copied the file to
> a local folder, opened it and did some editing. When I tried to save, same
> problem. This time, though, after Word wrote rescue.asd, I tried to save
> the file with another name. No problem.
>
> So, I'm coming to the conclusion that the permission error occurs when Word
> tries to rename or delete the old file. I can say that after the failure
> the original file is gone, so it clearly deleted the original file.
>
> This has happened 3 times now with one specific file; I've not seen it
> happen with any others. This file contains a lot of graphics - could this
> be the problem?
> --
> Regards,
> Dean

I think the word file may be corrupted. And maybe you can try a can
try a utility called Advanced Word Repair to repair your Word
document. It works rather well for my corrupt Word documents. Its web
address is http://www.datanumen.com/awr/

Alan