Unsupported file formats for Adobe Pro 8

I am trying to convert a group of files ranging from .xsl to .doc types.  Adobe is saying these are not supported.  I see .dwg, .txt, .jpeg, etc. but no .doc or .xls format.  I know adobe should support these document types as I have seen it on other computers.  Is there a way to update the supported document types?
I am going into the folder with the desired folders and want to click on "combine files to single pdf" but this option is not there.  This should be possible as I have seen it on coworkers computers today.  I have word 2003 and am able to convert .doc and .xls files through the respective programs, but if I have a large number of files this way is tedious. The main point is that .doc files and .xls files are not supported by adobe in this case when I know they should be.
Running windows.

Can you use PDF Maker to create the files from these applications. The option you are requesting uses PDF Maker in each of the applications as I understand it and if PDF Maker does not work, converting the files from Acrobat will not work. At least this is what I would be checking.
As an alternative, you can probably drag all of the documents to the Adobe PDF printer to create the PDF files.

Similar Messages

  • File format for Adobe Central Pro Server

    Is it possible to use a PDF instead of a MDF in Central Pro? What about XDP files?

    Sanket,
    Adobe Content Server adds Digital Rights Management (DRM) to PDFs to turn them into eBooks. Your questions seem to deal with a different product.

  • HT200179 aperture 3.4.5 does not support rx100m2.  I got a message "unsupport File Format" for each of the RAW file that I imported.  I have tried to repair permission, remove Aperture Plist from Preferences, create a new aperture library

    I have updated Aperture with RAW camera update 4.0.7.

    Wow, you got yourself a great camera!
    The list of supported raw formats is here:
    http://www.apple.com/aperture/specs/raw.html
    I see DSC-RX100***   on that list, but not yet rx100 Mark 2; I am afraid you will have to wait a bit for the raw support.
    You may want want to shoot raw+jpeg, while you are waiting, and work with the jpegs for the time being. You can import the raw later, when the raw support will be available, or use the software that came with the camera, while you are waiting.
    Regards
    Léonie

  • Ld: file was built for unsupported file format...for architecture armv7

    hi:
    I recently developed a project with custom ANE and I get this error msg when compile ipa since I upgraded the sdk from 3.5 to 3.8.
    ANE compile CMD:
    adt -package -storetype pkcs12 -keystore ane.p12 -storepass 1234 -target ane yund.ane extension.xml -swc yunding.swc -platform iPhone-ARM -platformoptions platform.xml IDS.framework library.swf libIslandIDSANE.a
    platform.xml:
    <platform xmlns="http://ns.adobe.com/air/extension/3.5">
         <sdkVersion>6.1</sdkVersion>
         <linkerOptions>
                        <option>-w</option>
            <option>-ios_version_min 4.2</option>
                        <option>-framework Foundation</option>
                        <option>-framework StoreKit</option>
                        <option>-framework AdSupport</option>
                        <option>-framework QuartzCore</option>
                        <option>-framework UIKit</option>
                        <option>-framework CoreGraphics</option>
                        <option>-framework SystemConfiguration</option>
                        <option>-framework Foundation</option>
                        <option>-lz</option>
         </linkerOptions>
                 <packagedDependencies>
                        <packagedDependency>IDS.framework</packagedDependency>
              </packagedDependencies>
    </platform>
    msg:
    ld: file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): C:\Users\timoo\AppData\Local\Temp\139d9782-79fd-422a-8c15-da1da2da8c53/IDS.framework/IDS for architecture armv7
    Compilation failed while executing : ld64
    help me
    thx

    Have you Found the way to solve this problem yet?
    I  have got the same problem. Here is the error log when building the IPA:
    ld: warning: ignoring file /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack, file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack
    ld: warning: CPU_SUBTYPE_ARM_ALL subtype is deprecated: /Users/apple/Documents/flexsdk/flex3.9/lib/aot/lib/libDebugger1.arm-air.a(avmplusDebugger .cpp.o)
    Undefined symbols for architecture armv7:
      "_OBJC_CLASS_$_Partytrack", referenced from:
          objc-class-ref in libcom.haibin.extension.PromotionAPI.a(partyTrackAPI.o)
    ld: symbol(s) not found for architecture armv7
    Compilation failed while executing : ld64
    My platformoption.xml content is：
    <platform xmlns="http://ns.adobe.com/air/extension/3.8">
        <sdkVersion>7.0</sdkVersion>
        <linkerOptions>
            <option>-ios_version_min 4.3</option>
            <option>-framework CoreData</option>
            <option>-framework UIKit</option>
            <option>-framework Foundation</option>
            <option>-framework Security</option>
            <option>-weak_framework AdSupport</option>
        </linkerOptions>
        <packagedDependencies>
            <packagedDependency>Partytrack.framework</packagedDependency>
        </packagedDependencies>
    </platform>
    And my build command are:
    <target name="package" description="Create the extension package">
    <exec executable="${FLEX_HOME}/bin/adt" failonerror="true" dir="${basedir}">
    <env key="AIR_SDK_HOME" value="${FLEX_HOME}"/>
    <arg value="-package"/>
    <arg line="-storetype pkcs12"/>
    <arg line="-keystore testkey.p12"/>
    <arg line="-storepass 123456"/>
    <arg line="-target ane"/>
    <arg value="../${ANE_NAME}.ane"/>
    <arg value="extension.xml"/>
    <arg line="-swc ../swc/${ANE_NAME}.swc"/>
    <arg line="-platform iPhone-ARM -platformoptions platform.xml -C ../iPhone-ARM/ . "/>
    <arg line="-platform Android-ARM -C ../Android-ARM/ ."/>
    <arg line="-platform default -C ../default/ ."/>
    </exec>
    </target>
    File "Partytrack.framework " is in the directory "iPhone-ARM"

  • My raw files go to unsupported file format when I load them in. Sony RX 100 had for one year. Never happened before.

    my raw files go to unsupported file format when I load them in. Sony RX 100 camera shooting RAW had for one year. Never happened before.
    Can only load the files in by running them trhough Adobe Camera RAW first and loading them as TIFFS into Aperture. JPEGs form the Sony load into Aperture just fine. Have repaired datebase, permissions ect but no change. Aperture 3.4.5 on a Power Mac. Whats up? Anyone know?

    You mention that 'most' of your files are DNG. Try
    running the effected files through Adobe DNG
    converter again and then import your reprocessed
    files to Aperture and see if the problem persists.
    I had a problem with a batch of D2x files converted
    to DNG which had been metadata tagged by
    PhotoMechanic (the evil app).
    B.T.W. You mention that you had been using Bridge.
    Are you getting any of the embedded XMP metadata
    coming into Aperture during the import process?
    Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
    I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
    Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

  • Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

    Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

    haben
    From looking at the specifications of your camera (SJCam 4000), we know already what video compression your camera is using. It is H.264.
    A H.264.mov file should be supported by Premiere Elements 11. On what computer operating system is your Premiere Elements 11 running?
    Do you have the latest version of QuickTime installed on your computer? And, are you running QuickTime and Premiere Elements 11 from a
    User Account with administrative privileges? Please go to Premiere Elements 11 Publish+Share/Computer/QuickTime to confirm that you find
    presets there for the QuickTime choice there.
    What are the properties of these H.264.mov files - is it 1080p30 (1920 x 1080p30)  or something else? Do you know if this camera is recording with a variable or
    a constant frame rate?
    Please review and consider and then we will decide what next.
    Thank you.
    ATR

  • Mavericks, Aperture upgrade; the message is: unsupported file format. This for my "normal" NEF

    When I try to edit my NEF File with an external editor eg. NikSoftware, Aperture show me this msg: Unsupported file format
    the editor doesn't start; in aperture i can't see the preview of that file.
    I tried to restart, but s.times ok others no.
    why?
    tks
    Alberto

    Have you two tried with the latest Nik Software update? You might need to update preview or reprocess the image after upgrade.
    See: https://support.google.com/nikcollection/answer/4400822?hl=en&ref_topic=3001406

  • Fed up with "Unsupported File format" crashes!

    I really like Aperture - but, I am totally fed up with only being able to edit a few photos before I get the dreaded red/brown screen and the message of 'Unsupported file format' This cannot be the case as they are all .tifs and I have just edited several OK. My whole day is now one of 'stop/start' and either quit or sometimes 'Force quit'. Then Aperture works fine for another short series of edits - before the same problem recurs. It wastes a lot of valuable editing time - and completely spoils the otherwise pleasurable experience of using Aperture!
    I have made a lot of scans from original slides via a Nikon Coolscan 5000 - using Silverfast I have converted these from 48 bit to 24 bit. However, the file size is still large at 100MB - to get the best from the slides. I then import these .tifs into Aperture 2.1. I am using a MacBook Pro, 2.4 Ghz Intel Core 2 Duo with 4 MB RAM. I have an external 24 inch monitor. The .tif files are on an external firewire hard drive - 500 GB LaCie. My Aperture library is in my pictures folder on my MacBook Pro.
    Can someone PLEASE explain how and why I can make a series of edits fine in Aperture and then suddenly I get the red/brown screen and this unsupported file format message?
    Is it a memory problem? Given that I need to edit such large files is it a problem for my (powerful) MacBook Pro? Or, is it a more general problem with Aperure 2.1?
    Any advice - or solutions - PLEASE

    It's a bug in Aperture 2.x with large files and/or large pixel dimensions on images (not clear which). I have submitted a bug report, as should anyone who is seeing this. You'll find quite a few threads on this if you search back. The error message is frustratingly incorrect: there is nothing whatsoever unsupported or wrong with the file format, it just leads you down some dead ends in trying to find a solution while you figure that out.
    I could sometimes not even work on one image before it would do this. I went from 6GB to 10GB in my Mac Pro, and now I can pretty reliably work on two images before having to restart. So that to me smells like a memory leak or memory mismanagement of some sort is at the root of this, but who knows. We're all just waiting for each next release, hoping Apple has finally found and fixed this, because as you know they don't spend a lot of time discussing what bugs they're addressing; they just show up fixed eventually (one hopes!)
    If anyone chimes in here to tell you it's your fault for working with such large images, just ignore them. There were releases of 1.5 that handled these images just fine, as Aperture should. It broke with 2.x.
    Duncan

  • CFZIP problems - Unsupported File Format

    [I tried researching this via Google, but the terms are so generic I didn't find any relevant hits]
    I am working with files that originate via incoming emails as attachments.  In CF I detach them from the emails and hand them off to other jobs for processing. Sometimes they are zipped files, and I have been using CFZIP to extract the actual data file and process it.
    I started getting new files from a client and they are zipped (.ZIP file type), and if I open them from Outlook WinZip opens them just fine.  If I open them in Notepad, they all start with "PK" which I have always believed to mean that they were zip (PKZIP) format, as opposed to other flavors such as GZip.  But when the CF script tries to open that same file with CFZIP, it throws an Unsupported File Format error.
    Any thoughts of diagnosing this error, to determine if it really is a valid ZIP format file?  Are there any utilities out there that would give me info on exactly what program/algorithm was used for the compression process? 
    In the past when I've had these problems it was because the file was .GZ (Gzip format) and not .ZIP, and in those cases even Winzip indicated as much when it opened the file.  But this is perplexing because Winzip seems to think the file is just fine, and CF doesn't.
    Thanks for any ideas!
    -reed

    Winzip supports some functionality that doesn't work with other zip programs, if I recall correctly. Perhaps these zip files use that functionality.
    Dave Watts, CTO, Fig Leaf Software
    http://www.figleaf.com/
    http://training.figleaf.com/
    Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
    GSA Schedule, and provides the highest caliber vendor-authorized
    instruction at our training centers, online, or onsite.
    Read this before you post:
    http://forums.adobe.com/thread/607238

  • Firefox for Mac preferences shows .qif file format for quicken as "quicktime image format"-wrong application and won't let me select anything else

    Post to Firefox forum; Oct.2011
    Re: Quicken 2007; Mac OS 10.5
    Problem: can’t import or download Qif format files into quicken from bofa or Chase. Mac can’t recognize; how do I set preferences in Firefox (or Safari).
    https://support.mozilla.com/en-US/questions/new?product=desktop&category=d1&search=Firefox+for+Mac+preferences+shows+.qif+file+format+for+quicken+as+%22quicktime+image+format%22-wrong+application+and+won%27t+let+me+select+anything+else&showform=1
    Hello,
    I previously used Firefox on my old Mac G4 with OS 10.3.9; the above issue existed with that system and Firefox 2.00.2 (or similar). I then "tried" to move to a G5 Mac with OS 10.5, hoping that an updated Mac Operating system and updating Firefox would solve that problem.
    I'm now working on my son's MacBook Pro, OS 10.5.8, 2.4 ghz Intel Core 2 Duo; 2gb Memory; 2 gb 667 Mhz DDR2 SDRAM.
    I still have a problem in Firefox Preferences trying to download .qif files. BofA Mortgage accounts only allow downloading of .qif files. My .qfx download works fine, but the error message is as follows:
    The error message is that this is a corrupted file or one that Preview doesn't recognize.
    and it is still a problem when trying to download Quicken .qif format files for our B of A mortgage.
    The preferences for Firefox under File Helpers won't let me name the extension I want; instead, it CONFUSES .qif (Quicken Interchange Format) with .qtif (Quicktime Image Format) for Mac.
    Therefore, when I download .qif files and try to import them to Quicken, I get a message that this is a corrupted file:
    thanks for any help.
    Val in Seattle

    Well, in the end, I just gave up and deleted the photos, in the hope that it was something to do with them. Took some more photos and they seem to have imported without any problems at all.
    Given that the same irksome photos loaded on the wife's macbook without so much as a murmur, how weird is that?
    Still- all's well that ends well. Thanks for the suggestions- much appreciated.
    Matt

  • Line Drawing best file format for import in InDesign

    i was wondering what is  the accepted and recommended file format for files to be imported in InDesign. I was under the impression that AI files should be saved as EPS but I just read an article that says that Adobe's Dov  Isaacs said that eps will be shortly obsolete.What should I do. I work on curriculum that contains both photographs and line drawing and we use tiff for the former and eps for the latter. Most of our line drawing is done in AI. Howeverwe have a cartoonist that sends us files in jpg format. What would be the best file format for him and for us as we draw in AI?
    Article link: http://www.prepressure.com/library/file-formats/eps
    The future of the EPS file format
    EPS is rapidly becoming an outdated file format which is being  replaced by PDF just like PostScript itself is also being phased out and  replaced by PDF. Don’t just take my word on this. Here is what Dov  Isaacs from Adobe said in a discussion on a PrintPlanet forum about the  future of PostScript: “ …Adobe will continue to support EPS as a  legacy graphics format for import of non-color managed, opaque graphical  data into Adobe applications (such as InDesign and Illustrator).  Although we certain do not recommend that new graphical content be  stored in EPS format (except to satisfy the need to import data into  page layout programs that aren’t quite PDF-centric — no need to mention  names here!), our user base should feel comfortable that there is no  need to worry about a need to convert their very sizable libraries of  EPS-based graphic assets.”

    Yes, I drag the AI file in.
    If after it's in place I need to change I can just right click and chose edit original make the changes and save and the illustration in inDesign will reflect the changes.
    On the other hand I can make changes to the original and all iterations of the file will automatically update, say if I used the illustration in several documents.
    As an example I had completed a set of documents for a new company, i.e., biz cards, brochures, product labeling, stationery, etc. and in their wisdom they decided to make changes in their logo, which, of course, is on everything. I opened the AI file with the logo made the changes saved and all the documents then reflected the changes. The only caveat to do this seamlessly is to make sure that your file logo size is the same as the original or you might have to tweak placement in the other documents
    It is this interoperability that to me makes the Creative Suite so much more than the sum of their parts.
    Craig

  • The workbook that you selected cannot be opened. The workbook may be in an unsupported file format, or it may be corrupt.

    Hello folk,
    I am trying to create pivot tables from an SSAS cube, in excel (Windows Authentication being used) and publishing the same to a document library in sharepoint. I am publishing only 'Pivot1'(the default name of the pivot table you create) using the Excel Services options. Similar excel sheets (containing pivot tables) are getting published to the same document library in sharepoint  - the only difference being that the data is not being imported from anywhere.  The error :
    The workbook that you selected cannot be opened.
    The workbook may be in an unsupported file format, or it may be
    corrupt.
    Would you like to try and
    open this file in Excel?   which opens perfectly when opened back in Excel.
    P.S. :
    The event viewer also shows a file missing event logged by sharepoint i.e. - Console Configuration File Error: File Not Found: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
    Any idea?
    -Khyati

    iqbalkmk and vijaynats:
    Do NOT propose your own posts as answers.
    The function is there so that *other people* can propose good posts as answers - not for you to propose your own posts.
    (Moderator)
     iqbalkmk:
    Your post was in any case not an answer. Also Project Server 2010 is NOT even close to be covered in these forums. There are separate forums for SP 2010 questions but Project Server 2010 questions go in any case to the Project Server forums.
    SP 2010 "FAQ" (mainly useful links):
    http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters

  • File Format for Fortran-95

    Hi
    I have installed Xcode command line tools and gfortran package from HPC website.
    Now, I can't figure what format should I use for input files to compiler.
    When I used rtf and txt following error occured.......
    ld: warning: ignoring file u.txt, file was built for unsupported file format ( 0x47 0x50 0x41 0x20 0x2d 0x2d 0x2d 0x20 0x31 0x30 0x a 0x47 0x52 0x45 0x20 0x2d ) which is not the architecture being linked (x86_64): u.txt
    Undefined symbols for architecture x86_64:
      "_main", referenced from:
         implicit entry/start for main executable
    ld: symbol(s) not found for architecture x86_64
    collect2: error: ld returned 1 exit status
    PLease Help....
    Thanks
    Gurpreet

    The source files must be plain text, with an extension of f90. It definitely must not be rich text, and the txt extension is unacceptable. Or the extension might be .f, .F, .F90, or others, depending on the contents of the file. Generally f90 will work. See the gfortran manual, available through a link at the HPC site.

  • Is there a spread sheet template for Adobe pro

    is there a spread sheet template for Adobe Pro. I am trying to import a pdf but it will only take have the document and turn it into a spread sheet form in Numbers. with an xlms ending.
    so i thought what if i make my own spread sheet with input for the?
    any answeres on making the print pdf version an electronic one like a fill in form pdf or a excel/numbers file etc.
    BMPhotography

    Are you using Adobe FormsCentral? If yes, please send me your PDF file that you try to import and I'd like to see what happens. My email address is [email protected] If you are using Adobe Acrobat, please submit your issue to http://forums.adobe.com/community/acrobat. Acrobat engineers will help you out there.
    Thanks,
    Wenlan

  • Does anyone know why Aperture gives me a message "unsupported File Format" when I try to import D4s RAW files?

    I just got a Nikon D4s, and I use Aperture 3 ( v 3.5.1) as my primary workflow program. I am getting a message that I am trying to import a "unsupported file format".
    Does anyone know if its just me, or does Apple have a fix to this problem?

    Have you updated to the most recent Digital Camera RAW Compatibility Update 5.05? If not, run Software Update.
    http://support.apple.com/kb/ht5955
    What are your settings for the RAW format in your camera?  The footnote for the RAW support for Nikon D4s reads:
    †Nikon RAW L format only.
    Maybe, you need to change your RAW format settings.

Maybe you are looking for