Sandbox refresh results in usernames being prefixed and old sandbox still accessible.
Last updated 2018-03-30 ·Reference W-2410200 ·Reported By 255 users
Upon refreshing a sandbox, you may receive an email message stating:
"Some users could not be created with their original user names in this sandbox. This is usually because these users exist in a previously copied sandbox and user names must be unique across all sandboxes."
Alternatively, if you attempt to change a username you may encounter the following validation error,
"Error: Duplicate Username.
The username already exists in this or another Salesforce organization. Usernames must be unique across all Salesforce organizations. To resolve, use a different username (it doesn't need to match the user's email address)."
Users may find that they are unable to login to the sandbox using the typical sandbox username convention and instead have to use the provided prefixed username to login. This may be due to an unexpected circumstance where the previous version of the sandbox has not been deleted properly.
If the previous refresh's sandbox environment is not deleted the username persists causing the new refresh's resulting username to not be unique so a second modification is performed in which a number of characters and digits are prepended to the modified username. This second modification may result in a username such as 00x7Vquser@acme.com.test.
This issue is a reopen of https://success.salesforce.com/issues_view?id=a1p30000000eJa0
1. Refresh an existing sandbox
2. Activate it
1. Attempt to change an existing sandbox's username
Instead of using the typical sandbox username syntax:
Use the provided usernames with the prefix to login to the sandbox after refresh.
The prefix can be found in the corresponding email message or by navigating to your sandbox setup section (Setup, click Sandboxes or Data Management | Sandboxes).
Locate the affected sandbox in the list, you should see a Current Org Id value similar to: 00Dn0000000CnGn the prefix can be the last 4 characters of this value in lowercase, or possibly the last 4 + the last three characters if the case insensitive id value was used: 4 character "cngn" or "cngneak" you can determine the 18 character version of the organization id value by inputting it here: http://www.adminbooster.com/tool/15to18
For a sandbox named "test" with the current Org Id above the usernames may be:
firstname.lastname@example.org or email@example.com
If you're still unable to login to the new sandbox please log a case with Salesforce Support and they can provide the required prefix or with your permission, they may be able to manually delete the persisting sandbox causing the unexpected behavior.
This issue has been fixed for new sandbox refreshes. To fully resolve the behavior on any sandboxes that were affected by this known issue during a previous refresh, it may be necessary for Salesforce Support to manually delete the persisting sandbox organization.
If you suspect your sandbox may have be affected, please log a case with Salesforce Support for assistance.
Reported By (255)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.