rgorelik

Q: CoreTelephony Trace File Error

Have an CoreTelephony Trace File Error, a file operation has failed, you may be out of space. Details: 'Failed to create directory /Network (0755)

Error occurred then user log in, after installing El Capitan.

What I can do?

iMac, OS X El Capitan (10.11)

Posted on Oct 2, 2015 12:10 AM

Close

Q: CoreTelephony Trace File Error

  • All replies
  • Helpful answers

first Previous Page 5 of 5
  • by christian222,

    christian222 christian222 Oct 17, 2016 10:04 PM in response to rgorelik
    Level 1 (4 points)
    Oct 17, 2016 10:04 PM in response to rgorelik

    I just thought I would share my results from this…

     

    So it turns out that all of the fixes on this site (http://www.macosxblog.com/how-to-fix-coretelephony-trace-file-error-on-mac/) require to turn off system protection mode which requires being in recovery mode.  Unfortunately since i am remote to the Mac OS X server running 10.11.6, I was unable to do that.  Therefore I decided to just upgrade to MacOS Sierra.  That fixed this issue completely.  So whatever was the issue the upgrade to Sierra solved the problem. 

  • by SoloMeter,

    SoloMeter SoloMeter Oct 17, 2016 11:25 PM in response to christian222
    Level 1 (8 points)
    Oct 17, 2016 11:25 PM in response to christian222

    HI,

     

    I contacted apple support and they advised the following which worked for me. I didn't need to go the sierra option, but if the reinstall OS X doesn't work, then sure try the last option.

     

    Steps

    Let’s restart your Mac into OS X Recovery by restarting and pressing Command-R upon restart and holding for one minute. From there, let’s click on Disk Utility > click your Macintosh HD > click First Aid at the top.

    This will ensure there are no underlying issues with the hard drive itself.

     

    From there, if there are any hard drive issues, that would be an indication of a hardware issue. However, if there aren’t, we’ll want to close out of Disk Utility while still in recovery mode, then choose Reinstall OS X. ( its the second option) This will reinstall the current version of OS X and only reinstall system files without erasing any user data, and can often times fix issues like this where it’s returning a trace file error. note: if you are not connected to ethernet, you will need to connect to wifi by clicking on the wifi icon in the top right of the recovery screen.

     

    Another option we can use to get this resolved in the event reinstalling OS X doesn’t work is upgrading to Sierra and then attempting reinstalling after.


    Cheers SoloMeter

  • by HerrRoetger,

    HerrRoetger HerrRoetger Oct 18, 2016 8:59 AM in response to rgorelik
    Level 1 (17 points)
    Mac OS X
    Oct 18, 2016 8:59 AM in response to rgorelik

    Same problem here, 21.5 inch late 2013 iMac, El Capitan

     

    Man, there are a lot of people running into this error recently, but still, there is no way known to me to fix it...

  • by julia-fl,

    julia-fl julia-fl Oct 18, 2016 10:54 PM in response to rgorelik
    Level 1 (4 points)
    Oct 18, 2016 10:54 PM in response to rgorelik

    Install MacOS Sierra version 10.12 - the Trace file error will go away.

  • by patdahat,

    patdahat patdahat Oct 19, 2016 2:24 AM in response to rgorelik
    Level 1 (8 points)
    Mac OS X
    Oct 19, 2016 2:24 AM in response to rgorelik

    I purchased new, a late 2015 model that came with El Capitan and is currently on version 10.11.6. It has only started displaying this pop-up upon log-in in recent weeks. Not unlike the iPhone/iPod Touch MyMusic autoplay malfunction (i.e., upon USB connection) that Apple Forum members have been screaming about for several years now, I see no helpful response and/or even remote concern on Apple's part with these annoyances and user-UNfriendly errors. Even the "geniuses" at The Genius Bar cannot offer any useful suggestions for addressing these system failures. They should consider a new marketing strategy based upon "sincerity" and "transparency", employing the catch phrase, "There are no solutions, only problems.

  • by dinerdog,

    dinerdog dinerdog Oct 19, 2016 10:15 AM in response to patdahat
    Level 1 (4 points)
    Oct 19, 2016 10:15 AM in response to patdahat

    Problem solved!

     

    Had mostly the same info: iMac Late 2015, El Cap etc. Tech support tried EVERYTHING. Only thing that instantly worked was to reinstall the OS from Recovery mode. Everything worked perfectly. No passwords to reset, nothing to re-authorize. Seemed a little faster too. Should've done this immediately and may in the future when things get buggy.

  • by psendeavor,

    psendeavor psendeavor Oct 19, 2016 10:57 AM in response to rgorelik
    Level 1 (14 points)
    Oct 19, 2016 10:57 AM in response to rgorelik

    Same problem here too, new iMac with El Capitan. Coretelephony error popped up yesterday without any changes/updates/installments etc to the system.

     

    Annoyed! What did Apple do here?

  • by dinerdog,

    dinerdog dinerdog Oct 19, 2016 2:37 PM in response to HerrRoetger
    Level 1 (4 points)
    Oct 19, 2016 2:37 PM in response to HerrRoetger

    Try reinstalling the OS from Recovery mode. Should work fine. Let us know.

  • by jwhitby,

    jwhitby jwhitby Oct 21, 2016 12:36 AM in response to patdahat
    Level 1 (4 points)
    Oct 21, 2016 12:36 AM in response to patdahat

    Similar symptoms here, error first appeared last week, not obviously linked to any upgrades of the OS (10.11.6) or Skype or similar services although I do use various browser-based web-conference systems which often seem to download a plugin. Changing the permissions of the /tmp directory didn't help me, but a reboot in recovery mode and a re-installation of the OS did fix the error message.

first Previous Page 5 of 5