Skip to main content
hendrikc99490104
Participant
December 1, 2016
Answered

Creative Cloud wont launch

  • December 1, 2016
  • 1 reply
  • 2005 views

Hey Adobe community,

I bought my Creative Cloud package about three days ago and been trying to open it ever since. I’m using a MacBook Pro (late 2012 running OS X Sierra) and already installed, uninstalled and cleaned my Mac with the the ACC-Cleaner Tool several times. The installation doesn’t seem to be the issue though. It installs the Creative Cloud Desktop Application but it wont open. Neither does the app launch nor does the little icon appear in the top right corner of my menu bar. The only thing I noticed is, that during installation the dock on my screen disappears for about a second but I don’t know if that is unusual or not.

I’ve already been searching solutions online, like using a second admin account, cleaning my hosts file or reinstalling OS X Sierra.

Nothing worked.

My AdobeIPCBroker log says this every time I try to open CC

2016-12-01 20:06:46:582 : ERROR vcfoundation::io::VCEndOfFile: send() failed <32: Broken pipe>

Trace: 0   AdobeIPCBroker                      0x000230fa AdobeIPCBroker + 139514

1   AdobeIPCBroker                      0x00022b3d AdobeIPCBroker + 138045

2   AdobeIPCBroker                      0x00029e60 AdobeIPCBroker + 167520

3   AdobeIPCBroker                      0x000289e8 AdobeIPCBroker + 162280

4   AdobeIPCBroker                      0x000263b4 AdobeIPCBroker + 152500

5   AdobeIPCBroker                      0x0001f7ee AdobeIPCBroker + 124910

6   AdobeIPCBroker                      0x00026b6d AdobeIPCBroker + 154477

7   AdobeIPCBroker                      0x00026951 AdobeIPCBroker + 153937

8   AdobeIPCBroker                      0x0002589a AdobeIPCBroker + 149658

9   AdobeIPCBroker                      0x000296f7 AdobeIPCBroker + 165623

10  libsystem_pthread.dylib             0x9f8a810b _pthread_body + 184

11  libsystem_pthread.dylib             0x9f8a8053 _pthread_body + 0

12  libsystem_pthread.dylib             0x9f8a792e thread_start + 34

and the log of the AdobeCRDaemon

Process:               AdobeCRDaemon [1848]

Path:                  /Users/USER/*/Creative Cloud.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/AdobeCRDaemon.app/Contents/MacOS/AdobeCRDaemon

Identifier:            AdobeCRDaemon

Version:               ???

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           AdobeCRDaemon [1848]

User ID:               501

Date/Time:             2016-11-29 19:08:46.985 +0100

OS Version:            Mac OS X 10.12.1 (16B2555)

Report Version:        12

Time Awake Since Boot: 1900 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'

terminating with uncaught exception of type NSException

abort() called

I really hope you can help me out.

Thank you.

This topic has been closed for replies.
Correct answer hendrikc99490104

In order to get it to work, I completely reset my Mac. The installation and launch of ACC worked absolutely fine this time.

Thanks for your quick help anyway.

1 reply

Jeffrey_A_Wright
Legend
December 2, 2016

Moving this discussion to the Adobe Creative Cloud forum.

Hendrikc99490104 to confirm that you are not facing an installation failure I would recommend completing the steps listed in "Failed to install" error received when installing Adobe Creative Cloud desktop app​.  If you have any questions regarding the steps, or experience any errors, you are welcome to update this discussion.

hendrikc99490104
hendrikc99490104AuthorCorrect answer
Participant
December 3, 2016

In order to get it to work, I completely reset my Mac. The installation and launch of ACC worked absolutely fine this time.

Thanks for your quick help anyway.