Skip to main content

This article applies to CrashPlan PROe version 4.

Code42 Support

Unable to reactivate users in a previously deactivated organization

This article applies to CrashPlan PROe version 4.


In version 4.2 of the Code42 platform, there is a known issue in which an administrator cannot reactivate a user that belongs to a previously deactivated organization. To resolve this issue, instruct the user to sign in on a device associated with that user.


Code42 environments running version 4.2 of the Code42 platform, in the following scenario:

  1. An administrator deactivates an organization.
  2. The administrator reactivates the organization.
    This action is expected to reactivate users and devices in the organization, but users and devices are not reactivated.
  3. The administrator cannot directly reactivate users and devices from the administration console.
Resolved in 4.3.0
This issue is resolved in version 4.3.0 of the Code42 platform. If possible, we recommend upgrading to version 4.3.0 or later.

Recommended solution

A user can resolve this issue by signing in to a device associated with the user's account. In this situation, signing in reactivates the user's account and the associated device.

Alternative solution

To resolve this issue, an administrator can:

  1. Sign in to the administration console.
  2. Block the user.
  3. Reactivate the user.
    The user and the user's devices are successfully reactivated.