Some of the Salesforce for Outlook sync error messages have changed over time. This article contains the old error message, the new error message if it is changing, and an explanation of the error if the message is not self explanatory.
Legacy Error Message |
Current Error Message |
Explanation |
|---|---|---|
| An event can't last longer than 14 days. | You can't create an Outlook event which spans more than 14 days, and sync it. That is an Outlook system limitation. | |
| Based on the frequency you selected, the end date cannot be after MM/DD/YYYY.: End Date | There is a maximum end date for any recurring event series in Salesforce. This error message is displayed if you exceed the max end date. | |
| Single events cannot have detail commands. | This event can't sync because it was converted into a recurring series in Outlook. To sync the series, delete and replace the event with a new recurring series in Outlook. | Please refer to Salesforce For Outlook - Sync Error "This event can't sync because it was converted into a recurring series in Outlook" for more information. |
| The end date of a recurring series cannot be set to a date in the past.: End Date | This error will happen when you have a recurring series in Outlook which is already synced to Salesforce and the end date of the series in Outlook is modified such that it is in the past. This change is allowed in Outlook but not in Salesforce. | |
| The field RecurrenceStartDateTime is invalid | This recurring series can't sync because it was converted into a non-recurring event in Outlook. To sync the event, delete and replace the recurring series with a new non-recurring event in Outlook. | |
| You cannot modify the start date of a recurrence series that has already started: Start Date. | This error will happen when you have a recurring series in Outlook which is already synced to Salesforce and change the start date after the series has started. This change is allowed in Outlook but not in Salesforce. Please see Start dates for recurring series in Outlook for further explanation. | |
| Unable to sync. Review the appropriate log for details. A sync error occurred. Review the appropriate log for details. | The Outlook event can't find the Salesforce event that it was syncing with. Delete and recreate the event to continue syncing it. | |
| Unable to sync. Review the appropriate log for details. Nullable object must have a value. | This event can't sync because it was converted into a recurring series in Outlook. To sync the series, delete and replace the event with a new recurring series in Outlook. | |
| Tasks between Salesforce and Outlook include matching subjects and due dates. To sync tasks successfully, verify that the following records include subjects and due dates that are unique between Salesforce and Outlook. Salesforce ID: 18-digit. | This happens when one Salesforce record matches multiple records in Outlook. The user would need to change the subject and due date in either Salesforce or Outlook to something unique and then sync again. It would be best to change in Salesforce as there would only be one record there. |
Considerations for Using Events in Lightning Experience
Considerations for Using Events and Calendars in Salesforce Classic
Salesforce Error 'Invalid Cross Reference Id' When Updating EmailMessageRelation Records
000387866

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.