End of File Error with Tiff

I saved my Tiff, 87 meg file on a Windows 7 Ultimate Laptop and set the computer to Hibernate. Next time I started up and got a BSD with memory dump. No problem I thought. Just restarted and everything looked fine. When I try to open the file I get "Could not complete your request because an unexpected end-of-file was encountered" Still using Elements 3.0. I know...I know....
Any suggestions? I can see Tiff repair files on the net but have no idea which are legitimate.
Thanks
Julius

Julius,
It might be useful to post to the PS Elements forum, though I have a feeling that the answer will be the same.
First thing that I would do is to try to Open the TIFF in another program, like IrfanView, which is freeware. Personally, I'd also try my ThumbsPlus and PhotoImpact, and anything else that I had around. If it does Open, then do a Save_As with the proper settings, and do NOT let your computer hibernate. I'd even keep screen saver off. Then, try Opening that new file in PSE.
PS/PSE are very sensitive to 100% correctly formed headers, for all file formats. Other programs, not so much. I've had TIFF's and JPEG's, that PS would not touch, but the other programs would, and a simile Save_As got me going.
Depending on a lot of factors with your Save, you might get a useful image, part of an image, or no image.
Also, there are some image recovery utilities. Some might be free. I have one from Stellar-Phoenix, which is anything but free. It has saved my bacon on a few instances, where clients got bad files written to a CD/DVD and then Deleted the source file. BTW - Stellar-Phoenix has some utilities to help with file recovery from a HDD too, plus their individual file recovery utility. I bought two licenses for their entire suite, I liked them so much.
Now, if your TIFF is hosed, you will have lost all of your work, but you should still have the original image, right? You didn't Save OVER an original, did you?
Good luck, and I hope that some other image program will Open the TIFF, so you can do a Save_As. If not, you have done the manipulation once, so should have a good idea of what will need to be done on the redo.
Hunt

Similar Messages

SOLUTION: Dealing with the 'end of file' error

Adobe have not only failed to fix the constant 'end of file' error after 6 versions but also, even worse, failed to make the error in any way useful. If you get this error when building a complex project, you have to completely rebuild your project to find the cause. This is a huge issue when dealing with projects like the one I'm currently doing: 7 different discs (projects), each with about 20 timelines.
A simple 'end of file: NAME OF FILE' in the error message would solve this.
However, luckily (as I would have otherwise killed myself by now), I have found a much quicker way of finding problematic files. This is the Windows solution, but hopefully there's an equivelant Mac way of doing it.
Get Process Monitor from here.
Run it, and hit the Filter button on the toolbar.
Add filters for:
Process Name is Adobe Encore.exe
Operation is ReadFile
Go start your build process
When the 'end of file' message appears, switch over to Process Monitor and scroll down to the bottom
Scroll up until you see the last time a file of yours was accessed
There's your culprit
The actual problem with the file usually seems related to Encore not dealing with externally created files very well. Import a non-DVD/blu-ray ready copy of your video and transcode it internally, that seems to fix it.
Adobe needs to stop work on every new feature or bugfix for Encore, and fix the error messages. Bugs are inevitable, but not having adequate error messages or logging so the bugs can be worked around is unforgiveable. It's a simple matter and should be fixed immediately.

Here is where you tell Adobe about bugs, and also where you ask for new features
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

End of file error using modified version Cont Pattern Input.

Hi. I am using the Cont Pattern Input example, which is modified to write the Data Read to a file on the hard drive. A wire is connected from the Data Read to a "Write to I16 subVI" which is also modified to be a "Write to U8 subVI". It writes problem free to the file specified until the 2.1 GB when it displays a Error 4 "End of File Error". There is ample space on the hard drive. How do we get rid of this error as we would eventually need to write up to 60 GB of data?

Unfortunately, the only thing to do is get a different operating system. I seem to recall that Windows has a fixed limit on file size of about 2G.
Is there any way you can logically break the data you're collecting into smaller logical units? Alternately, you could structure your code to write to one file till it fills and automatically switch to a second, and a third and so on. As long as the routine that you write for working with these huge datasets keeps track of the various pieces of data it could all work as though it were all in one very very very large file.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

End of file error on previously opened Raw files.

I recently had an external hard drive get damaged. Many raw files were able to be recovered but when I go to open ones I had previously manipulated in ACR I get an end of file error. It seems it's only on the previously used photos...is there a way to recover them so I can re-edit them?

You might try IfranView - it's free. It will open corrupt images and you can visually see the extent of the corruption, e.g. 90% of the image might show, with garbage showing at the bottom.
You could then crop the image and use that - losing the corrupt part.
You should also consider using a cloud storage service like dropbox, google drive, box.com, Creative Cloud etc. to backup your images.
I'd try to refrain from working from an external drive.

End of File error on .nef files

I am beginning to see a growing number of my .nef files becoming visually corrupt in the viewer and showing the "end of file" error when opening in PS or any other application.
The corruption does NOT seem to affect the associated .jpg file (if there is one) but I am also NOT able to generate another "clean" .jpg file with the .nef files that have become corrupt.
I hope that I haven't confused everyone - but this issue is rather baffeling in that I can't seem to pinpoint a cause.
My master files are stored as reference files on a server share - all shot with a Nikon D2X.
Does anyone have an idea of what may be causing this - and better yet - is there a way to reverse the corruption?

I do have a number of other systems that I can use to test from. THe file server is a general purpose server in my home running 10.4.x with all of the latest patches, etc.
I am using a SanDisk card reader to ingest directly into Aperture. The corruptness appears to be random.
I am using a Nikon D2X with a number of CF cards, usually 1 or 2GB in size. I capture recording .nef (RAW) images to the CF card.
My workstation is a PowerMac, Dual G5, with 2.5GB processors and 2.5GB of memory. I am using MacOS 10.4.2 with all of the appropriate patches and updates.
The Server is a PowerMac, Dual G5, with 2.5GB processors and 2.5GB of memory. The server is running MacOS 10.4.x Server, again with all of the appropriate patches and software.
The network is Gigabit speed with one switch between my workstation and the server. The Switch is a GSM7224 L2, 24-port 10/100/1000MBps managed switch.
The users in my home (in this case; me) log into any of a number of workstations in my home and authenticate against the server using LDAP. Once authenticated, home directories are available and stored on the server.
This appears to be network related as I can ingest and save locally to the server and open the files without any corruption.

Photoshop CS4 "Cannot save due to an end-of-file error" Help

This problem occurs daily, probably 15-20 times per project. I take on normally 3-4 projects per day, so you can see how annoying this is. Basically when I'm saving, I get a dialogue box that says "Cannot save your file due to an end-of-file error" or something to that extent. I would love to resolve this, this problem is persistent and it's driving me out of my mind I'm saving to a network, if that has any correlation. Thanks in advance
     Chris

This is the boilerplate text often used in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.
See:
http://kb2.adobe.com/cps/406/kb406793.html
Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
     Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work.   It should.
    Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
When problems arise, a lot of valuable work can be lost.

Inconsistent "End of file error" on "open for access "myFile.txt"

I have a script that accesses a txt file containing info needed for values in the script. Sometimes the script works flawless, but once I get the "End of file error," it won't work right anymore unless I log out and log back in or if I dump the file and rewrite it. Below is a copy of the portion of script having the problem:
+set _fileRef to open for access "Library:Preferences:MyTextFile.txt" with permission+
+ set ReadMyTextFile to read _fileRef as string+
+ close access _fileRef+
Is there a way to reset the "End of file" status so that I can access it later with the same script in one login session? I have a feeling that the first time it opens, that it reads to the end of the file and then closes the file. When it opens again the script starts to read where it left off at the end of the file. Does that sound right?
Any help would be great.

OK, it looks like if you are going to use the open for access..close access, you need to keep tack of the EOF yourself, so you can just read to the EOF - for example:
<pre title="this text can be pasted into the Script Editor" style="font-family: Monaco, 'Courier New', Courier, monospace; font-size: 10px; padding: 5px; width: 720px; color: #000000; background-color: #E0E0E0; overflow: auto"> set TheOpenFile to open for access (choose file)
try
set SomeText to paragraphs of (read TheOpenFile to eof as text)
close access TheOpenFile
on error
close access TheOpenFile
end try
choose from list SomeText with prompt "File text:" with empty selection allowed
</pre>
If there isn't any particular reason to explicitly open and close the file, you can use something like:
<pre title="this text can be pasted into the Script Editor" style="font-family: Monaco, 'Courier New', Courier, monospace; font-size: 10px; padding: 5px; width: 720px; color: #000000; background-color: #E0E0E0; overflow: auto"> set SomeText to paragraphs of (read (choose file) as text)
choose from list SomeText with prompt "File text:" with empty selection allowed
</pre>
In the above examples I used paragraphs of in order to use the choose from list, since it displays stuff like this a little bit better - see this article for a tutorial on file read/write in AppleScript.

There was an unexpected end of file error

I am currently using DNG Converter 8.1 and converting NEF files from a Nikon D600.
Occacionally I get an error message on some of the files.
"The was an unexpected end of file error" It only happens on some of the ffiles but I can not figure out what is wrong or how to fix the problem.

plasticAnimal wrote:
my solution to the problem was to re-copy the problem files from the card.
Consider checking your disk drive, or just getting a new one.
If known good (on disk) files go bad, problem is usually disk (or ram).
If files known to be good on card, are bad after transfer, problem is usually with the transfer hardware.
If files bad on card, problem is usually camera or card, but may be reader...
Problem is not likely due to DNG Converter software (nor OS) - sorry Jeff if not worded strongly enough for you.
R

What causes 'Unexpected end-of-file' error?

Hi,
I am a photographer and an avid Lightroom user. I have two camera's (Nikon D700 and D300) and two computers, a desktop PC and a MacbookPro. Lightroom is installed on both computers.
For the last three photoshoots I have had this problem where 1 in 3 to 1 in 5 images in Lightroom on my desktop PC suddenly gives a 'Unexpected end-of-file' error. First I thought it was my camera. But then I loaded the images onto my MacbookPro and they worked fine. Then I took some images with my other camera, loaded them on to my Desktop PC, and, voila, same problem.
The problem specified: the image stops rendering a preview. A dull preview appears. At the top of the screen the message appears: "An unexpected end-of-file occurred." The histogram window stays empty and the image can not be developed.
I have browsed through this forum some looking for the cause and the fix. There are some mentions of it, but they all date back to 2007.
I run LR 2.2 on Windows XP SP2 and on a MacbookPro with OS X, version 10.5.8.
Please help me understand the cause of this problem, and help me find a fix?
Thanks,
Rogier
Rotterdam, The Netherlands
www.rogierbos.com

While the corruption in your .NEF file could come from any one of a number of sources, here is a way to recover at least some of the information if you own Adobe Acrobat. Your .NEF file should contain a smaller JPEG file created by your Nikon camera when the picture was taken. Even if the .NEF file is corrupt, the JPEG may well be intact, and you can tell that's the case if a preview is visible in Lightroom or Bridge.
If you try to print it from Bridge or Lightroom, though, you will get an error. You can get around this by loading up a CODEC that will let you preview the files in Windows Photo Gallery. Nikon has one available for download to use with Vista x32 at http://www.nikonimglib.com/nefcodec/index.html.en, but it doesn't support Vista x64, so if you're running that (as I am) you'll need a second party CODEC such as the one available from http://www.ardfry.com/Products.htm with a 15-day trial download available. They also have a DNG CODEC which I have not tried.
With that CODEC installed and your system rebooted, preview the damaged NEF file in Windows Photo Gallery. Choose the "Print" option and select the "Adobe PDF" printer. Choose the "Postscript Custom Paper Size" option, and set the dpi resolution to the highest available (4000).
Go to the "Options" link on the bottom right of the window and uncheck the "Sharpen For Printing" box, as you can do this yourself with later processing. Then go to the "Printer Properties" link to see the Adobe PDF settings.
Go to the Adobe PDF Settings tab and choose Default Settings: High Quality Print, which will set the resolution to 2400 dpi.
You want to have Acrobat interfere as little as possible with the output, so select "Edit" from the Default Settings tab, which will bring up the "High Quality Print - Adobe PDF Settings" dialog. Here, turn off the "Optimize for fast web view" check box, then go to the "Images" folder and set the "Downsample" setting to Off and the pixels per inch to 2400. Also, set "Compression" to Off.
If you're going to do this in the future, you can also "Save As ..." your settings for future use with a name like "Fix Bad NEF Files."
Print the file to a designated folder. It won't be quite as good as the NEF file would have been, but at least you haven't lost the shot.

Unexpected End of File error in LR 1.3

Using the computer's built-in SD card reader, I imported NEF files taken on my Nikon D80. The previews showed up in the Library window of LR, but when I tried to open the files in Loupe view, I received an "Unexpected End of File" error on most of the images.
Thinking it might be a card issue, I took some test shots using JPG format instead of NEF, and all images imported and opened properly.
I then took some other photos in NEF format, imported them thru the card reader, and none of the new files would open in loupe view. I deleted all the files from the computer and library, and tried the following.
I then hooked the camera directly to the computer's USB port and imported the problem NEF files from the camera (SD card in the camera). Everything worked fine -- all the NEF files opened properly.
Not being a technical type, I don't know if this is a software or hardware issue -- does anybody have a clue?
I have used this card before and have used the card reader to inport RAW files from a different camera (Panasonic LUMIX) with no problem.
I hesitate to use RAW format on my Nikon D80 until I can figure out what the problem is.

I believe the problem is related to Edit > Catalog Settings... > Metadata > EXIF > Write date or time changes into proprietary raw files. If this is selected and you change the capture time on your images then around 1 in 256 photos will become corrupted. The problem is one in 256 files will end with character 26 (or character 1A in Hex). When updating the files Lightroom removes the trailing character 26. First of all turn off this switch. Secondly if you don't have a good original copy you can download and use HEdit to append the trailing character 26 to your file.
I first posted this problem in September 2007 on the forum. It is still an issue in the 3.2 RC. I have reported the bug through adobe labs (correct channel rather than this forum) and they are looking into the problem.
http://forums.adobe.com/message/1399193#1399193

ORA-03113 End-of-file error after xmltype.transform

I tried to use the xmltype.transform to transform xml data extracted from the database with a xslt contained also in the DB. If I did this with a file of 39 KB, everything works well, but when I did it with a 129 KB xslt file, I got an ora-03113 End of file error.
I suppose the error is connected to the size of the file.
Can everybody help me or suggest some ways to solve the problem?
thank you
Francesco Seriani

1)Run a trace on your session.
2)Look at the server to see if an error trace file is getting generated on the database. There may be information in the error log to point toward the underlying problem.

End-of-file errors

I just came back from a month of travels and shot 3k of photographs. About 70% of my images are plagued with 'end-of-file errors'.
Here's some details:
Nikon D700 with 2 X Transcend 16GB compactflash cards.
All images are NEF (Raw).
I made backups on a portable hard drive every night, but checking them reveals the same errors. I presume these errors were caused from when the data was written to the card rather then when the data was pulled from the card.
Lightroom 3 and Photoshop CS3 give me 'end-of-file' errors when I try to work with them.
Nikon's ViewNX 2 software can open the files and even save them out as jpegs, no problem. So as a last resort I'll do this, however it's a lot of extra work, over 2k of pictures to save out as jpegs... ideally I'd like the raws, that's why I shot them in the first place.
I've tried a few pieces of software to help, including PhotoRescue Expert.. it pulled the images off the card, but the errors persist.
I've searched all over the net, including the Adobe forums and haven't found any real solution. So what can I do?
Is there any software that can repair these NEF's? Are they just corrupted and it's just tough luck? Any serious advice would be appreciated.
One more question... has anyone experienced problems with Transcend cards before, I'm wondering about their reliability.
Paul.

Sounds like bad flash media, or a bad link in the physical import chain. You can try extracting the data off those (assuming you have not formatted them) in a different manner, or on a different computer and see if he problem is in the chain somewhere between the card and the computer.
There are utilities to extract data from formatted flahs media, and when you format in-camera the flash firmware will try to spread writes over other parts of the media, so you might get lucky and be able to extract data from formatted media, assuming it is not corrupt on the media.
Which is also a possibility.
The other apps you mention don't actually read the raw image in its entirety as Lightroom does. They just read the file header and the embedded preview (which Lr does not use) so the JPEG you are extracting is just a copy of this preview. If you are lucky you might be able to reimport to get the missing trailing information that seems to be trunctated.
I bet there are command line tools you can script to extract these previews from a group of raw images in a more automated fashion.

Logical end of file error

I am getting a "logical end of file error =39" message when trying to export audio to SDII for making a time stamped (BWF) . Any ideas?

How long is the wedding video?
My standard list of things to do first...
Run MacJanitor (free download) to do all the Unix Cron Maintenance scripts.
Run Disk Utility (Applications -> Utilities) and repair disk permissions on your start up drive (typically your internal drive). Also verify any other drives mounted on the system.
Run Preferential Treatment (free download) to check for corrupt/damaged application and system preference files.
Run Cache Out X (free download) to clear all system and application caches.
Reboot your Mac.
If you still can not get it to run correctly, next thing to try is to throw out the iDVD preference file (don't forget to change back those preferences you want different from the defaults next time you run it). If it still doesn't work, then I would suggest you reinstall iDVD.
Patrick

End of file error, elements 12

I've recently started getting an 'End of file' error when I try to open around a third of my RAW files in Elements 12.
Very frustrating, as I've some decent photo's, and means I'm taking having to take photo's twice to compensate, not ideal. I wondered if it may be a space issue, so have deleted lots of files from my Toshiba laptop, and in particular edited files that use up more space. This hasn't helped though so I'm pulling my hair out.
Any help would be greatly appreciated, thank you.

Yes, definitely, the GB Project file is corrupt, delete it, empty the trash, and it would be a good idea to run some kind of disk repair program, even if it's just Disk Utility. Then create a new project file.
Good luck --HangTime [Will Compute for Food] B-|>

HELP! 'unexpected end of file' error-Is there a fix?! OS 10.4.11

Getting 'Unexpected end of file' error when trying to open a file (that's a rush job) in QuarkXpress 6.5. I attributed it to lack of memory, so I immediately backed up all files and HD to an external drive to free up space. Restarted and prayed... Quark launched, but file won't open. Same error.
Have: 2.1 GHz PPC G5, 1.5 GB DDR2 SDRAM OS 10.4.11 (pre Intel)
Capacity: 232.8GB, Available: 163GB, Used 69.6GB
Have been searching help site for 5 hours looking for answer and am DESPERATE! I saved changes regularly, but can't access this file at all... I've lost 2 full days & nights working on this project that has to be done in 2 days.
Ran Disk Utility, but no success opening this specific Quark file (Quark will launch- it's just this file that's affected). Have tried to down load Applejack, etc. but keep finding out they only support OS 10.5 or higher. (Haven't been able to afford upgraded system since Intel requires purchase of full verions of graphics software instead of upgrades to the tune of $6k).
PLEASE, I only know enough to be dangerous, so ANY help is GREATLY APPRECIATED!
Savvy folks- if I'm in the wrong place, please send me a link where I can solve this personal catastrophy.
Many thanks-in-advance

I think you best do over your work from scratch. You need to make backup copies of the files regularly. You need to have copies on multiple disks or flash drives.
I saved changes regularly
You should know that this isn't sufficient. You need to have multiplte copies of the file. Backup anyone? Could be the file structure got messed up. Could be Quark messed up the file.
You need to get a newer machine. G5's are not reliable any more. Need to see if Quark will run in compatiblity mode on an intel machine. You should at least get an external firewire drive from owc. Old hd's are not reliable.
Boot in safe mode. Hold down the shift key when powering on the machine. This will run a disk repair program. Boot up will take longer as the harddrive is scanned and repaired.
See this article:
http://docs.info.apple.com/article.html?artnum=107393
Or from:
    mrtotes article :
    Boot from the OS X Install disk and from the Menu Bar choose Disk Utility. Then run "Repair Disk" and "Repair Disk Permissions" on your hard disk.
    a brody:
    https://discussions.apple.com/docs/DOC-1689
Here the apple article on booting single user mode and using fsck. See the section on Use fsck:
http://docs.info.apple.com/article.html?artnum=106214
I suspect not but Perhaps Disk Warrior will be of some help:
http://www.alsoft.com/DiskWarrior/
Robert

End of File Error with Tiff

Similar Messages

Maybe you are looking for