User Login

Help Community Login:

CrashPlan Help? "Can't Connect to Service, Try Again?"

1 reply [Last post]
Voudas's picture
Relationship Status:
Single & Looking
Joined: 10/27/2013
Posts: 1
Drops: 3
Mood: Awake

hi all. Suddenly my CrashPlan tray icon is gray all the time and when I try to start the backup again it hangs for a while, and then shows the message:

Can't Connect to Service, Try Again?

With Yes and No buttons. No matter how many times I click the Yes button, I just keep getting this same message. I DON'T want to have to do a full re-install just to fix their stupid, broken software! It was working just fine and then just suddenly stopped. Does anyone can help me?

I Averaged: 3.5 | 2 votes

Read More ...

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
STaRDoGG's picture
Head Mucky MuckJoined the Dark SidePremium Member (Gold)I'm a Code Monkey!The Steel CurtainI use FirefoxI use Google ChromeI use Internet ExplorerI use SafariLinux UserMac UserWindows UserI donated to GeekDrop simply because I love it!Booga Booga BoogaI took a bite of the AppleFormer Phrozen Crew MemberI'm MagicMember of VileThe Dr. put the stem on the apple!The JokerSomeone thinks you're udderly delightful!
Relationship Status:
Single & Not Looking
Joined: 01/14/2009
Posts: 2609
Drops: 3088
Mood: Energetic
Re: CrashPlan Help? "Can't Connect to Service, Try Again?"

I've run into this problem in the past. CrashPlan is a great service, but slooooowww to backup, and their software is real fussy.

Anyway, first thing to try is this:

  1. Open the CrashPlanService.ini, which resides in the same folder where CrashPlan was installed to on your computer. (open with Notepad).

  2. Look near the top, where is says "Output File=". It shows where it keeps a log of what it's doing. By default, it should be "C:\ProgramData\CrashPlan\log\service_output.log".

  3. Open that file in Notepad too, then look near the bottom. It should show you what the problem is.


Chances are pretty likely that at the bottom of that file it'll mention something like this:

There is an incompatible JNA native library installed on this system. To resolve this issue you may do one of the following:
- remove or uninstall the offending library
- set the system property jna.nosys=true
- set jna.boot.library.path to include the path to the version of the jnidispatch library included with the JNA jar file you are using

(Bold text added by me, because this is what we're going to address in this fix).

  1. Go back to CrashPlanService.ini, and around line 11, where it says "Virtual Machine Parameters=", add this to the end of that line: -Djna.nosys=true

  2. Save the file, overwriting if it asks.

  3. Restart the CrashPlan Service: Right-click on your windows Taskbar -> click "Task Manager" -> Click the tab that says "Services" -> Look for "CrashPlanService" -> Right-click it and click Restart.

  4. Start CrashPlan back up, it should connect now, without issue. *fingers crossed* Wink

Shhh.. dont tell anyone, but we also have a private forum area with the really good stuff, see?

Who's New

nemesis3290's picture
chap2315's picture
GeekGirlFTDropOG's picture
Pancake's picture
Stephenhaw909's picture
travis's picture
hawkeyefxr's picture
Michaelchung2002.'s picture
Norielm19's picture
vankemp68's picture
ajfan91's picture
Circuit VPN's picture
itsjusme's picture
Wcochran271's picture
braybray's picture
facebook codes exploits tips tricks Phrozen Crew
All contents ©Copyright GeekDrop™ 2009-2021
TOS | Privacy Policy