Firefox, Thunderbird & SeaMonkeyPost your questions about Mozilla based products (Firefox, Thunderbird & SeaMonkey) here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
While emailing a MS Word 2002 document through Netscape 7.1, the recipient cannot open the document. This is the error:
Word experienced an error trying to open the file. Try these suggestions.
*Check the file permissions for the document or drive.
*Make sure there is sufficient free memory and disk space.
*Open the file with the Text Recovery converter.
Show He lp >> OK
The file permissions are "ok", there's more than a sufficient amount of memory & disk space, AND the Text Recovery converter is not an available option.....?.....
When clicking on the attachment from email, and "save as", I get the same error. Now if the same document is copied to a network share, it will open fine.
Is this a MS Word or Netscape 7.1 error? AND, what can be done to help fix this ongoing error?
Suzette
Didn't find the information you thought to find? Check out these Similar Threads
Suzette - I know nothing about Netscape and think that to be the more appropriate forum, but you might also consider a Repair of Word as a possible solution.
Edit | Preferences | Navigator | Helper Applications
If you have an entry for:
application/msword
Highlight the entry
In the "File Type Details" ensure "Save to disk" isn't selected
Click the EDIT button
Disable "always ask" if it is checked
If you've encountered an attachment with an unknown filetype like application/octet-stream before, then you may also have a helper entry listed for application/octet-stream. If it's set up to save to disk, that's OK and you can leave it alone. Any other action for application/octet-stream is incorrect, and you should select it and remove it from the list.
If none of the above applies, then the problem might be with a corrupt compreg.dat, mimetypes.rdf, or downloads.rdf file. Try deleting or renaming these files one at a time to see if it effects your problem. Ensure that Netscape and Quick Launch are closed when renaming, or deleting.
NOTE: Deleting mimetypes.rdf will clear your Helper Applications, so renaming might be a better choice. Netscape rebuilds a pristine copy of all three files on restart.
If this doesn't help, then you might want to troubleshoot MS Word.
I have to appologize, late Friday afternoon burnout skid....;( I don't think I worded the problem quite clearly enough.
The document is being sent from one individual's pc. In other words, anyone she sends to, the reciepient cannot open the document without the error popping up. If the document is saved on a network share or diskette or cd, it can be opened. Whenever she sends out any MS Word document, through Netscape 7.1 attachment, the reciepient(s) cannot open the document.
I had hoped that this was a Netscape 7.1 bug, only because the document can be opened if delivered/shared some other way.
I think I will try re-installing netscape 7.1. Unfortunately Netscape has made this release so impossible for a simple user to understand and work with....;(
If this reinstalled fails, I will have to follow through with MS Word. I will post back with my results. Hopefully they won't be more complicated. If you have any other suggestions, I would love to hear them before tackling the beast.
This is an older post, but it's got a "happy ending"..... During my never-ending searches for solutions on the internet, (and firstly here, if that's an actualy word) I've found the solution to my users errors.
Her document is fine, and so is the application(s). At the receiving end, saving the document to their temp folder, opening Word, directing themselves to the document and highlighting it, (not opening it yet), clicking on the pull down menu on the open button, and choosing the "open and repair" option helped fix. The application that the document was originally created in was Office 95.
Another happy camper.... Hope this helps others some day!