Skip to main content
Devices frequently going into inactive state
Updated over a week ago

Problem description

The devices activated with inSync Client, get marked as inactive frequently and randomly, despite the devices being regularly connected with the internet.


The following errors are observed in the inSync Client logs:

Log file:inSyncClient.xxxx-xxx.log

Log Location:C:\ProgramData\Druva\inSync4\users\<UserName>\logs

[ERROR] Error <class 'socket.error'>:[Errno 10054] An existing connection was forcibly closed by the remote host. Traceback


This error is observed in various scenarios out of which, the following are the most common scenarios:

  1. The connection is sending malformed data to the application.

  2. The network link between the inSync Client and server is going down for some reason.

  3. Something has triggered a bug in the application that caused it to crash.

  4. The application has exhausted system resources.

The aforementioned 4 issues may also have various reasons to occur, however, the following reasons are common:

  1. Data packets dropped due to network adapter issues. Mostly due to non-updated network drivers.

  2. Network data transfer monitoring software.

  3. Antivirus programs.

  4. Restrictions on the network to which the device is connected.

  5. Lack of resources on the device.


  1. We strongly recommend you to implementantivirus exclusions for inSync Client.

  2. You can alsomanage the network bandwidthallotted to the devices.

  3. We suggest you consult with your networking team or Windows team to check for network-level interruptions for your devices.

  4. Check for any missing updates for the network drivers on the devices. Consult with your Windows or Networking team about this.


  • Since the devices are in the inactive state, the persistent connection between the device and the inSync Cloud is lost.

  • Thus, inSync Administrators will no longer be able to trigger a backup from the inSync Management Console.

If the information provided in this article does not address the issue, then kindly submit a support ticket from the Druva Support Portal for further investigation.

Did this answer your question?