Pages-created document cannot be opened

I created a few documents within the Pages iOS application. I have created copies of a few of them. Now the orignal and the copies of the document will not open at all in Pages. Nor will the edit function that enables the ability to send the files will work because the application just hangs at the point after selecting which format to export/email - I have tried all three supported export formats. I have tried deleting the app, re-up from cloud and nothing has worked. Is there an update coming if this is a known problem hopefully?!?

You are aware that Pages for Mac and Pages for iPad /iPhone/iPod are 2 different program?
Looks like you have Pages for Apple mobile devices but not for your Mac.
If that's the case
Pages for Mac: https://itunes.apple.com/au/app/pages/id409201541?mt=12
Pages for iPad/iPhone/iPod touch: https://itunes.apple.com/au/app/pages/id361309726?mt=8

Similar Messages

As I like open a file it coms message This document cannot be open because is it too old. First open by Pages 09 What I have to do?? I do not have Page 09 any more.

As I like open a file it coms message
"This document cannot be open because is it too old. First open by Pages 09"
What I have to do?? I do not have Page 09 any more. I've got Pages Vers.5.0.1

I suspect you have created the documnet's in Pages 08 or earlier. Do you have the iWork 08 DVD so you can install it? Then update to from this link Pages 08 3.0.3 Use it for you older documents and use Pages 5 only for new documents.

Pages '09 Document won't open - file missing

Hi all, I recently upgraded to Pages '09, and have created my first document it in, a four page newsletter. I attempted to open it this evening, and am getting an error message that says "Newsletter Name" couldn't be opened, the required index.xml file is missing.
If I attempt to open it in Pages, it doesn't even show up on my recent list. I can see it in my documents, though, and trying to open it there gives me the above message. Is there a way to recover the document, or am I doomed? Obviously, I've now learned to save a copy, but I've never had this happen and have created over 50 documents in Pages '06 and 08.
Oh, and I can do a "quick view" and see the document in small format.
Help!

Amy,
I was having a similiar problem: Message-"The document [ ] cannot be opened. The file is not in the right format. The file might be corrupted, truncated or in a different format that than you expect."
I was able to figure out that for some reason Pages did not set itself as the default program to open Pages documents. Very strange.
Here's what I did: select the icon that represents the document, go to Finder menu and select File - Get Info, in 'Sharing and Permissions' section click on the 'key' icon and type in my password from the keychain, in the 'Open with...' section change the software selection to 'Pages', go to 'Sharing and Permissions' to lock the 'key' icon, close 'Get Info'.
Hope this helps anyone.

I'm getting a "Document Cannot Be Opened" message when trying to open a recent document - any ideas?

When I try to open a recent document in Pages, I get a "Document Cannot Be Opened" message.
Also, it just clocks when I try to create a new doc.

A search of this forum for the message turns up this thread. Does it help?
https://discussions.apple.com/message/15988208#15988208

This document cannot be opened because it is corrupted or damaged.

Hi There
I have recently created a pdf document in "Expert PDF 7" from "Avanquest". I have inserted certain fields which needs to be completed by the reader for example name, surname etc.
On my desktop, using Windows 7 and Adobe Reader X it works perfectly but, when using my iPad 3 and Adobe Reader it stalls. I can enter the first field but, as soon as I move to the next field the following error appears; "This document cannot be opened because it is corrupted or damaged."
Can someone please assist?
Regards,
Marinus

Unfortunately, the file cannot be recovered. Also, it would be difficult to ascertain the reason that led to this issue. There was an issue with the previous versions of Adobe Reader that led to some Acrobat.com documents to be corrupted which is fixed in the latest version. Request you to update Adobe Reader to the latest version(11.7.0) available on the Play Store where you won't encounter the issue again.
Thanks,
Adobe Reader Team

This document cannot be opened as it is not a valid PDF document

I am trying to get my Amex statement from Amex on my tablet. I have Adobe reader for Andriod and Pdf to Go. Each time I download and tray to read the document I get this error. Other Pdf files I have downloaded open OK.

I GOT PROBLEMS TOO...got this error when trying open the pdf files in android devices "The document cannot be opened because it is not a valid PDF document" ..im using samsung s4..i tried open the same files at windows pc and its can be open fine,the files not contain any passwod btw..seem some files cannot be open at android is this normal or what? got solution of tht?or i just search another pdf viewer?
example of files : http://www.mediafire.com/download/raz3x0bk1mvnni4/Lawak+Kampus+01%40ih azaliza.blogspot.com.pdf
this the screenshot

Why does it say my event is already open with the same identifier so the second document cannot be opened?

I have been working for 7 hours today on a major 3-month project. Everything was okay until I closed it and tried to open it. I received this error:
"/Volumes/MediaSAN4/Workbench/HRL /Final Cut Events/Move-In is already open with the same identifier as /Volumes/MediaSAN4/Workbench/HRL /Final Cut Events/Move-In, so the second document cannot be opened.
Move one of these documents out of your Final Cut Events folder. To avoid this problem, copy events from within Final Cut Pro."
not sure what it wants me to do.
When i hit ok EVERY event is gone. all projects say missing event. Even the two I'm not working on. I'm so frustrated I've thought about starting the project over in 7 but I want to stick with it.
I work for a university and have not been able to find help, even from my boss. The only thing I have found to fix it is to dismount the drive (mediasan4) and then remount it and it reconnects everything. But this can't be a good way to work. There are no duplicate events anywhere. there IS for some reason a duplicate mediasan4 drive in the project library, but not under the events library. I have been working in one and everytime I make an edit to my projects in there it makes the changes to the other one. I cannot find a way to delete it. We just reinstalled fcpx a few days ago.
Any and all help is greatly appreciated!

Oh yea sorry about that, but yes sir, I sure am. The SAN not the drive. I have tried renaming the event as well. Thanks for checking though.

Moving pages created documents between macs

I need to move pages created documents from imac to air lap top (running new pages in Mavericks) and to ipad (running ios pages). Get message on Imac (running pages 9) that xml document missing. Moving these documents is important for writing and editing them. I hesitate to upgrade the imac (snow leopard) to the new pages for fear I will lose all my previous documents created in pages 9. Help!

Thank you, I checked the IPad and sure enough I do have version 2.01 and it makes the documents unreadable in Pages 09. It will transport them if they are made into Word documents and then they are read as Page documents in Pages09. Unfortunately if they were not created as word processing documents in the first place, this won't work. Is there a way to back up IOS pages to v.1.71 on my IPad and IPhone? If not, will know that IOS will not work for documents. You would think Apple would have not created this mess since I am surely not the only person writing documents on these devices and needing to move them around for changes and editing!!
Thanks for your help and Peter, your comment about ICloud is also helpful. I have never used it, was tempted, and now will not use that either. Again, Apple getting ahead of themselves and their customers. Love them but get frustrated by them often.:--))

Pages document 'cannot be opened'

I was working on a document in Pages, closed it, then reopened it, to be greeted by this error message:
It hasn't happened with any other documents (yet). I called Apple Support, copied, exported to PDF, erased and installed Pages fresh, only to still have the same problem. What makes this particularly annoying is that this machine is two weeks old and has been doing nothing but word proceesing. Can anyone shed some light on how I might resolve this?

FUBAR, indeed. Make sure you have ver 5.1. Not only are versions 5 and 5.01 incompatible with Pages 09, not only are Pages for icloud and Pages 2.x for ios incompatible with pages 09, but docs created w 5.1 cannot be open with 5.0 or 5.01. Get the latest (5.1) , open the file and export to word or Pages 09. Word, nota bene, cannot open Pages files: nothing can. Pages cannot even open files edited with different versions of itself. It is a mess. Microsoft is rumored to be bringing office to ios. If that happens, pages will be dead.

Mavericks Pages 5 documents won't open

I upgraded to Mavericks a few days ago. I have documents that were created in Pages ’09 that will no longer open. (Some will, and I don’t know what the difference is) When I try to open one, it either opens, no problem, or I get the message “The required index.xml file is missing”. This message is in a rectangle with an icon representative of Pages ’09 (the inkwell). Since it has this icon, I’m assuming that I was trying to open it in the ’09 version, which is what I intended to do. Since this didn’t work, I tried to “open with Pages.app (4.0.5)” and got the same message. I’m a little afraid to try to open it in Pages 5, since I’ve heard rumors that this could ruin the document. I’m at a loss, and, like everybody else, I have important documents that I need access to. After I upgraded I had both Pages ’09 and Pages 5 on my dock, instead of one of them being in the applications folder. I have looked briefly at pages 5 and determined that I prefer ’09. They are both still in my dock but I never open Pages 5. I’m using an iMac with 10.9.4. All my documents are in Pages ’09 and I want to open them in Pages ’09. What to do?

Having two versions of Pages on your Mac is a royal pain. The correct version of Pages '09 for Mavericks is v4.3. Apple has a downloadable update here. I am current with both, including Pages v5.2.2. Your opening errors may be due to that Pages v4.0.5 running on Mavericks and needing a newer v4.3. Run Disk Utility from /Applications/Utilities after updating Pages ’09 per above, and verify/repair your permissions.
I have dragged and dropped Pages '09 from /Applications/iWork '09, and Pages v5.2.2 from /Applications onto my Dock, so the icons are adjacent. You should drag and drop each of your Pages Dock icons out on to your Desktop about two inches and release them to remove them from the Dock. Don't worry, these are aliases to the real applications. Now drag/drop each of the Pages applications back onto the Dock as I have done. You will now know exactly where these icons point back to the individual application locations.
In System Preferences > Security & Privacy (click the gold lock), under Allow apps downloaded from: mine is set to Mac App Store and identified developers. I am wondering if you have FileVault enabled for your boot drive? I have never seen your dialog as posted, so try my settings.
With both applications installed on your Mac, you can only open Pages ’09 documents as follows, and double-click will always open them in Pages v5+.
Launch Pages ’09, and open the document via the application File chooser
Right-click on the ’09 document, and from the Open With sub-menu, select Pages (v4.n)
Drag and drop the ’09 document onto the Pages ’09 Dock icon.
Pages v5.2+ will open a Pages ’09 document without asking if you want too. As Pages v5.2+ is about 110 features/functionality less than Pages ’09 v4.3, it will also silently filter content from your ’09 documents as it opens them. This has been a catastrophe for those without backups.
For forward organizational purposes, I would recommend that you create a custom tag name and color in Finder Preferences for explicit identification of your Pages ’09 documents. You can change this color and tag name in the open document title when you roll over the file name. Then you have both a visual clue to avoid opening these in Pages v5+, and the tag name allows you to use an Finder Window, or Spotlight search on that name to exclusive find Pages ’09 documents. Here is an example of a Finder tag: Pages search:

Pages '08 document cannot be read properly in '09

Hey guys,
I'm currently working on my last major assignment for university, and I've written about 3 quarters of the assignment in Pages '08, however, when I open the document in Pages '09 - even though the settings and preferences are the same - the spacing is completely different throughout the entire document, and as I have lots of images in the document, it's really screwed up my assignment. I'm not happy!
Here's the settings for both Pages '08 & '09:
Character: 0%
Line: 15 pt (at least)
Before paragraph: 0 pt
After paragraph: 5 pt
Being that both Spacing settings are exactly the same, you'd expect the spacing to be the same... right?
That's what's so confusing...
How did Apple manage to screw up such a simple thing?
I wouldn't mind just using '08 for the rest of the assignment, and then switch over to '09 afterwards.. but the fullscreen feature would be massively helpful.
Any ideas/input would be much appreciated,
Thanks!
Andy

I've also noticed this. In '08 an "exact" line spacing of 14 pt would in fact not be exactly 14 pt when using e.g. Times New Roman. The actual line spacing would differ from font to font. In '09 "exactly 14 pt" means the same for all fonts, it seems.
Comparing '08 and '09 side by side I notice that 14 pt of "exact" line spacing looks the same in both versions when using Times, Palatino and most other fonts (indicating that in '08 most fonts behave well), but that the line spacing is larger in '08 when using Times New Roman, Minion Pro and Stone Serif (indicating that these fonts misbehave in '08).
Of course, I found out when I opened an '08 document in '09 and noticed that the line spacing had become substatially smaller, but only with these specific fonts.
It's a nuisance, of course, but it's better to fix this bug in '09 than to keep it there for compatibility with '08. Still, it means that for some of us it's a good idea to keep an installation of '08 even after installing '09. I have some huge manuscripts written in Pages '08, most of them with unproblematic fonts, but some of them will need manual adjustment when eventually converted to '09.

Load report failed - document cannot be opened in the c++ stack

I am now receiving an error when trying to load a report into the report viewer. The error I am recieving is "Load report failed ... Unsupported operation. A document processed by the JRC engine cannot be opened in the C++ stack"
 
Here is the error stack:
 <br/ />
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
 
Exception Text **************
CrystalDecisions.Shared.CrystalReportsException: Load report failed. ---> System.Runtime.InteropServices.COMException (0x80041811): Unsupported Operation. A document processed by the JRC engine cannot be opened in the C++ stack.
 at CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object& DocumentPath, Int32 Options)
 at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath, Int32 Options)
 at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
 --- End of inner exception stack trace ---
 at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
 at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)
 at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)
 at IPAM_Reporting.frmCrystalReport.frmCrystalReport_Load(Object sender, EventArgs e)
 at System.EventHandler.Invoke(Object sender, EventArgs e)
 at System.Windows.Forms.Form.OnLoad(EventArgs e)
 at System.Windows.Forms.Form.OnCreateControl()
 at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
 at System.Windows.Forms.Control.CreateControl()
 at System.Windows.Forms.Control.WmShowWindow(Message& m)
 at System.Windows.Forms.Control.WndProc(Message& m)
 at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
 at System.Windows.Forms.ContainerControl.WndProc(Message& m)
 at System.Windows.Forms.Form.WmShowWindow(Message& m)
 at System.Windows.Forms.Form.WndProc(Message& m)
 at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
 at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
 at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
mscorlib
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5444 (Win7SP1GDR.050727-5400)
 CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
IPAM_Reporting
 Assembly Version: 1.1.0.0
 Win32 Version: 1.0.0.0
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/IPAM_Reporting.exe
System.Windows.Forms
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Infragistics2.Win.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.v10.3.DLL
System.Xml
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Infragistics2.Shared.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Shared.v10.3.DLL
Infragistics2.Win.UltraWinExplorerBar.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.UltraWinExplorerBar.v10.3.DLL
Infragistics2.Win.UltraWinToolbars.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.UltraWinToolbars.v10.3.DLL
Infragistics2.Win.UltraWinDock.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.UltraWinDock.v10.3.DLL
System.Configuration
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
Infragistics2.Win.Misc.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.Misc.v10.3.DLL
Accessibility
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Infragistics2.Win.UltraWinEditors.v10.3
 Assembly Version: 10.3.20103.1000
 Win32 Version: 10.3.20103.1000
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/Infragistics2.Win.UltraWinEditors.v10.3.DLL
SQLDatabaseConnectivity
 Assembly Version: 1.0.0.0
 Win32 Version: 1.0.0.0
 CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/IPAM%20Reporting%20System/SQLDatabaseConnectivity.DLL
System.Data
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
System.Transactions
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
 CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
System.Core
 Assembly Version: 3.5.0.0
 Win32 Version: 3.5.30729.5420 built by: Win7SP1
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
CrystalDecisions.Windows.Forms
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Windows.Forms/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Windows.Forms.dll
CrystalDecisions.Shared
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Shared/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Shared.dll
CrystalDecisions.ReportSource
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportSource/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportSource.dll
log4net
 Assembly Version: 1.2.10.0
 Win32 Version: 1.2.10.0
 CodeBase: file:///C:/Windows/assembly/GAC_32/log4net/1.2.10.0__692fbea5521e1304/log4net.dll
System.Web
 Assembly Version: 2.0.0.0
 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
 CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
CrystalDecisions.CrystalReports.Engine
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.CrystalReports.Engine/13.0.2000.0__692fbea5521e1304/CrystalDecisions.CrystalReports.Engine.dll
CrystalDecisions.ReportAppServer.CommLayer
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.CommLayer/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.CommLayer.dll
CrystalDecisions.ReportAppServer.ClientDoc
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.ClientDoc/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.ClientDoc.dll
CrystalDecisions.ReportAppServer.Controllers
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.Controllers/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.Controllers.dll
CrystalDecisions.ReportAppServer.DataDefModel
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.DataDefModel/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.DataDefModel.dll
CrystalDecisions.ReportAppServer.DataSetConversion
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.DataSetConversion/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.DataSetConversion.dll
CrystalDecisions.ReportAppServer.CubeDefModel
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.CubeDefModel/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.CubeDefModel.dll
CrystalDecisions.ReportAppServer.ReportDefModel
 Assembly Version: 13.0.2000.0
 Win32 Version: 13.0.0.99
 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.ReportDefModel/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.ReportDefModel.dll
JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
 <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
What could be the problem now.
Edited by: mcontri on Apr 15, 2011 6:49 PM
Edited by: mcontri on Apr 15, 2011 6:49 PM
Edited by: mcontri on Apr 15, 2011 6:51 PM

Hi Rama,
Please search, this issue has been discussed many times before.
For starter, see below doc.
Troubleshooting error: "Unsupported Operation. A document processed by the JRC engine cannot be opened in the C++ stack…
Thanks,
Bhushan

Downloaded document cannot be opened in Adobe Digital Editions, error is #2038

I have downloaded a document for Adobe Digital Editions, but it cannot be opened, error is # 2038, what to be done ??

Hi minczel,
The #2038 error indicates that ADE cannot get to Activation server. This generally happens because of either system or application level firewalls disallow access to the Adobe activation site (http://adeactivate.adobe.com/adept/)
Try disabling the firewall and check.
You might also want to refer to the solution mentioned in the thread : Error # 2038
Regards,
Rave

HT5534 I DOWNLOADED SOME UPDATE FOR PAGES, AND NOW MY OLD DOCUMENTS CANNOT BE OPENED UNLESS I BUY THE NEW PAGES APPLICATION. THIS *****, I HAVE WORK TO DO NOW AND AM NOT INTERESTED IN AN UPGRADE.

I downloaded some upgrade for pages, (not the new version for $19.95) now my computer will not open previous pages documents on my desktop without me buying the new version. I am not interested in the new version as I have seen numerous negative comments. I simply want my system to work as it did before Apple pulled this trick to force me into buying the new pages. Any suggestions would be appreciated. I have work to do !

You are aware that Pages for Mac and Pages for iPad /iPhone/iPod are 2 different program?
Looks like you have Pages for Apple mobile devices but not for your Mac.
If that's the case
Pages for Mac: https://itunes.apple.com/au/app/pages/id409201541?mt=12
Pages for iPad/iPhone/iPod touch: https://itunes.apple.com/au/app/pages/id361309726?mt=8

Since OS X Yosemite upgrade, cannot share document from pages in word format. Therefore document cannot be opened by non apple user. How do I get around this please?

Since the OS X Yosemite 10.10.2 update to my iMac (27 inch, Mid 2010) , I can no longer "share" a document from Pages in word format via email. It can be sent as an att but then as "Pages" cannot be accessed by a non apple receiver. Please what is the answer, the old method was fast, simple and efficient.
Out of my depth appreciate some help.

Are you using the File > Export function? It will deposit a Word document onto your desktop (or any folder you choose) and then you can attach it to your email.

Pages-created document cannot be opened

Similar Messages

Maybe you are looking for