X
Tap here to go to the mobile version of the site.

Support Forum

Problem opening attachments of Word documents with spaces in the filename

Posted

Since the upgrade to 68.3, my wife can no longer open attachments of Word documents (docx) whose filename contains blank spaces (e.g. File name.docx). The error message popups indicate that Word is trying to open a different document with each word in the filename. So, in the above case it tries to open a document named File.docx, fails, and the another document named name.docx and also fails. Oddly, this is limited to Word files. Similarly named PDFs and PowerPoint files work fine.

The temporary files created when I attempt to open the offending attachments are saved with the proper folder. I can find them in the Tools->Saved Files, and the full file names appear. Attempting to open them through Thunderbird results in the same error. However, selecting the Open Containing Folder, and then double-clicking them from there (taking Thunderbird out of the loop) works as it should.

I've tried safe mode, but that did not fix the problem. She can forward the email to me, and I can open it on my laptop.....using version 68.3. If I replace the spaces with underscores and ship the file back to her, it opens without incident. The settings on our installations are the same, both using Windows 10, both with Word 2016.

I've tried repairing the folder (Inbox), compacting, and even deleting the msf file so it could be rebuilt, but the problem persists.

In scanning the database, I found an old problem that is similar: content-disposition filename cut (truncated) at space. That problem was resolved 16 years ago. As best as I can tell, that problem involved saving the file, whereas in this case the temporary files are being saved correctly, but Word is being told to open a file with only the portion of the name until the space, and then additional files between the spaces.

I tried reinstalling 68.3, but got the same results. I rolled her back to 68.2.2 and restoring a profile from the day before the upgrade, and everything works as it should.

There is nothing peculiar about her configuration. The only thing not by default is her email data (not the profile) is stored in a separate partition on her SSD, a D partition devoted to data storage only.

Disabling the internet security did not help. Since the email data was unchanged in the restore process, the problem does not lie in the data file.

Any suggestions?

Configuration details are available, if needed.

Since the upgrade to 68.3, my wife can no longer open attachments of Word documents (docx) whose filename contains blank spaces (e.g. File name.docx). The error message popups indicate that Word is trying to open a different document with each word in the filename. So, in the above case it tries to open a document named File.docx, fails, and the another document named name.docx and also fails. Oddly, this is limited to Word files. Similarly named PDFs and PowerPoint files work fine. The temporary files created when I attempt to open the offending attachments are saved with the proper folder. I can find them in the Tools->Saved Files, and the full file names appear. Attempting to open them through Thunderbird results in the same error. However, selecting the Open Containing Folder, and then double-clicking them from there (taking Thunderbird out of the loop) works as it should. I've tried safe mode, but that did not fix the problem. She can forward the email to me, and I can open it on my laptop.....using version 68.3. If I replace the spaces with underscores and ship the file back to her, it opens without incident. The settings on our installations are the same, both using Windows 10, both with Word 2016. I've tried repairing the folder (Inbox), compacting, and even deleting the msf file so it could be rebuilt, but the problem persists. In scanning the database, I found an old problem that is similar: content-disposition filename cut (truncated) at space. That problem was resolved 16 years ago. As best as I can tell, that problem involved saving the file, whereas in this case the temporary files are being saved correctly, but Word is being told to open a file with only the portion of the name until the space, and then additional files between the spaces. I tried reinstalling 68.3, but got the same results. I rolled her back to 68.2.2 and restoring a profile from the day before the upgrade, and everything works as it should. There is nothing peculiar about her configuration. The only thing not by default is her email data (not the profile) is stored in a separate partition on her SSD, a D partition devoted to data storage only. Disabling the internet security did not help. Since the email data was unchanged in the restore process, the problem does not lie in the data file. Any suggestions? Configuration details are available, if needed.

Chosen solution

Upgraded the offending system to 68.4.1 and the problem has been resolved.

Read this answer in context 2
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

More Information

Question owner

BTW, the temporary files created are saved with the correct name. My original write up indicated they were saved in the correct folder, which is also true.

BTW, the temporary files created are saved with the correct name. My original write up indicated they were saved in the correct folder, which is also true.
Was this helpful to you?
Quote
sfhowes
  • Top 10 Contributor
1897 solutions 9485 answers

I can't explain your result, but I can supply some additional evidence.

The first picture shows the window that appears when I open a docx attachment with a space in the name; this was sent to myself from TB. Note that the Open with suggests the default app, one that opens docx files. Clicking OK opens the file with no error. But if I click the drop-down, then Other..., and select the same app, it appears in the box without (default), the 2nd picture. This time, clicking OK produces the error in the 3rd picture, referring to a file with the part of the name before the space.

Note that in the first picture, the 'Do this automatically...' box is greyed out, due to the file being sent by TB with incorrect encoding. If the same file is sent by, e.g. Hotmail, the file is correctly encoded and the box is clickable (4th picture). However, this has no effect on the error with opening the file with the 'non-default' default app.

I can't explain your result, but I can supply some additional evidence. The first picture shows the window that appears when I open a docx attachment with a space in the name; this was sent to myself from TB. Note that the Open with suggests the default app, one that opens docx files. Clicking OK opens the file with no error. But if I click the drop-down, then Other..., and select the same app, it appears in the box without (default), the 2nd picture. This time, clicking OK produces the error in the 3rd picture, referring to a file with the part of the name before the space. Note that in the first picture, the 'Do this automatically...' box is greyed out, due to the file being sent by TB with incorrect encoding. If the same file is sent by, e.g. Hotmail, the file is correctly encoded and the box is clickable (4th picture). However, this has no effect on the error with opening the file with the 'non-default' default app.
Was this helpful to you? 1
Quote
Wayne Mery
  • Top 25 Contributor
  • Moderator
602 solutions 5774 answers

the space is a known issue which is close to being resolved and expected to be fixed in 68.3.1

the space is a known issue which is close to being resolved and expected to be fixed in 68.3.1
Was this helpful to you? 1
Quote

Question owner

Thanks to you both. I'll check on it before I upgrade her system to 68.3.1. Any idea why it works correctly on the system I am using right now? That is the piece that had me scratching my head and not just dismissing it as something that would be fixed in a release or two.

Thanks to you both. I'll check on it before I upgrade her system to 68.3.1. Any idea why it works correctly on the system I am using right now? That is the piece that had me scratching my head and not just dismissing it as something that would be fixed in a release or two.
Was this helpful to you?
Quote
sfhowes
  • Top 10 Contributor
1897 solutions 9485 answers

Helpful Reply

Here is the bug report:

https://bugzilla.mozilla.org/show_bug.cgi?id=1601905

Maybe it depends on whether the helper app is the system default or not, even if the helper (e.g. Launch Windows App) is the same as the default.

Here is the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1601905 Maybe it depends on whether the helper app is the system default or not, even if the helper (e.g. Launch Windows App) is the same as the default.
Was this helpful to you? 2
Quote
Stolenchild 0 solutions 2 answers

MrBunter said

Thanks to you both. I'll check on it before I upgrade her system to 68.3.1. Any idea why it works correctly on the system I am using right now? That is the piece that had me scratching my head and not just dismissing it as something that would be fixed in a release or two.

I have this problem only since I updated to 68.3.1

''MrBunter [[#answer-1272302|said]]'' <blockquote> Thanks to you both. I'll check on it before I upgrade her system to 68.3.1. Any idea why it works correctly on the system I am using right now? That is the piece that had me scratching my head and not just dismissing it as something that would be fixed in a release or two. </blockquote> I have this problem only since I updated to 68.3.1
Was this helpful to you?
Quote
Stolenchild 0 solutions 2 answers

Wayne Mery said

the space is a known issue which is close to being resolved and expected to be fixed in 68.3.1

I have this problem only since I updated to 68.3.1

''Wayne Mery [[#answer-1272289|said]]'' <blockquote> the space is a known issue which is close to being resolved and expected to be fixed in 68.3.1 </blockquote> I have this problem only since I updated to 68.3.1
Was this helpful to you?
Quote
David White 0 solutions 1 answers

I still have the problem with 68.3.1.

I still have the problem with 68.3.1.
Was this helpful to you?
Quote
sfhowes
  • Top 10 Contributor
1897 solutions 9485 answers

The bug report doesn't indicate the problem has yet been fixed, and there's no mention in the 68.3.1 release notes.

The bug report doesn't indicate the problem has yet been fixed, and there's no mention in the 68.3.1 release notes.
Was this helpful to you?
Quote
julien3 0 solutions 1 answers

Very strange, in my case : OK for this filename : 1920 RANDO Galette des Rois (2).docx NOK for this filename : 1920 RANDO Galette des Rois (2).pdf

Version 63.8.1

Very strange, in my case : OK for this filename : 1920 RANDO Galette des Rois (2).docx NOK for this filename : 1920 RANDO Galette des Rois (2).pdf Version 63.8.1
Was this helpful to you?
Quote
t.powell929 0 solutions 1 answers

I have the same problem with spaces only for .pdf files.

If I select forward for the email, I can open the pdf from the Compose message window only.

If anyone knows what version has solved this, that would be great. I have 68.3.1 as well

I have the same problem with spaces only for .pdf files. If I select forward for the email, I can open the pdf from the Compose message window only. If anyone knows what version has solved this, that would be great. I have 68.3.1 as well
Was this helpful to you?
Quote
Susanh 0 solutions 2 answers

I also have this problem on a new Win 10 PC using 68.3.1. The problem only exists with .doc or .docx files, which I open normally with LibreOffice Writer. I can open .pdfs and any spreadsheet or image files without issue.

I first had the same results as the original post, with error messages for each word in the file and only one file being created in the temp directory. I'm not sure what changed but after a shutdown overnight, the next day I started to get a command window with LibreOffice help open up when I try to open a Writer file but the file is still created in the temp folder. I can right-click and save the file without issue, this is my current workaround.

I also have this problem on a new Win 10 PC using 68.3.1. The problem only exists with .doc or .docx files, which I open normally with LibreOffice Writer. I can open .pdfs and any spreadsheet or image files without issue. I first had the same results as the original post, with error messages for each word in the file and only one file being created in the temp directory. I'm not sure what changed but after a shutdown overnight, the next day I started to get a command window with LibreOffice help open up when I try to open a Writer file but the file is still created in the temp folder. I can right-click and save the file without issue, this is my current workaround.

Modified by Susanh

Was this helpful to you? 1
Quote
Keith 0 solutions 1 answers

I also have this problem and using 68.3.1. A temporary work-around is to save Word files as Word 97-2003 documents

I also have this problem and using 68.3.1. A temporary work-around is to save Word files as Word 97-2003 documents
Was this helpful to you?
Quote
Jeremy G 0 solutions 1 answers

Hello, I also have this problem, and when I received a document with space in the name, my pdf reader try to load each words of the name like a new file.

Hello, I also have this problem, and when I received a document with space in the name, my pdf reader try to load each words of the name like a new file.
Was this helpful to you?
Quote
loyall 1 solutions 16 answers

After this latest TB upgrade to 68.3.1, attachments are not working properly. When I create a new message and wish to add an attachment, I click the attach link in the upper right corner and navigate to my scanned documents folder. There I select the scanned document that I wish to attach, and it appears in my message in the attachments box with the correct .jpg file ending. Then when I click the attachment to make sure that I have the correct one, the Firefox browser opens, even though it is not my default browser, (yes, I checked) with the message "file not found" and multiple other Firefox tabs that have nothing to do with me. Even so, the attachment appears in-line under the text of the message. So Thunderbird cannot open my own attachment even though I can open it directly from its folder into my default .jpg app which is Microsoft Photos. In my years of using TB, I have never had a problem with attachments before. Can this possibly be related to the issues reported above in this thread?

After this latest TB upgrade to 68.3.1, attachments are not working properly. When I create a new message and wish to add an attachment, I click the attach link in the upper right corner and navigate to my scanned documents folder. There I select the scanned document that I wish to attach, and it appears in my message in the attachments box with the correct .jpg file ending. Then when I click the attachment to make sure that I have the correct one, the Firefox browser opens, even though it is not my default browser, (yes, I checked) with the message "file not found" and multiple other Firefox tabs that have nothing to do with me. Even so, the attachment appears in-line under the text of the message. So Thunderbird cannot open my own attachment even though I can open it directly from its folder into my default .jpg app which is Microsoft Photos. In my years of using TB, I have never had a problem with attachments before. Can this possibly be related to the issues reported above in this thread?

Modified by loyall

Was this helpful to you?
Quote
john93 0 solutions 5 answers

Running 68.3.1 32bit in Windows 7 Pro. Cannot open attachments with spaces in file name. My default pdf reader "fails to open" phantom files whose names are bits of the attached file's actual name, broken at the spaces.

Please fix this.

Running 68.3.1 32bit in Windows 7 Pro. Cannot open attachments with spaces in file name. My default pdf reader "fails to open" phantom files whose names are bits of the attached file's actual name, broken at the spaces. Please fix this.
Was this helpful to you?
Quote
sfhowes
  • Top 10 Contributor
1897 solutions 9485 answers

The fix is expected to be in the next release, 68.4:

https://bugzilla.mozilla.org/show_bug.cgi?id=1601905#c51

The fix is expected to be in the next release, 68.4: https://bugzilla.mozilla.org/show_bug.cgi?id=1601905#c51
Was this helpful to you? 1
Quote
john93 0 solutions 5 answers

Thank you, sfhowes! Anxious to see it!

Thank you, sfhowes! Anxious to see it!
Was this helpful to you?
Quote
loyall 1 solutions 16 answers

sfhowes, Do you think my problem, that I described above, will also be fixed in release 68.4? Or do you think my problem is different?

sfhowes, Do you think my problem, that I described above, will also be fixed in release 68.4? Or do you think my problem is different?
Was this helpful to you?
Quote
sfhowes
  • Top 10 Contributor
1897 solutions 9485 answers

loyall said

sfhowes, Do you think my problem, that I described above, will also be fixed in release 68.4? Or do you think my problem is different?

I think the bug affects attachments in received or composed messages, so it's likely your issue will be fixed as well.

''loyall [[#answer-1278647|said]]'' <blockquote> sfhowes, Do you think my problem, that I described above, will also be fixed in release 68.4? Or do you think my problem is different? </blockquote> I think the bug affects attachments in received or composed messages, so it's likely your issue will be fixed as well.
Was this helpful to you? 1
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.