- Code42 CrashPlan (previously CrashPlan PROe)
If you attempt to start the Code42 CrashPlan app and it displays the message, "Code42 CrashPlan cannot connect to its background service", this article can help troubleshoot the issue. This error usually occurs because the CrashPlan service is not running.
Under the hood
The CrashPlan app consists of two parts:
- Graphical user interface that the user interacts with
- CrashPlan service that runs in the background
These two pieces communicate over a local network connection that is built into every device. When the CrashPlan app starts, the graphical user interface and the CrashPlan service attempt to connect to each other. If they can't connect, the graphical user interface displays an error message.
Recommended solutions (all operating systems)
The recommendations below apply to all operating systems. These are the resolutions that most often resolve the issue. If these solutions don't resolve the issue, review additional recommendations below.
Restart the CrashPlan service
The first thing to try on all platforms is to restart the CrashPlan service. If this doesn't resolve the issue, try the recommended solutions below.
Out of memory
If you have a large backup selection (more than 1 TB or 1 million files), you may need to allocate more memory to the CrashPlan app. When CrashPlan runs into this memory limit, the CrashPlan service is not able to run, resulting in the "Code42 CrashPlan cannot connect to its background service" message. If you have a large file selection backing up, refer to our troubleshooting article on this topic to address the issue.
Uninstall and reinstall
If you're still having trouble, the next step is to uninstall and reinstall the CrashPlan app.
Check for port conflicts
If the CrashPlan service still does not connect, verify that another application is not already using the required ports. While CrashPlan may not require these ports all of the time, the CrashPlan service still must prepare them for use.
Recommended solutions (Windows)
If you are using a Windows device and the recommended solutions for all platforms didn't resolve the problem, try the following solutions for Windows.
Verify that the CrashPlan service is enabled
- Open the Start menu.
- Locate and open the Services program: Type services.msc into the Start menu search bar and click Enter.
- Double-click CrashPlan Backup Service.
The CrashPlan Backup Service Properties window opens.
- Ensure that the Startup Type is set to Automatic.
- If the Start service status button is available, click it to start the CrashPlan service.
- Click Apply if you made changes to your settings, then close the window.
Failure after Windows restart
If the message "Code42 CrashPlan cannot connect to its background service" returns after each reboot, this is usually caused by a Windows service causing a loopback conflict with the CrashPlan service at boot. To resolve this, you can delay CrashPlan's startup:
- Open the CrashPlan Backup Service's properties window using the directions above.
- In the General tab, change Automatic to Automatic (delayed start).
- Click OK.
Recommended solution (Linux)
If your system language is not set to English when the CrashPlan app is installed, the application starts and backs up but fails to open after rebooting the device. To ensure that the CrashPlan app is able to open after rebooting:
- Uninstall the CrashPlan app.
- Change the Linux system language to English.
Consult the documentation for your Linux distribution for instructions on changing the system language.
- Install the CrashPlan app.
- Change the Linux system language back to your language.
CrashPlan will open normally.
Manually starting the CrashPlan service after restarting your device will allow you to open the CrashPlan app.
Using this method to start the CrashPlan service will not persist after restarting the device and will have to be reapplied after every restart.