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

Similar Messages

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

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"

Unsupported File Format (nokia lumia 520)

My Nokia Lumia 520 will not post pictures to social networks, transfer them to my computer, set them as my lock screen or even edit them. I purchased the phone only a couple of months ago and it was working perfectly, but then it would just come up with 'Unsupported File Format' when i tried to do anything with them. I did a full system reset, but the problem remained and I don't know what to do. I still have warranty on it and don't know wether swapping it would do any good. Please help!

Hi cjford,
Welcome to Nokia Support Discussions!
Are you still having the same issue? If so, have you tried the suggestion given by nj15? Did you reset it by going to Settings > About > Reset your phone? Are all the pictures taken from your phone's camera or came from other sources?
Keep us posted.

Unsupported file format

Hi
In CS4 i saved one file after some time i try to open the same file that file is not opening, can any one please tell what is the problem and how to open the file.i tried to open in different version also but it is not opening it is showing error messaage as Unsupported file format.

Hi
http://www.mediafire.com/?7ob473p7mcbua4z
Please check the file i have attached here

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.

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.

Unsupported file format - not solved by restart!

Hello,
I recently installed aperture, and have been organizing and editing photos on my new imac 2.66 4 GB for over a day. I had encountered a few 'unsupported file format' errors, but suddenly I cant open any thing. Quitting and rebooting have no effect. Does anyone have any ideas? Will I have to re-install and reload my photos?
Help!
Eric

I’ve just started having the "Unsupported File Format" error on select other photos too, where the thumbnails looks OK but the photo won't load and you get the dark reddish frame instead. This problem does not go away when you restart Aperture.
Does anybody know if the photo has been corrupted at some point? The thumbnails look good in all three browser modes.
BTW, I also just started having the exact same black photo problem on a particular photo, and only when in the browser film strip mode. It looked fine in the other modes. Eventually, it stopped displaying as black and looked OK. I think it was after I restarted Aperture.
So far, I’ve only noticed these problems with my Nikon D300 photos, but others seemed to have had problems with older cameras too.
I'm using a 20" G5 iMac with my Aperture2 library on external FW drives.

Error while opening pdf in reader in windows 8:Can't open this file. There's a problem with file format

I have a problem with a pdf file which does not open with reader in windows 8 but it opens properly with adobe pdf reader. All other pdf can be opened in reader.But when i open a pdf(see this link for pdf for which i got error http://incometaxsoft.com/temp/Form.pdf)
it gives error as "Can't open this file. There's a problem with file format".
The same file opens properly in adobe pdf reader.You can check the pdf file which i have mentioned in the link above.But the reader which comes with windows 8 can open some other pdf in the same PC.What may be the error causing this??

This has turned out to be an enormous issue for me as I sell PDF files as ebooks. I have done a fair amount of investigating this for my system.
My files have to be compatible not just across readers but across operating systems.
To date, I have over 200 PDFs that have functioned flawlessly across Mac, PC (Windows 7 and below), Android, iPhone/iPad, Linux.
I personally test my PDFs using a variety of readers and PDF editors including
PDF XChange (my favorite)
Foxit (runner up for me and I recommend for most people)
Adobe (the bloated monster)
Nitro 9 (great for moving graphical elements around)
ABBYY
And the Nuance PDF Create toolsets
Those are off the top of my head. There are a bunch on Android that I test with too.
I am running the Windows 10 Pro Tech Preview and I have this same problem so I know it isn't fixed yet in any kind of pre-release way (-sigh-)
Here is what I've learned for my situation
The PDFs I created using NUANCE'S PDF CREATE PROFESSIONAL VERSION 8
all fail using the built-in Windows 8/10 PDF reader.
When I look at the PDF properties for these Nuance created files, the underlying engine used to write them is called "ImageToPDF". Using ABBYY it indicates their own engine as does everyone else that I've tried. It is easy for you to check to see
what created your PDF by doing a "Control D" (look at the document properties). Perhaps there's a common engine causing issues.
If I use the exact same source files to create a PDF using any of my other tools I have no issues. I checked the PDF versions made by the tools and they are all set to 1.5.
A customer mentioned being able to convert them in a way they worked by saving them without having to do any kind of extraction, but I have not been able to duplicate that. Perhaps he did a "print" which seems like it could work.
In summary, the workaround everyone is talking about, using an alternate reader, of course works. But not everyone wants to change.
The culprit I have found is my Nuance PDF Creation tools that are using the ImageToPDF engine.
I hope it gets FIXED as I really don't want to have to regenerate all of my PDF files.

Export Datatable to Excel 2010 format and Save in SharePoint Document library ,and whn opening file getting error "WorkBook may be in unsupported file format "

im converting stringwriter objec to Memory stream and saving this as .xlsx uploading file in library ,but when i try to open the file im getting error as below
WorkBook may be in unsupported file format
and when trying to open in excel getting message as
Excel cannot open file because file extention or file format is not valid .verify thet the file has not been corrupted and file extensions match file format

May be you can use this approach:
http://www.c-sharpcorner.com/UploadFile/pandeypradip/export-data-into-excel-in-a-pre-defined-template-using-strea/

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

Yosemite and Canon RAWs - Random "Unsupported File Format"

It all started with Yosemite betas, random raw files in Aperture would pop up with the dreaded "Unsupported File Format" graphic. I tried a lot of stuff, rebuild the library, delete prefs, etc. Nothing work. I tried exporting the raws and neither iPhoto or Preview would open them. Downloaded the LightRoom 5 trial and it opens the files fine. OK, tried Aperture on a laptop with Mavericks, the files open fine there too. So it looks like it is something in the way that MacOS is handling
Any ideas? Now with the final release of Yosemite and Aperture 3.6 trying to open one of these file just crashes the software. I can't really say I like LightRoom but if I have to move on, I guess I will.

What version of iPhoto is it?
The issue is that the OS provides RAW support, but the applications need to leverage it. Aperture 1.5.6 is old: Aperture 2.0 came out in March of 2008 so there hasn't been an update to Aperture 1.5 since 2007-ish. It is unlikely that any cameras that shipped since then will ever be supported in Aperture 1.5.x.
The improvements/advantages to going with Aperture 3.1 over 1.5 are huge (assuming you have a capable machine) and well worth it.

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

Unsupported file format message w/media converter

I am using final cut express ver 2.0.3,with a canopus media converter.When using capture now function,I now get a message saying I am using an unsupported file format. This had always been working until recently.I have quicktime ver.7.1.3.Does anyone know how to solve this?

I am using canopus advc110.I see no video in the capture screen.I have only recently upgraded to this quicktime vers.7.1.3.Does this older vers.of final cut express not support this new quicktime? Thanks for your time.

YouTube app problem: Same file formats, cannot view some videos

This is weird. I uploaded several videos to YouTube with the same file format (.mkv) that YouTube supports.
I have two Playlists. Only the videos in one of those Playlists are playable on my touch. But the videos in the other Playlist are not supported by the touch:
Video Unavailable
This video does not currently support iPod.
Now why, if 100% of my videos are of the same format and uploaded exactly the same way, do only the videos in one of my Playlists are viewable on my touch and the others are not?
I am viewing the videos from My Videos folder instead of the Playlists folder but it doesn't matter.
Frustrating, to be sure.

I have to make a correction that makes this even more frustrating.
I found a few videos in that Playlist that I said can play on my touch that CANNOT be viewed on my touch! Some of the playable videos are marked private and others are marked unlisted but that doesn't seem to be part of the problem.
So this problem seems to be totally random. A few videos can be viewed on my touch, the others cannot.
HELP!

CFZIP problems - Unsupported File Format

Similar Messages

Maybe you are looking for