Remove duplicate section

Author: PatAltimore

articles/iot-edge/troubleshoot-common-errors.md

@@ -537,22 +537,6 @@ You do not need to disable socket activation on a distro where socket activation
 1. Change the iotedge config to use `/var/lib/iotedge/*.sock` in both `connect` and `listen` sections
 1. If you already have modules, they have the old `/var/run/iotedge/*.sock` mounts, so `docker rm -f` them.
 
-## DPS client error
-
-**Observed behavior:**
-
-IoT Edge fails to start with error message `failed to provision with IoT Hub, and no valid device backup was found dps client error.`
-
-**Root cause:**
-
-A group enrollment is used to provision an IoT Edge device to an IoT Hub. The registration is deleted in DPS. A new registration is created in DPS to link to a different IoT hub. The device isn't reprovisioned because reprovisioning is set to false.
-
-**Resolution:**
-
-If you remove the group enrollment and re-create it, you must run `sudo iotedge system reprovision` to reprovision the device. Run the reprovision command even if no DPS information has changed in `config.toml` for the device.
-
-To automatically reprovision, use the `always_reprovision_on_startup` or `dynamic_reprovisioning` lines to configure your device's reprovisioning behavior. If a device is set to reprovision on startup, it will always attempt to provision with DPS first and then fall back to the provisioning backup if that fails. If a device is set to dynamically reprovision itself, IoT Edge (and all modules) will restart and reprovision if a reprovisioning event is detected, like if the device is moved from one IoT Hub to another. Specifically, IoT Edge checks for `bad_credential` or `device_disabled` errors from the SDK to detect the reprovision event. To trigger this event manually, disable the device in IoT Hub. For more information, see [IoT Hub device reprovisioning concepts](../iot-dps/concepts-device-reprovision.md).
-
 ## Next steps
 
 Do you think that you found a bug in the IoT Edge platform? [Submit an issue](https://github.com/Azure/iotedge/issues) so that we can continue to improve.