Can't open a document saved as a text file

I recently saved a document as a text file because I wanted to send it to some Windows users. Now, a few days latter when I try to open the document it is in code/ASCII thereby unreadalbe. I had one of the people I sent it to send it back to me, which he did with a .doc extension. I cannot open it either. I don't have Word. Is there anyway I can open this document. And . . what am I doing wrong so I don't do this again.
Also if this topic has already been address please excuse me. My search didn't bring up anything. Thanks.

Welcome to Apple Discussions
You shouldn't have a problem opening a text file, but there are a couple of things that could be causing a problem. First, make sure the AppleWorks 6 application is in the AppleWorks 6 folder in Applications and that the folder also contains the AppleWorks Essentials folder. In the AppleWorks Essentials folder is a folder named Translators. I the application & the translators are not in the same AppleWorks 6 folder, they won't be able to "make a connection." This may also let you open a .doc file, but I can't guarantee it as Microsoft has made significant changes in the last couple of years causing AppleWorks' .doc translator to fail.
Also, try adding .txt to end of the file name. This will let OS X identify the file as text &, if nothing else, will allow TextEdit to open it.

Similar Messages

How can I create a Document object from a text file (myFile.txt)

Hi everybody:
Thank you for reading this message.
I am trying to find a method to convert a text file ( I have it in a File object) to a Document object.
I read the Java API but it is strange, I do not know if I have to create an AbstractDocument, it is really strange for me.
Any comment is welcome,
Regards,
JB

Document is an interface, and AbstractDocument is abstract, so you
can't create either of those directly. Assuming you are dealing with a
a plain text file, you could do something like
// Not catching any exceptions that get thrown
File file = /* file you already have */
String eol = System.getProperty( "line.separator" );
int eolLen = eol.length();
FileReader reader = new FileReader( file );
BufferedReader buffer = new BufferedReader( reader );
PlainDocument doc = new PlainDocument();
for ( String line = buffer.readLine() ; line != null ; line = buffer.readLine() ) {
    int len = doc.getLength();
    if ( len > 0 ) {
        doc.insertString( len, eol, null );
        len += eolLen;
    doc.insertString( len, line, null );
}and now you have a document.
: jay

Pages 5.0 can't open iCloud documents. Has anybody run into this issue?

Here's the story:
I upgraded to Pages 5.0 and can't open .pages documents saved in icloud.
It does not seem to be a file incompatibility. I am creating files in Pages for Mac, saving them to iCloud. They are immediately unable to re-open.
I only get a message saying: The file “{file name}.pages” couldn’t be opened.
Documents can be created without issue. If they are saved to my local drive, I can open them again.
Obviously, this makes it very difficult to use Pages with any other devices because document syncing is impossible.
Details on my system:
Mid-2010 13" Macbook pro
2.4 Ghz core 2 duo
8 GB ram
OS X 10.9

I was also experiencing same issues without being to open Older Pages Docs from iCloud in Pages 5. I followed suneson Recommendation and process to the T... Works perfectly.
Important to note you do have to do the second part in order for it to work completely. I tested just the first half and still had issues. Once Disabling and Re-enabling Documents and Clearing Cache - works perfectly now. Thanks Suneson!
Suneson process:
Move all of your iCloud documents to a local folder (offline).
Go to the iCloud preference pane i System Preferences.
Click Manage... and delete all Pages data.
The Next Step is required:
Go back to iCloud preferences and uncheck "Documents & Data".
Check it again.
Delete ~/Library/Caches/--anything related to Pages or iWork--

Can't open a document I created an hour before with Pages 5.0.1; get message saying my Pages is too old, for me to download 5.0.1

Can't open a document I created an hour before with Pages 5.0.1; get message saying my Pages is too old, for me to download 5.0.1

You have 2 versions of Pages on your Mac.
Pages 5 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Anything that is saved to iCloud is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Note: Apple has removed over 90 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
Peter

Can't open numbers documents, says index.xml file is missing?

can't open numbers documents, says index.xml file is missing

I came across this problem after upgrading to Mavericks. Here's what I did to solve the problem:
Issue: I began working on an existing spreadsheet. After I saved it and tried to pull it up again later, I got the message "index.xml file is missing...".
Go to your dock and delete the icon for Numbers (mine still referred to the previous version of Numbers).
Go to Applications and drag the Numbers icon to the dock. This icon now links to the new version of Numbers and (hopefully) your spreadsheet should work.

When i submit a document the receiving parties can't open the document. How do i change the document to a word (.doc)?

When i submit a document the receiving parties can't open the document. How do I change my document to WORD (.doc)????

wolfpack22 wrote:
When i submit a document the receiving parties can't open the document. How do I change my document to WORD (.doc)????
How are you creating the document? In your word processing app save the document as a Word doument then send this saved document.

How can I attach a document saved in my iCloud to a web based outlook email on my IPad?

How can I attach a document saved in my iCloud to a web based outlook email on my IPad?

Thanks Nik and Roger. I think we've all come to the same realization: the new Pages will not attach documents to e-mail without going through Cloud. If you don't want to give your files to Apple to keep in its Cloud (which I assume the NSA has access to through a back door), then you can't use the new Pages.
If, like me, you downloaded the new Pages and used it to work on a document, before realizing you couldn't attach it to e-mail, then when you saved that document it was saved in the new Pages. If you later delete the new Pages (as I did) and go back to using an older version (which you can find in your iWorks file on your hard drive), then you discover that the older version of Pages won't open a document that you worked on and saved with the new Pages.
Nik and Roger have found the solution, if you keep the new Pages. If you delete the new Pages (as I did) then I had to accept the loss of any work I did on my documents using the new Pages, and began over using the latest version of my document that I had saved with the older Pages.
All in all, this has really soured my tase for Apple. If I hadn't recently bought a new MacBook Pro, I'd be switching to a PC now. I refuse to let Apple bully me into using their Cloud.

Can't open a document I was writing yesterday-alert says I need a newer version of pages, but I only updated it in August

Can't open a document I was writing yesterday- alert says it needs a new version of pages, but I only updated it in August 2014. Help please!

You have two versions of Pages on your Mac.
Pages v5.2.2 in /Applications
Pages ’09 v4 in /Applications/iWork ’09
When you open a Pages ’09 document in the default Pages v5.2.2, it is converted to the latter exclusive, new document format, and is not directly backwards compatible with Pages ’09. You would have to use Export To > Pages ’09 in Pages v5.2.2.
If Pages ’09 is running, with/without an open window — double-clicking a Pages v5.2.2 formatted document, or attempting to open said document with the Pages ’09 document chooser, will generate the dialog you saw. It really means you cannot open this newer document format with your older version of Pages. There is nothing to download, because the cause of this dialog is simply having Pages v5.2.2 installed.
You can open actual Pages ’09 documents:
Right-click, Open with > Pages (4.3)
Via Pages ’09 document chooser
Drag/drop Pages ’09 document on the Pages ’09 Dock icon
Pages ’09 File > Open…
Pages ’09 File > Open Recent >

Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

Hello
I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
The error message I get for WORD, PDF and Excel files is:
The ULS logs on the WFE give me this:
WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
01/08/2014 11:01:58.01*   w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             afk59   Monitorable
WOPI                             agxqc   Medium     WOPI Signature verification
attempt failed with public key 01/08/2014
11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqc   Medium     WOPI
Signature verification attempt failed with public key
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqb   Medium     WOPI
Signature verification attempt failed - no public key   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ahdzz   Monitorable   WOPI
Proof: All WOPI Signature verification attempts failed   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ag7pj   Unexpected   WOPI
(CheckFile) - Invalid Proof Signature for file Letterhead Template.docx url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
The ULS Logs on my Office Web Apps server gives me this:
Error message from host: Verifying signature failed, host correlation:    d197d187-ef9d-42f6-ae4f-c4b8199c1078
WOPICheckFile,WACSERVER FileNotFound
WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
Any idea what may have caused this issue all of a sudden?
Thank you.
Yoshi

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word"

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word".I am sure that document is not corrupted and
all. something it showing the preview and sometimes it throwing this error. I hope this error is intermident. When clicking on the link also it throws this error but on refreshing it working fine. I dont know why it is happening. Please helpme to resolve
this issue.

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

Can't open secured documents on windows 7 domain client with mandatory profiles.

While opening certain PDF files we have the problem that the user is presented with a message that he does not have the rights permissions. This happens twice, after that the users gets an empty page with the message the Adobe version might not be up to date. We use Acrobat Pro 10, but this also happens while using Reader 11.0.8. On our windows 2008 terminal services machine this could be fixed by giving the user rights on c:\ to create and remove a file. :O. On windows 7 this doesn't work probably because of UAC. But we've tried every solution to that available on the internet, disabling uac, changing uac options, changing rights on userprofile folders, changing rights on c:\ but to no avail. When using process explorer we can see it wants to create a temp file p328hkl.tmp or something like that on C but it can't and immediattely after is shows the error on screen.
Anyone who also has this problem or solved it? There are no problems with simple self made pdf files/scans but only with certain types of pdf files for which it tries to create a tmp file.
Thanks,
Peter

Hi Brogers,
Thanks for your reaction. We do have AppData redirection in place. We redirect AppData to a share on our data server which works perfectly fine for all other applications. The weird thing is that Reader/Acrobat try to write to C:\ which to my knowledge should not happen, is this maybe a fallback because it can’t write to a different location? Users have full control on their own roaming AppData but not on their local AppData that is made by windows itself while copying the mandatory default profile to C:\.
I might use the wrong term while saying secured documents. I’m talking about a document created by Raet/Youforce a web application for personal administration. The documents can be opened by other viewers than Acrobat/Reader but then only contain the background and not the text. In Acrobat/Reader they do open normally when Acrobat/Reader can create the .tmp file. Otherwise it will not display the file at all. I would attach such a document to see but since it contains certain info I am not allowed to do so.
I hope we can work out a solution for this.
Met vriendelijke groet,
Peter Gerritsen
Engineer
AndoBurg BV
Voorstraat 31
3931 HB Woudenberg
T 033 479 40 80
F 033 479 40 89
E [email protected]<mailto:[email protected]>
I www.andoburg.com<http://www.andoburg.com/>
Als u niet de geadresseerde van dit bericht bent, verzoeken wij u ons hiervan op de hoogte te brengen en het bericht te verwijderen. AndoBurg BV aanvaardt geen aansprakelijkheid voor schade die voortvloeit uit elektronische verzending van informatie. Aan de inhoud van deze e-mail en eventuele bijlagen kunnen geen rechten worden ontleend, tenzij schriftelijk anders is overeengekomen.
Van: brogers_1
Verzonden: vrijdag 19 september 2014 20:10
Aan: Peter Gerritsen
Onderwerp: Can't open secured documents on windows 7 domain client with mandatory profiles.
Can't open secured documents on windows 7 domain client with mandatory profiles.
created by brogers_1<https://forums.adobe.com/people/brogers_1> in Enterprise Deployment (Acrobat and Reader) - View the full discussion<https://forums.adobe.com/message/6745441#6745441>

I upgraded to Mavericks. I just spent an hour in Pages. Now I can't open my documents, it says I need to upgrade to a newer version. It looks like the new 5.0 when I typed but it's saying I'm running 4.3. the App store says I've already upgraded. Hel

I upgraded to Mavericks. I just spent an hour in Pages. Now I can't open my documents, it says I need to upgrade to a newer version. It looks like the new 5.0 when I typed but it's saying I'm running 4.3. the App store says I've already upgraded. HelP

Actually, there seems to be a bit of a bug. Encountered this with a couple of files my wife made. The files were set to "open with" the new Keynote, but clicking the file brought up this error. Right-clicking and selecting "open with..." worked correctly. I can only assume the OS was attempting to open the file with Keynote '09 despite the file property setting.
Probably requires a Launch Services DB reset (although I haven't actually tried it on my wife's MBA yet...since she's still "working on stuff". So I can't confirm if it will solve the problem).
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -r -domain local -domain system -domain user ; killall Dock

Can't open webi documents

Hi,
We can't open webi documents on BO XI 3.0. We have the following error message :
com.businessobjects.wp.om.OMReportElementContainer
(Error: INF)
But we can open deski documents through infoview.
Any ideas ?

We are seeing this error now and it has happened again after restarting the SIA and Tomcat. We will try rebooting whole server tonight.
SAP KB 1326991 suggests:
Cause
The CMSClusterMembers entry in the registry is not updated.
Resolution
WARNING ***********
The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall the Microsoft Windows operating system.
Use the Registry Editor at your own risk. It is strongly recommended that you make a backup copy of the registry files before you edit the registry. For information on how to edit the registry key, view the 'Changing Keys And Values' online Help topic in the Registry Editor (Regedit.exe).
Make sure that the CMSClusterMembers entry is updated in the registry. Or you can edit it manually.
The CMSClusterMembers entry can be modified from HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Enterprise\CMSClusterMembers.
Restart Server Intelligence Agent (SIA).
Has anyone tried this - what is meant by 'updating' the registry entry? Updating to what?
thanks
Keith
XI 3.1 SP2

I have been working on a document in Pages 4.3 and now it tells me I can not open the document unless I upgrade to Pages 5.2. When I look up Pages 5.2 the App store says "installed" nor can I find a "purchase" or "install" button.

My OS is 10.9.3.I've been working on a document in Pages 4.3. Now is says I can not open the document unless I upgrade to Pages 5.2. The Pages 5.2 page in the App store says "installed" nor can I find a "purchase" or "install" button. How do I get Pages 5.2?

If you have already updated to Pages 5.2 on your Mac, you may be trying to open the file with a previous version of Pages. If this is the case, you have two versions of Pages on your Mac & are trying to open Pages 5 documents with Pages 4. Are you launching Pages from an icon in your Dock? Installing the update does not change the Dock icons & it does not remove the older versions. Go to your Applications folder & launch the new Pages from there then right-click on the Dock icon & select Options > Keep in Dock.
Installing new versions of iWork has never replaced existing versions. This is nothing new. The only thing new is that the '09 apps are moved to an iWork '09 folder if they were purchased from the Mac App Store. If they were installed from disk they should already be in a separate folder in Applications.

Down loaded new version of Pages. Now can't open a document and get message I need a newer version of Pages to open. How can I get it to open

I download the new Update for Pages (5.2.2)on September 8th. Now I can't open a document I created in 2012. I get message "You need a newer version of Pages to open this document" What can I do to get this doc to open

First, open Finder, go to Applications folder and delete iWork '06. Then, open Pages and it will use the most recent version

Can't open a document saved as a text file

Similar Messages

Maybe you are looking for