Enabling CRM Analytics Results in Internal Server Error

When you enable CRM Analytics in a Salesforce org, the process attempts to create two system users: the Analytics Cloud Integration User and the Analytics Cloud Security User. If this user creation is blocked due to org configuration issues, an Internal Server Error occurs and the enablement process fails.
This article covers the most common causes of this error and how to resolve each one before re-attempting CRM Analytics enablement.

"This feature is not currently enabled for this user"

This message appears when a user does not have the "Manage Analytics" system permission or the "Customize Application" profile permission assigned. To resolve this, assign the default Analytics Admin permission set to a System Administrator. See the Basic Setup  documentation for steps.

Restricted Email Domains

If the org has restricted email domains configured under Setup > Manage Users > Allowed Email Domains, add the 18-character Org ID followed by ".com" to the Allowed Email Domain list. Example: 00D00000000AaaaHHH.com. You can convert a 15-character Org ID to 18 characters using the  Record ID Converter bookmarklet. Note: The 18-character ID is overwritten when a Sandbox is refreshed. You must re-add a unique 18-character ID for the Sandbox after each refresh.

Email Change Verification Disabled

If email change verification is disabled in the org, contact Salesforce Support to unblock the user creation process. Submit a case through the Help & Training portal.

Required or Unique-Required Custom Fields on User Object

If the org has required or unique-required custom fields on the User object, creating the Integration or Security User may fail with an error such as: "duplicate value found: unknown duplicates value on records with id: unknown". To resolve this, temporarily change the field settings to allow the enablement to complete.

Non-Required Unique Fields with a Default Value on User Object

If a unique field with a default value already exists on a user record, this prevents the creation of the required system users. Temporarily make the affected field non-unique until CRM Analytics has been successfully enabled, then restore the unique constraint.

Dependent Picklist on User Object with Mismatched Default Values

If the org has a dependent picklist on the User object with a default value defined, but the controlling picklist does not have a matching default value for that dependency, user creation will fail during Analytics enablement. For example: a controlling picklist with values "AMER", "EMEA", and "APAC", and a dependent picklist with "United States" as the default value — if the controlling picklist has no default, or has a default of "EMEA" that doesn't match the "United States" dependency, the error will occur. To resolve this, either temporarily remove the default value from the dependent picklist, or set a default value on the controlling picklist that matches the dependent picklist's default dependency.

Expired Permission Set License on Integration or Security User

If CRM Analytics is being reactivated and the Integration or Security User has Permission Set Licenses assigned that are no longer available, those users cannot be reactivated during enablement. Remove any expired or unavailable Permission Set Licenses from the Integration and Security Users before re-enabling. See Best Practices for the Analytics Cloud Integration and Security Users  for guidance on Permission Set License assignment.

Dataflows Reference Objects or Fields That Are Inaccessible

If Data Sync is turned on, CRM Analytics enablement examines sfdcDigest nodes in existing scheduled dataflows to check which Salesforce objects and fields are being extracted. If an object or field is not accessible by the Integration User, an error like the following occurs: "Something went wrong while executing the Sync_Objectname node: Object [NameoftheObject] is not available. Verify that the object exists and that the Analytics Cloud Integration User profile has Read level access on the object." If the Analytics > Settings page is available, disable Data Sync before re-enabling CRM Analytics. If the Data Manager is accessible, remove or delete the inaccessible object/field references. If neither is accessible, log a Support case with the internal server error ID and impacted org ID.

Non-System User Assigned to System Analytics Profiles or Licenses

There are two Analytics Cloud Integration User licenses per org. If a regular user is already assigned to one or both of these licenses or to the Integration/Security User profile, the enablement will fail because the license count is exceeded. To resolve this, change the regular user's profile to a non-system profile. This also changes the license assignment.