Can't save=Error -39 Logical End Of File Reached

Hi whenever I try to re-save a .jpg file, I get the "Error -39 Logical End Of File Reached."
I have tryed everything I can think of: Copy/Pasting; Importing, etc. with no success. Any help would be greatly appreciated!
Thanks.

DamonGrant wrote:
Thanks for those suggestions Erik...
It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.
It seems to happen after working on a project for some time.
After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?
Now there might be a clue. What happens when you then quit Logic, reboot your Mac, and reopen the active session? It might be that your disk has become a bit messy from all the traffic, and it just needs to 'settle' in OS X again. Click on the *Spotlight icon* top right of your screen and see if any indexing is taking place. Wait for it to finish before launching Logic.
Alternatively, you could exclude your recording disk from Spotlight indexing alltogether, by dragging the disk to the Privacy field in the Spotlight Sysprefpane.
One other thing to do: turn off Journaling , using *Disk Utility.* Select your recording volume in Disk Utility, hold the alt key while dropping down the File menu. Choose *Disable Journaling.*
On the other hand, it might also point to a RAM issue. Do you ever suffer Kernel panics (=the darkening 'curtain' and the message "You need to restart your Mac... etc")? or 'unexplained' crashes? If not or very rarely, I'ld rule out a RAM issue. If daily, it could be. What you can try in this case is to turn of your Mac and physically take out and reinsert your RAM.
And when you trash (=eject/unmount), physically disconnect and reconnect your recording disk? Does that help? (Logic should not be running when you do this)

Similar Messages

Error: Logical end-of-file reached during read operation. Result Code = -39

Hello all,
Recently, I have been suddenly getting this error message:
"Logical end-of-file reached during read operation. Result Code = -39."
In my case, when it does come up, it always pops up during the recording of an audio take. Almost immediately after hitting the stop button, this error message would pop up. And then when I go to check the take that was just recorded, there is nothing but shrieking noise. As a result, this pop up error trashes any good take I may have had. It's unpredictable as to when this error decides to pop up as well. So now, when I record, I tend to just have my fingers crossed and hope that this error doesn't pop up especially right after recording a good take!
To no avail, I have tried different I/O buffer settings, repaired permissions, rebooted, and even re-formatted my recording hard disk.
Could this be a possible hint that my hard disk is about to physically collapse? I have had it for about 2 years. Could it be some sort of bug in Logic? Or something else perhaps?
Appreciate any feedback! Thanks a lot!

DamonGrant wrote:
Thanks for those suggestions Erik...
It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.
It seems to happen after working on a project for some time.
After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?
Now there might be a clue. What happens when you then quit Logic, reboot your Mac, and reopen the active session? It might be that your disk has become a bit messy from all the traffic, and it just needs to 'settle' in OS X again. Click on the *Spotlight icon* top right of your screen and see if any indexing is taking place. Wait for it to finish before launching Logic.
Alternatively, you could exclude your recording disk from Spotlight indexing alltogether, by dragging the disk to the Privacy field in the Spotlight Sysprefpane.
One other thing to do: turn off Journaling , using *Disk Utility.* Select your recording volume in Disk Utility, hold the alt key while dropping down the File menu. Choose *Disable Journaling.*
On the other hand, it might also point to a RAM issue. Do you ever suffer Kernel panics (=the darkening 'curtain' and the message "You need to restart your Mac... etc")? or 'unexplained' crashes? If not or very rarely, I'ld rule out a RAM issue. If daily, it could be. What you can try in this case is to turn of your Mac and physically take out and reinsert your RAM.
And when you trash (=eject/unmount), physically disconnect and reconnect your recording disk? Does that help? (Logic should not be running when you do this)

Keep getting message pop up "Error reading/writing file "com.apple.logic.pro.cs": Logical end-of-file reached during read operation," and "The Preferences are not loaded completely. Save them to "com.apple.logic.pro.cs" anyway?" Using Logic pro 8. ???

Logic froze while I was working on something so I forced quit. Now every time I open LOGIC a message pops up that says:
"Error reading/writing file
“com.apple.logic.pro.cs”:
Logical end-of-file reached during read operation."
The only button option is cancel so I press it and another message appears that says:
"The Preferences are not loaded completely.
Do not save them, as you would overwrite the Preferences file with incomplete data."
Then when i close logic a box appears saying:
"The Preferences are not loaded completely.
Save them to "com.apple.logic.pro.cs" anyway?"
There are 3 button options to press; ok, cancel or dont save.
I press "don’t save" cuz I don't want to ruin anything.
I found a discussion located here: https://discussions.apple.com/message/9564253#9564253 that says if I delete the file "com.apple.logic.pro.cs" it will resolve the problem. If I do this will I loose or mess anything up at all, automation, saved channel strips customizations, saved effects, synth, or ultrabeat customizations etc? Or especially will I loose any work I've done? I have hundreds pieces of music files I've created. I'm scared to mess anything up with all the hours and months of work I've done. Is there anyway to fix this without loosing anything? I'm using Logic Pro 8.
Thank you

You can safely delete this file - its the preference file for control surface settings - you haven't said whether you're actually using a control surface or not, if so, you will have to set it up again. A new file will be created when you fire Logic up again, but of course it will contain default settings. If you have a complicated control surface setup, remember to keep a backup copy somewhere in case any future problems arise.
Other than that, you really have nothing to be scared about - hopefully your problem is as simple as that and there isn't an underlying problem (a corrupt hard drive, for example). You seem concerned about losing work, so I guess you want to think about backing that up on a regular basis too. If you're saving your projects to your system drive, do get an external one for this. And also check that you have plent of free space on your system drive - you need to keep about a quarter or third of it free for your OS and programs to run properly (some temporarily stored files can be quite large).

Error "logical end of file reached during read operation"

I am trying to burn a dvd of a wedding I did, and this is the error I am getting. After 5 hours of it trying to burn when I click cancel this it says " logical end of file reached during read operation". Does anyone know what this means, and how I can fix it? I am anxious to get this wedding finished and out to the customer. Any help would be greatly appreciated.

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

U201Ccom.apple.garageband.cs\U201D - Logical end of file reached...

Hello,
I'm getting two errors. Hopefully someone can help with one or both.
1) U201Ccom.apple.garageband.cs\U201D - Logical end-of-file reached during read operation.
From other posts, I've tried to go into Library -> Prefs -> but, there's no file there to delete. I also have reinstalled Garageband, with the same issue popping up.
2) "Garageband unexpectedly quit." - Not sure what's going on here. Anytime I close the program, it has a 2 second lock-up, and then the yellow triangle with the exclamation point pops up with that message?
I do not have any 3rd party apps or add-on's.
Thanks in advance.
Cheers,
Sean

I've tried to go into Library -> Prefs -> but, there's no file there to delete.
http://www.bulletsandbones.com/GB/Tutorials.html#deleteprefs

Logical end-of-file reached during read operation

Hi,
Something strange happened to my Logic a couple of days ago - all of a sudden. When I start Logic up it gives me the following error message:
*Error reading/writing file “com.apple.logic.pro.cs”: Logical end-of-file reached during read operation.*
I have re-installed Logic, as well as updated it (8.0.2), I have repaired disk permissions in Disk Utility, and it still keeps popping up. I cannot get on with my projects and I have deadlines!
I found an IT support site, according to that I don't have enough space on my HD. However, I do... I'm confused, and desperately need help.
Thank you so much, I'm looking forward to hearing from somebody.
Agnes

I am not opening any files, just launching Logic.
I know. And when you launch Logic, it loads its preferences files - and it seems this is failing - most likely due to file corruption. So delete the file, as I said, and Logic should load fine.

EXS 24 Logical end-of-file reached during read operation Result code = -39

EXS kit Trip Hop Remix will not completely load. Upon trying to load it I get the error, Logical end-of-file reached during read operation Result code = -39. The kit ends up lacking samples. It worked at one time but now it will not load up. To try and fix I extracted two kits with the same name but oddly they are slightly different sizes and have different creation dates, one 2004 the other 2007 hmmm (one goes in Garage band for remix tools the other gets placed in 02 Electronic Drum kits) from the install disks using Pacifist hoping to replace corrupted files. NG. I also reinstalled all the samples from the LP8 install disk, still NG. Anybody have a solution. THanks.

To further clarify, the samples are all located in the folder Garage band/.../.../.../Sampler Files/Treated Percussion Sets/Perc-DnB+Triphop. They are used in the EXS24 Trip Hop Remix kit.exs. The 3 samples that seem to be causing the error are, YT2BGLRHTX02_3ue.aif, YT2BGLRHTX03_3ue.aif, YT2BGLRHTX04_3ue.aif. The kit is useless and my song is screwed up now that the kit will not load. Any ideas for a fix out there ?

What mean "logical end-of-file reached" messaage ? (screen attached)

I see that when loading project. Is all ok after i press OK but what is that means ?

Not seeing a picture... are there audio files associated with this project?
Logical-end-of-file-reached usually refers to a corrupt audio file where the data header file end does not match the actual file length. In other words, the audio file it truncated or the file header describing the file is corrupt.
It could also be an audio file has been marked "read only" but that is less likely.
Are you sure all of your audio files are working correctly.

"Logical End of File Reached"

Ok, this error happens randomly when punching in. I'm using "punch on the fly" and comping the track afterwards. Sometimes on the punch after I hit stop, that error pops up which I have to hit cancel on. If I play the audio back it's a nasty "pink noise" type of sound. If I undo it and record again it's fine. The dialog that pops up during recording says I have 268:0:00 or whatever left so it's not like I'm reaching the end of my track. It happened on a drum punch this past weekend...A vocal punch Tuesday, and a guitar solo punch yesterday during a really hard sweeping section. The guitarist wasn't too happy about that after he nailed it...

Yeah, mine's for audio. I haven't gotten it yet while working with samples. I do have a problem with the organ samples that are built in with Logic...They only work below the A below middle C. None of the other patches have this problem...I don't know if it's an organ bug or not.

Logical end-of-file reached during read operation Result code= -39 ANYONE ?

I am aware this is an error that can occur when trying to load files off a drive into ram that may be corrupt in a certain way. I am an Apple Logic Pro 8 user getting this error when trying to load certain apple .aiff samples that came with LP8. I think I have this small group of files narrowed down and have even tried re-installing them from the install disks. Same error. These audio files playback fine when previewed in finder, but when I try to load them into my software, I get the above errors. How can I repair these damaged files. No one so far on the LP8 forum have responded to my post in the LP8 forum.

ert

Logical end-of-file reached during read operation - Errorcode -39 - EXS24

After i switch the harddisc-speed from medium to slow in the exs24 virtual memory setting, everything works fine. If i now try to relaunch the Song i get this error-message and one exs24-instrument sounds strange. This is a sound from one garageband expansion pack. If i now reset this setting to medium again, everything is allright.
Mac Pro Two 3.0GHz Dual-Core Intel Xeon Mac OS X (10.4.9) Logic Pro 7.2.3

It's a problem when (opening a song) Logic try to
open an exs24 with some corrupted sound.
YES! This is absolutely correct.
Problem solved!
After posting my problem on two boards:
First, I went through the songs audio files one by one, in Logic's audio window using the "Change/Convert" command with "Change file reference in audio window" selected. This didn't help in this case though.
After looking through the EXS24 tracks I discovered that the culprit must have been sample(s) for an "exotic" EXS24 percussion track. After bouncing the track, I re-added it from Audio window, and now the error is gone.
Phew! Thanks everybody.
PETE
http://www.myspace.com/petedako

"Logical end-of-file reached during read operation, result code = -39"

This is the message i get when I open Logicpro. I don't really see what difference it makes, but rcently I noticed the "trip Hop Remix" kit does not produce any sound at all. When I copy a loop whcih comprises of Trip Hop remix as an instrument, it plays only as an audio files, i.e, i have to copy the file into an audio track from the library. It does not play if copied into a MIDI track, and hence, I cannot edit it. the error message, and the absense of sound from the instrument, are they linked?

hi,
they are linked.
the HipHopKit makes not sound 'cos logic cannot find some/all of the samples used.
Spotlight prolly needs updating, and this might not do the trick.
back in logic 5, (emagic) i used to get this a lot.
less so now.
usually on EXS instruments that i haven't used for years.
i had to manually load ALL pertinent samples into some of the EXS instruments a coupla years ago, when apple included the Jam Packs with LP.
mainly the drum kits, maybe because they do spare some sample sets.
best.
j.

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

BI7 Transport system active can not save error

Transport system active can not save error
Hi ,
We are using BI7 SP13 integrated with Portal.When we try to save the reports it throws error" Transport system is active can not save"
BI 7.0 Test Server still has SP09 and the report works fine.
Has anyone experienced this issue before ?? Pls suggest

Hi Kristene,
Are you getting this error for one report or for all the reports which you are trying to save them in your favourates.
Best Wishes.
Kumar

End-of-file reached (-39) error

I currently use QT 7.0.2. Frequently when I join multi-part AVI. videos together using "Split and Concat" software and try to play them I get the error message "end-of-file reached (-39)" and nothing happens. What does this message mean and how can I remedy the situation?

DamonGrant wrote:
Thanks for those suggestions Erik...
It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.
It seems to happen after working on a project for some time.
After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?
Now there might be a clue. What happens when you then quit Logic, reboot your Mac, and reopen the active session? It might be that your disk has become a bit messy from all the traffic, and it just needs to 'settle' in OS X again. Click on the *Spotlight icon* top right of your screen and see if any indexing is taking place. Wait for it to finish before launching Logic.
Alternatively, you could exclude your recording disk from Spotlight indexing alltogether, by dragging the disk to the Privacy field in the Spotlight Sysprefpane.
One other thing to do: turn off Journaling , using *Disk Utility.* Select your recording volume in Disk Utility, hold the alt key while dropping down the File menu. Choose *Disable Journaling.*
On the other hand, it might also point to a RAM issue. Do you ever suffer Kernel panics (=the darkening 'curtain' and the message "You need to restart your Mac... etc")? or 'unexplained' crashes? If not or very rarely, I'ld rule out a RAM issue. If daily, it could be. What you can try in this case is to turn of your Mac and physically take out and reinsert your RAM.
And when you trash (=eject/unmount), physically disconnect and reconnect your recording disk? Does that help? (Logic should not be running when you do this)

Can't save=Error -39 Logical End Of File Reached

Similar Messages

Maybe you are looking for