Can't open a document made by another using IDcc in my IDcs6 software

I use a marketing service that creates brochures, etc. using InDesign CC (v.10).  When I try to open them using InDesign CS6 I get an error message telling me to use CC to save the document in IDML.  Since I don't have CC software, is there another way for me to get access to the IDML version?  Is it up to the marketing company to do something so I can open the brochure.  They seem to say I have to open it in IDML and I can't find any way to do this?  Am I missing something obvious?

Thanks. While taking your suggestion, I realized what happened to me yesterday. InDesign is always defaulting the save file type to indd so when I opened the idml, made changes and saved, it saved an indd which I can't open any more than the ones the consultant originally sent. I guess I'm just out a day's work there. It's also a pain that every time I want to save my updated idml, I will have to change the extension.
Can you explain the difference between working with an idml and an indd? The former is much smaller. Is it pulling in all of the graphics from my Links folder each time it opens while the indd has them all saved as part of the document? Will I lose anything by just maintaining these as idml's? Since I just downloaded the latest version from Creative Cloud as a trial last week, I'm puzzled as to why I can't open the indd's.
I appreciate your help.

Similar Messages

  • 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 Office documents from share on Windows 8

    We have a problem with a customer that they can't open Office documents(Word,Excel etc.) on Windows 8.1 image on a network share. The error message is just that the document can't open.
    The documents are on a sharepoint site and we can open the documents within the site and also we can open the Office documents on a Windows 7 image from the networkshares.
    Also can't open the documents if i copy them to the local desktop.
    I think there is a group policy for Windows 8 for this but I don't know for sure?
    Anybody?

    Hi,
    As I understand, the issue is that customers can’t open office documents on windows 8.1 on a network share or copying them to the local desktop.
    Per my test, I can open documents on windows 8.1 on a network share.
    1. By default, Word doesn't trust files in temp directories from your browser. You can add the
    network address and local address to the trusted list. From Word 2010/2013: Click File > Word Options > Trust Center->trust center setting->add new location.
    2. You can create a shortcut on the desktop using the network address and then open the documents by that way.
    3. To narrow down the research scope that you can create a new document library->Download a problematic file (an Excel workbook or a word document) to your local->Upload the local file to the new document library->do the same option to check if
    the same situation will occur.
    There is a similar case:
    http://superuser.com/questions/693871/word-2013-wont-open-files-downloaded-trust-center
    Best regards
    Sara Fan
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected].
    Hi Sara Fan,
    Thanks for your reply.
    I have added the profile to the trusted locations but without success. Also a shortcut is not working. I still can't open any Office document on that location(Error message: location ***.xxxx can't be opened). The problem occurs on every client.
    1. Opening Office documents under local administrator account, domain admin account is working fine
    2. Re-image the machine is not a solution
    4. All locations use the same Windows 8.1 image through SCCM
    3. When the user logon to another location(site) it's working fine and they can open Office documents so it seems site-specific
    4. The problem is specific from 2 sharepoint shares. We can open office documents from other shares.
    5. Can't open Office documents from the library on the sharepoint site(browser), but on another location it's working fine.
    Problem only occurs on Windows 8.1 image with domain users. Other locations of this company do not have the problem. Note, every location have their own OU for users/clients.
    Any other suggestions? 

  • Word Web App (2013) can't open this document ... Because the service is busy

    I have just set up Office Web Apps Server in a SharePoint 2013 test environment as per document here:
    http://technet.microsoft.com/en-us/library/ff431687.aspx
    Although I had some issues with Excel Web App at first, I've solved this and excel seems to work ok, However, the Word Web App just sits there spinning and ultimately give the error dialog:
    "Sorry, Word Web App can't open this document because the service is busy. Please try again later"   The Same link as above has a simple solution :
     Did you install Office Web Apps Server on a domain controller? Office Web Apps Server cannot run on a domain controller. Office Web Apps Server must be installed on a separate server that is part of a domain. For more information, see
    Software, hardware, and configuration requirements for Office Web Apps Server.
    I certainly did not install on a DC - its a standalone server.
    ULS Logs are growing by 2K per second even when I am not doing anything on the server.
    VERY FRUSTRATED!

    So after further research we have found the following:
    Un-bind and unindstall Web Application Server
    Clean Server
    Reinstall (by Mistake to the C: Drive)
    Bind and Provision
    WOW it works!
    Un-bind, deprovision, Uninstall, Web Application Server
    clean Server
    Re-install to the D: Drive
    Provision and Bind
    wow - it DOES NOT work
    Again - repeat the first scenario
    and once again IT WORKS
    SO Why doesn't it work on the D Drive - We've checked IIS Setting and Permission - there don't seem to be any differences.
    SO - Why isn't this working when changing the default installation location, is it just me?   Has anyone gotten this working installing to another drive?
    Thanks
    James Moore

  • Can't open Adobe documents on iPad 3

    Can't open Adobe documents on iPad 3 with Adobe app

    Here is web site where I had the problem.
    http://hosted.rightprospectus.com/IvyFunds/Fund.aspx?dt=AR&cu=8911&ss=IF
    Since then I received another such email with a pdf extension and it worked!
    I got this reply from Adobe on my problem with the above link.
    "Thanks John,
    I looked at your screenshots, and it appears that the issue you are seeing is that the website you are trying to get the documents from is not compatible with the iPad. Unfortunately, many websites have still not yet updated to work with the new mobile systems, but since tablet sales are increasing rapidly, and should overtake laptops in the next 3 years, that will change.
    The website seems to be using an HTML feature called “Object Embedding” which only works on desktop computers. The website seems to also be presenting a dialog to the user letting them know that to view the embedded PDF they need to install Adobe Reader, and forwards the user to our standard Adobe Reader download page.
    The net is that I don’t know how to make this work for you, unless you can find a way to make that website give you a link to just download the PDF directly.
    Dennis Griffin
    Adobe"
    Sent from my iPad

  • HELP!!! Can't open any documents from documents to go

    Helo anyone can help me...
    i can't open any documents (word, excel, jpeg etc)from documents to go it says: "there is no application to open this document"
    what should i do....i've just deleted the documents to go from my Handheld cause i got frustated already...
    so....what should i do now...?
    please help me...
    Message Edited by fachrul on 07-15-2008 11:47 AM
    Message Edited by fachrul on 07-15-2008 11:48 AM

    I am trying to open a pdf file through documents to go on my Centro (verizon). I received a this message: An unexpected error occured! Error number: 0x7371803. 
    What does this mean?
    I saw on another thread there is a palm pdf software that works. I went to the site; it said this program is not compatitable with Centro. Has anyone else found a workaround or another program?
    Hi, and welcome to the Palm Community Forums.
    The error could be caused by the particular file you are trying to open, the way it was created, etc.  Have you tried opening other .pdf documents? 
    Post relates to: Centro (AT&T)
    smkranz
    I am a volunteer, and not an HP employee.
    Palm OS ∙ webOS ∙ Android

  • How can I open a project made in 2000 on Final Cut Pro to migrate it to a new version?

    how can I open a project made in late 2000 on Final Cut Pro to migrate it to a new version to finish editing it? files, timeline and unfinished edit are all stored on hard drive since early 2001, with all the original miniDV tapes still in hand

    Do you still have legacy FCP? If you not you need to find someone who will open the project in FCP6.0.6 or later. Export an XML file of the project. Use 7toX to convert it to an XML format that works with FCPX. Import the converted XML file to FCP.

  • Can't open 1 document created using travel journal template

    Since installing Snow Leopard yesterday I found out I can't open this one file I created using the travel journal template. All other Pages '09 files are fine. I just get this error message telling me Pages had to close my document "unexpectedly".
    *"Pages quit unexpectedly while using the SFWordProcessing plug-in"*
    Don't see why it would need to use this plug-in. And I don't recall choosing this plug-in. There must be a way around this. To open this file by turning off that plug-in perhaps. Unless it's absolutely necessary when using the templates. Or the "travel journal" template.

    http://discussions.apple.com/thread.jspa?threadID=2141021&tstart=15

  • 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 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 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

  • Can I open psd file made in photoshop cs3 with photoshop ps2?

    Can I open psd file made in photoshop cs3 with photoshop ps2? Thanks in advance!

    Actually you can open a CS3 file with smart filters in CS2
    the only problem is CS2 will not understand the Smart filter and flatten it.
    If you leave the smart filtered object alone in CS2 save the file and it should still be a smart filtered object in CS3

Maybe you are looking for