Deploying change set containing community fails with error: "An unknown exception has occurred"
Last updated 2020-02-15 ·Reference W-4282300 ·Reported By 57 users
This issue occurs when deploying a community from an org to another using change sets.
Typically the error thrown when validating the change set in the target org is "An unknown exception has occurred."
Below is a technical explanation of how this issue occurs.
When a Force.com Site for a community is first created in any org, it uses the naming convention "<Community_Name>1". However, if renamed later, the naming convention is changed to "<Community_Name>_C".
This community naming convention mismatch between the community's site component may cause the deployment to fail with the generic error above.
You can verify whether this is the scenario by clicking (View Source) for the community's Network component in the inbound change set. Locate the 'picassoSite' property and if its value ends with "_C" it would indicate the site had been renamed in the source org at some point in time.
To check the naming convention of your Community Site in the target org you can run the following query:
SELECT Id, MasterLabel, Name, SiteType FROM Site WHERE SiteType = 'ChatterNetworkPicasso'
Review the Name field value and check to see if it ends with "1" and if so, it's unlikely the community has been renamed. If the two values described above match then the deployment should be successful.
1. Create a community in your source org.
2. Change the community's name to something else and then change it back to its original naming convention.
3. For the purposes of deployment, create a community in the target org that shares the same naming convention for the community you created in step 1.
4. Create an outbound change set containing your community and all of its dependent components from the source org and upload it to the target org.
5. Attempt to deploy or validate your inbound change set in the target org.
Actual Results: The deployment fails with the following error:
An unknown exception has occurred.
In reviewing the community's Site.com component's Developer name:
- In the source org it may have a developer name of: <Community_Name>_C
- In the target org it may have a syntax of <Community_Name>1
Expected Results: The community change set deployment would succeed without an issue or the error would provide a sufficient description of the Force.com Site naming convention mismatch causing it to fail.
Ensure the community's related Site.com component's developer name matches in both the source and target org. You can do so by temporarily changing and saving your Community's name in both orgs and then reverting the name change back to its original in both the target and source org.
For more details on how to temporarily change your community's name see:
Update Your Community Settings
Once your community has been renamed, re-create and upload and deploy your change set once again.
Reported By (57)
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.