Loading...
Loading...
When attempting to add a Salesforce sandbox to an on-premise installation of Veeam Backup for Salesforce, the following error occurs: 4BDN: Connected Salesforce Org already exists.
This occurs when the sandbox being added has the same name as a Salesforce sandbox that was previously added to Veeam Backup for Salesforce. This often occurs when a sandbox is refreshed. When a Salesforce sandbox is refreshed, the following occurs: The sandbox organization name stays the same. A new sandbox Organization ID is created. Because the sandbox name does not change, but the Organization ID does, Veeam Backup for Salesforce cannot continue the existing backup or add the sandbox as a new organization.
The solution to this issue depends on whether the existing backups of the Salesforce sandbox need to be retained. The choice is whether to retain the backups or keep the sandbox's existing name.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.