I read some FAQs and opened a firewall port on the laptop which got it to work and complete a full backup. On the laptop (this might be related to the first problem) I had issues connecting to the remote backup destination (the main computer), and I got the same 'Destination Unavailable' message.When I try to access the hard drive I can see it is working fine, and when I click the 'Backup now' button it will suddenly find it and start the backup process On the main computer (connected with USB to the external hard drive) I have many cases that I see CrashPlan say it has not ran a backup for a few days since the 'Destination is unavailable'.I have another laptop, on the same CrashPlan account, which is also set to backup to the main computer.

The main one has a 2TB external hard drive, which is set as a backup destination. Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.I'm using the free version of CrashPlan on Win7 to backup two computers at home. Delegated Authentication for Veeva CRM via MDMĬRM Knowledge Article: Are THIRD_PARTY_AUTH_URL and THIRD_PARTY_APPLIESTO_URL Required When Using SSO Login in CRM?.If SSO is not being used, the Authentication Settings can be disabled which allows the user to login with a username and password.

Navigate to Settings -> Veeva CRM -> Enable Third Party Authentication.On the iPad, click the Home Button once so that the iPad is on the home screen.The CRM Help documentation attached has more information about Delegated Authentication with and without tokens. Please find the CRM Knowledge Article below for more information regarding the Enable Third Party Authentication setting, THIRD_PARTY_AUTH_URL, and THIRD_PARTY_APPLIESTO_URL. If the user is using standard Delegated Authentication without tokens, the Enable Third Party Authentication setting should not be enabled. If the org is configured for SSO, specifically Delegated Authentication with tokens, and the user is using this specific SSO to authenticate, the Enable Third Party Authentication setting needs to be enabled.

If the org is not configured for Third Party Authentication and the user is not an SSO user, disable the Enable Third Party Authentication setting.

There are two solutions depending on whether the user is a Single Sign-On (SSO) user or not:

Code42 service is currently unavailable