On-Prem Data Connector will not provision after sandbox refresh
This article includes suggestions and workarounds. Content may not be accurate for all use cases or represent best practices for the latest release.
Question
Why is my On-Prem Data Connector not provisioning after a recent migration, clone, or refresh?
Answer
On-Prem Data Connectors that were previously provisioned in a sandbox might not exist after a sandbox refresh because the refreshed sandbox is a copy of another instance and the integration configuration may be different from what was previously configured in the sandbox.
The On-Prem Data Connector software does not automatically remove local configuration files related to the old sandbox connectors; however, it may still allow a user to try to provision the new sandbox connector which may have the same name and internal identifier as the old sandbox connectors. This can cause the On-Prem Data Connector on the server to enter a "provisioning" state indefinitely, meaning that it will never complete successfully or terminate with an error.
To provision a new On-Prem Data Connector for a new instance (or recently refreshed instance):
- Log in to the On-Prem Data Connector machine and open the On-Prem Data Connector Manager.
- Go to the Backup/Unprovision tab.
- In the Select Active OPDC dropdown menu, select each connector that starts with the sandbox instance code and click Unprovision OPDC.You can find the instance code by logging in to the sandbox and going to Administration > General Setup.

- After all On-Prem Data Connector with the sandbox instance code have been unprovisioned, close the On-Prem Data Connector Manager.
- Open the Services program, right-click on On-Prem Data Connector, and click Restart.
- After the service has restarted, open the On-Prem Data Connector Service again and provision the On-Prem Data Connector. See Create On-Prem Data Connectors.
The key is to follow the above steps before attempting to provision any On-Prem Data Connector after the sandbox is refreshed. If the old connectors are unprovisioned locally and the service is restarted beforehand, provisioning should work without issue.
