The “ Cannot Connect to Background Service ” Error is displayed sometimes while starting the Code 42 app and it indicates an issue with port availability or interruption between the functionality of the application. This error might also be triggered due to blockage from the AntiVirus.

How to Fix Code42 CrashPlan ‘cannot connect to background service’ error - 1

Cannot Connect to Background Service Error on Code 42 App

What Causes the “Cannot Connect to Background Service” Error on Code 42?

We found the underlying causes to be:

  • Glitched Application: In some cases, the app might be glitched due to which the error might be triggered. Small bugs and glitches are occasionally seen in the digital world and they often fix themselves after a simple restart.
  • Memory Shortage: Often companies have a large amount of data that has to be backed up constantly and that process requires a lot of resources. You have to allocate a certain amount of memory to the Code 42 app and this memory can sometimes run out. Therefore, if the memory runs out, the error might be triggered.
  • Previous Installations: If the Code 42 app has been installed on your system more than once, it usually leaves behind a residue file that needs to be deleted before a new installation can be completed. This file is located in the users’ personal files and there might be multiple files if there are multiple users.
  • Port Conflicts: Sometimes, the Antivirus or the Firewall might block the application from using certain ports due to which this error might be triggered. It is also possible, that there might be certain ports that are already in use by other applications and the Code 42 app is trying to use them which is creating a conflict.
  • Disabled Service: In some cases, the Code 42 Service might have been disabled due to which the error is being triggered. This service can sometimes be disabled by optimization apps that limit the background services.

Solution 1: Restarting the Application

If the application has been glitched, the simplest troubleshooting step is to restart the app and check if the glitch is fixed. Since this error is triggered mostly while signing in to the account, we will be able to access the console. For that:

  1. Start the Code 42 app.
  2. Press the following button combination for your relevant device. Windows: Ctrl+Shift+C Mac: Option+Command+C Linux: Ctrl+Shift+C
  3. Type in the following command and press “Enter”. Restart
  4. Once the app is restarted, sign in and check to see if the issue persists.

Solution 2: Allocating More Memory

If the memory allocated for the application has run out, it is recommended that you dedicate more memory towards the app or select a smaller backup. You can find the guide online to help dedicate more memory depending upon your device.

Solution 3: Removing Previous Files

If there are residues left from previous installation files, the error might be triggered. Therefore, in this step, we will be deleting the previously installed files. For that:

  1. Navigate to the following addresses depending upon your devices. Windows Vista, 7, 8, and 10: C:\Users<username>\AppData<Local or Roaming>\CrashPlan Windows XP: C:\Documents and Settings<username>\Application Data\CrashPlan Mac: /Users//Library/Application Support/CrashPlan
  2. Delete the “ .ui_info ” file in the folder and restart the Code 42 application.
  3. Check to see if the issue persists.

Solution 4: Starting Service (Windows Only)

If the Code 42 service has been stopped, the error might be triggered because it is crucial in starting the application. To start the service:

  1. Press “Windows” + “R” to open the Run prompt.
  2. Type in “services.msc” and press “Enter”. Opening services by typing “services.msc” in the Run command.
  3. Double click on the “ Code 42 CrashPlan Backup Service ” and select the “Start” button.
  4. Click on the “Startup Type” Dropdown and select “Automatic”. Changing the startup type
  5. Click on “Apply” and select “Ok”.
  6. Restart the app and check to see if the issue persists.

Note: Disable all Firewall and Antivirus software and check if that has an effect on the functionality of the application. Also, contact your ISP to forward the ports that the app is using. It can also help to reinstall the application completely after uninstalling if the above guide didn’t help.

How to Fix “Printer is in an error state” Issue?

The error “ WinRAR Error: Next Volume Is Required ” usually appears when you’re extracting a multi-part RAR archive and WinRAR can’t find (or can’t correctly identify) the next file in the sequence . This often happens when a volume is missing , stored in a different folder , or renamed in a way that breaks the archive’s expected order .

How to Fix Code42 CrashPlan ‘cannot connect to background service’ error - 2

In this guide, we’ll go over the most reliable fixes confirmed by affected users, along with what each method is doing behind the scenes so you can choose the right one for your situation.

Important: To extract multi-volume archives, you should always start extraction from the first file in the set. This is usually file.part1.rar , or (in older sets) the main .rar file that comes before .r01 , .r02 , and so on.

1. Download and Place the Missing RAR File

WinRAR needs all parts of a multi-volume archive to complete extraction. This error usually appears when one of the volumes in a set like .part2.rar , .r01 , .r02 , .001 , and similar naming formats is missing . Downloading the missing volume and placing it in the same folder as the other parts allows WinRAR to continue extracting normally .

  1. Look at the error message or review the list of archive parts in the folder.
  2. Identify which volume is missing (for example, part2.rar , .r02 , .001 , etc.).
  3. Go back to the website or source where you downloaded the archive.
  4. Locate and download the exact missing file using the same naming format as the others.
  5. Make sure the new file name matches the pattern of the rest. Example: If you have file.part1.rar and file.part3.rar , the missing one must be file.part2.rar .
  6. Move the downloaded missing volume into the same folder as the other archive parts.
  7. Confirm that all parts are in a single folder before extracting.
  8. Right-click the first file in the series (usually part1 or the main .rar file) and select Extract Here or Extract to Folder .
  9. WinRAR should now detect all volumes and continue extraction normally .

2. Manually Browse & Select the Next Volume

Use this method only if the next volume already exists , but WinRAR is failing to detect it automatically. This can happen due to incorrect naming , the file being in a different location , or a temporary file access issue. Manually browsing helps WinRAR locate the correct volume and resume extraction without interruption .

  1. Right-click the first file in the series (usually .rar or part1.rar ) and select Extract Here or Extract to Folder .
  2. When WinRAR cannot find the next volume, it will show the “ Next Volume Is Required ” message.
  3. A small window will appear, allowing you to manually select the next volume .
  4. Use the file explorer window to locate the folder where the other archive parts are saved.
  5. Select the next part based on the naming order (example: select file.part2.rar after file.part1.rar ).
  6. Make sure the selected file matches the naming format of the archive (no extra characters like (1) and no mismatched numbering).
  7. WinRAR will resume extraction using the selected volume .
  8. If additional volumes are missing or stored separately, WinRAR may prompt you again. Repeat the same process until extraction completes.

3. Rename the RAR files in Order

WinRAR relies on a proper naming sequence (such as file.part1.rar , file.part2.rar , file.part3.rar ) to extract multi-volume archives. If a file is named incorrectly, contains extra characters, or is out of order, WinRAR may fail to locate the next volume and show this error. Renaming the files correctly helps WinRAR follow the sequence and extract the archive without interruptions .

Note: Renaming only changes the file name , not the file contents. The goal is to restore the correct sequence so WinRAR can detect the next volume.

  1. Go to the folder where all the RAR files are saved.
  2. Make sure all parts of the archive are present and stored in the same folder .
  3. Check how the parts are currently named . Common patterns include:
file.part1.rar, file.part2.rar, file.part3.rar
file.rar, file.r01, file.r02, file.r03
  1. Look for files that don’t match the expected numbering pattern (for example, file.part01.rar , file.part1(1).rar , or unrelated names).
  2. Rename each file so it follows the same order without extra characters or mismatched numbering. Example:
Incorrect: file.part1.rar, file.part3.rar, file.part2(1).rar
Correct: file.part1.rar, file.part2.rar, file.part3.rar
  1. Make sure the text before the number is exactly the same for all files.
  2. Only the last part number should change.
  3. Right-click the first file in the series (usually part1.rar or the main .rar file) and select Extract Here .
  4. WinRAR should now recognize the sequence and continue extraction normally .

If you still get the same prompt: the archive set is likely incomplete (a part was never downloaded or was removed), or one of the volumes is corrupt and must be re-downloaded from the original source.