Powered byCRASHPLAN

Questions? Call +31-157-112-149
or Contact us online

Apple update Java 1.06.0_37 causes CrashPlan to not start

Affects

OS X 10.7 and 10.8 with Java 1.7 installed

  • October 16, 2012, Apple released an update to Java 1.6. This update changes default Java runtime to version 1.7 when possible.
  • As Java 1.7 is not available for 10.6 or earlier, older Mac OS X versions are not affected.
  • For those who were running Java 1.6, CrashPlan still works.
  • For those who were running Java 1.6 alongside Java 1.7, this update causes Java 1.7 to be used by default, and CrashPlan no longer works.

 

Solution

Edit the CrashPlan engine's com.crashplan.engine.plist ("the plist file") file to make CrashPlan use Java 1.6. You will need to use Terminal for this.

  1. Stop the backup engine by copying this into the Terminal application:
    $ sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist
  2. Run this command to edit the backup engine its plist file:
    $ sudo nano /Library/LaunchDaemons/com.crashplan.engine.plist
  3. When prompted, type in your computer's Admin password. Note that you will not see the text-cursor move when you do - this is normal.
  4. Find the line (Ctrl + W is the shortcut for searching):
    <string>/usr/bin/java</string>
  5. Replace it with:
    <string>/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Commands/java</string>
  6. Hold the Control key and tap the x key to exit. Choose y to confirm it.
  7. You'll see the prompt "File Name to Write: /Library/LaunchDaemons/com.crashplan.engine.plist". Hit enter to save to the existing location.
  8. Start the backup engine by executing:
    $ sudo launchctl load /Library/LaunchDaemons/com.crashplan.engine.plist

Once you have done this please re-open the CrashPlan Desktop and confirm that CrashPlan is working as it should.

Apple-Update Java 1.06.0_37 verursacht dass CrashPlan nicht startet Apple-update Java 1.06.0_37 veroorzaakt dat CrashPlan niet begint