Re: The document name or path is not vaild...

You know - the more I look into this the more it seems like a huge problem
with Word.

Try this search in Google groups...with enough examples of lost documents
after transferring through e-mail, or burned onto CD.

http://groups-beta.google.com/groups?hl=en&lr=&safe=off&num=100&q=%22document+name+or+path+is+not+valid%22&qt_s=Search+Groups&safe=off

as said - it seems to be a header corruption issue and the "file name not
valid" is a catch-all for "hey there, this document is corrupted".

Interestingly in our case - when we asked the supplier to Zip and resend the
file (see below), the Zip file was corrupt.

For our client in the UK (using W2002) - they received the same error from a
file saved on my machine (which has every conceviable update) - and sent to
them through FTP. I tried saving in every Word version (from my machine).
The only thing that worked was of course RTF. It seems that Word 2003 is
very persnickety with its header.

Regards,
Shane




"Jerry Pacemaker" <nospamspam-sfclarke@xxxxxxxxxx> wrote in message
news:%23RgugOZNFHA.1308@xxxxxxxxxxxxxxxxxxxxxxx
> Hello Mike,
>
> Unfortunately I have no solution, just emotional support. We are getting
> this more frequently, with a client in the UK who cannot open our
> documents, and with a supplier in NYC whose documents we cannot open.
>
> I am trying to troubleshoot with no success - there seems to be no useful
> information expect that this involves corrupt headers - I will let you
> know if we find out anything. I found this mail looking for a solution.
>
> I have Word 2002 with SP3 also.
>
> Shane
>
> "MikePL" <mpleedham@xxxxxxxxx> wrote in message
> news:33e9836a.0503290329.6fcd9b5f@xxxxxxxxxxxxxxxxxxxxx
>> We are getting more and more documents arriving from our clients via
>> email which we are unable to open and produce the following error
>> message:
>>
>> "The document name or path is not vaild. Try these suggestions.
>> *Check the file permissions for the document or drive.
>> *Use the File Open dialog box to locate the document.
>> (..document name..)"
>>
>> We are using Word 2002 with Service Pack 3 and all subsequent updates.
>> I have switched on the "RepairSmartTags" registry key and tried to
>> open with repair in safe mode as outlined in Q328100 & Q832890. But
>> nothing makes any difference.
>>
>> I have tried saving the file to network drives, local drives and
>> opening direct from the email.
>>
>> We do not have Norton AntiVirus installed (we use McAfee, I have also
>> tried with this uninstalled).
>>
>> Nothing seems to work and this problem is now getting quite serious,
>> we can't always ask our clients to re-send in Rich Text Format!
>>
>> Any advice would be appreciated.
>
>


.

Relevant Pages

  • Re: 4 CONSECUTIVE CORRUPT DISK DISASTERS WITH WIN2K
    ... Disk and drive controller. ... The application install is responsible for placing the shortcuts. ... unreadable / corrupt. ... Restoration of data files from backup hard drives during re-installation ...
    (microsoft.public.win2000.general)
  • Re: Read Only
    ... If your mailer lets you edit headers and remove the In-Reply-To: ... Does the "hdpparm" command work on USB drives? ...
    (RedHat)
  • Re: Correcting corrupt $MFT on shared clustered disk.
    ... Next I am not sure if you are aware but http://support.microsoft.com/kb/903650 Extended Maintenance mode is now available when you need to run chkdsk on a drive. ... We have a two node cluster running Windows 2003 R2 ... The three drives are a 500MB for the quorum, ... directory E:\$Mft is corrupt and unreadable. ...
    (microsoft.public.windows.server.clustering)
  • 4 CONSECUTIVE CORRUPT DISK DISASTERS WITH WIN2K
    ... running Windows 2000 SP4 with latest updates, ... unreadable / corrupt. ... installation CD, thoroughly irrelevant for what I was doing at the time. ... Restoration of data files from backup hard drives during re-installation ...
    (microsoft.public.win2000.general)
  • Re: Frontend backend problem
    ... One thing you can do define a standard location for the backend. ... resides in a folder on the clients server, then mimick that same folder on ... have some partioned drives and I can just place the backend on my E drive ... mimicks my clients setup. ...
    (microsoft.public.access.developers.toolkitode)