This topic lists the errors that you might encounter while mass deploying inSync Client using IMD.
Note: For Druva inSync Private Cloud, see Integrated mass deployment error messages.
List of error codes
The following table describes the errors and the action to resolve it.
|Error||Issue||What to do|
|17 - Server is not reachable.||Druva inSync Server is not reachable due to issue with network connectivity or network configuration.||Verify your network configuration or network connection to resolve the issue.|
|22 - Invalid mass deployment token.||The authentication request sent by inSync Client includes the mass deployment token. This mass deployment token is either invalid or has expired.||Generate a new mass deployment token. For more information, see Generate a mass deployment token.|
|34 - Dropped network connection.||Connection to Druva inSync Server was established but dropped due to network connectivity issue.||Verify your network connection.|
|95 - Authentication error.||The authentication request sent by inSync Client includes the mass deployment token. This mass deployment token is either invalid or has expired.||Generate a new mass deployment token. For more information, see Generate a mass deployment token.|
|106 - Number of devices activated have exceeded the limit.||
You have exceeded the maximum number of users for whom you can mass deploy inSync Client.
|The number of devices that an user can activate is driven by the profile associated with the user account. For more information, see Allow users to activate Druva inSync.|
|110 - Security certificate presented by Druva inSync Server is not trusted by your operating system.||Security certificate presented by Druva inSync Server is issued by a certificate authority that is not trusted by your operating system.||If the issue persists, contact Druva Support.|
|138 - Requested AD Mapping does not exist.||For an user activation through IMD, Druva inSync Server cannot find the associated AD mapping.||
To resolve this issue, ensure the following;
|167 - Only first device is allowed to be activated during mass deployment.||IMD is configured to activate inSync Client only on the first laptop that the user logs on to.||To update the configuration, see Configure integrated mass deployment settings.|
|168 - Common Name or User Principal Name is invalid.||Druva inSync user name for a user account created does not have a Common Name or User Principal Name (UPN) associated with it.||Set a common name or UPN for the user account.|
|169 - Timeout occurred for IMD.||Upon installation on a device, inSync Client did not activate within configured time.||
To resolve the issue,
|170 - No active AD user sessions for IMD activations.||The user has not logged on to the laptop where you have installed the inSync Client using IMD. Only after the user logs on to their laptop using the AD credentials, the inSync Client fetches the user's AD information from the AD Server.||
To resolve the issue, check the following and take appropriate action;
|171 - A user is already activated on this device. Multiple user activation is disabled on a single device.||By default, only one user activation is allowed per device.||If you want to update the behavior, contact Druva Support.|
Server security certificate is not trusted by Druva inSync. do you want to use system's certificate store?
inSync Client has failed to validate Druva inSync server's certificate.
This is expected if the client connects with the server through an MITM proxy and the message is displayed when the user is performing inSync Client activation.
If you are sure of the MITM setup and that the root certificate of MITM proxy is installed on the client device, ask the user to click Use system store's certificates and proceed with inSync Client activation.