After the nightly integration sync occurs, an email notification will be sent to the Pearson SIS Admin as well as to the district tech contact(s) identified during setup.
This notification reports on the status of the data transfer from our partner, Elevate Data Sync (EDS), to our LMS. If the sync has completed successfully, the email notification will contain the following information:
Subject: OneRoster SIS Integration Success - Please do not reply to this email.
From: Pearson Connexus <notifications@connexus.com>
Email body: Process for Connexus EMS and your SIS integration was successful
Errors and troubleshooting
If the sync has failed, the email notification will contain the following information instead:
Subject: OneRoster SIS Integration Failure - Please do not reply to this email.
From: Pearson Connexus <notifications@connexus.com>
The body of the email will contain more information about the processing failure, including details about specific errors. A failure at this step may result from improperly formatted data from your SIS, errors in the data during processing within EDS, API connection errors, or other issues that require investigation. If you’re uncertain what an error means or unable to find an error on your end, please contact your District Success Partner (DSP), who will connect with the Pearson SIS Admin for further information and next steps. Next steps will typically involve written communication in emails but may require a meeting if an issue requires real-time coordination.
Missing email notification
If you didn’t receive either the Success or Failure email notification overnight, double-check that it wasn’t caught by spam filtering or message handling rules. If after checking those you still don’t have the email, reach out to your DSP. Your DSP and the Pearson SIS Admin will determine if the correct email addresses are in the notification list and whether there was a failure in the process before the point where an email should have been generated.
Example errors and solutions
IDs and usernames in these examples have been replaced with placeholder “[…]”. Actual email notifications will contain information that can be used for troubleshooting instead of these placeholders.
Any student information contained in these email notifications is limited to the unique ID assigned in your SIS and can’t be used to identify a student without access to your SIS and/or to the Pearson LMS.
This isn’t an exhaustive sampling of possible errors. If an error reported in the log is similar to one of the examples below, the solution and next steps will likely also be similar. If you’re unable to determine if the error is similar or if you need further guidance on next steps, reach out to your DSP for help.
Example 1
Email body:
Process for Connexus EMS and your SIS integration was not successful. Please see below errors and correct the errors for the next process run to be successful. Please note users/courses/enrollments data will not be processed if Org file data has no valid entry.
User creation failed for user with username '[…]'. Error : Unable to create user […]. Duplicate domain/username: […]/[…]
Possible cause: The username field typically contains the student or teacher’s email address unless a different username is used within your SIS. This error may be caused by multiple users in the SIS having the same username (or email address, if that’s the username used by your SIS).
Next steps: Double-check the user(s) in your SIS whose usernames were listed in the error notification. If you’re unable to identify or resolve the issue, contact your SIS Vendor for support.
Example 2
Email body:
Process for Connexus EMS and your SIS integration was not successful. Please see below errors and correct the errors for the next process run to be successful. Please note users/courses/enrollments data will not be processed if Org file data has no valid entry.
Validation failed for row with SourceId '[…]' for columnName 'UserSourcedId' in Enrollment file due to : UserDependencyFailed
Possible cause: The user ID associated with the enrollment in your SIS data doesn’t match any of the users from your SIS. This can sometimes be caused by working with data that has leading zeroes or by mismatches while pulling custom reports out of your SIS to send to Pearson in CSV files.
Next steps: Check that the user IDs in the enrollment data match the formatting of the user IDs in your user data. Also check if the specific user in the error log is formatted correctly and included in the user data.
Example 3
Email body:
Process for Connexus EMS and your SIS integration was not successful. Please see below errors and correct the errors for the next process run to be successful. Please note users/courses/enrollments data will not be processed if Org file data has no valid entry.
Enrollment creation failed for source Id '[…]'. Error : Duplicate enrollment
Possible cause: The student or teacher is already enrolled in this course in PCx, but the enrollment doesn’t have an External ID. This can happen if the student or teacher was added to the class manually before the integration had a chance to run.
Next steps: Use the source Id to determine which student and which course this is. On the PCx side, find that course and check if the student is there with a blank “Enrollment External ID”. If yes, edit the enrollment to add the source ID from the email notification into the Enrollment External ID field. Contact your DSP if you can’t edit this yourself.
Example 4
Email body:
Process for Connexus EMS and your SIS integration was not successful. Please see below errors and correct the errors for the next process run to be successful. Please note users/courses/enrollments data will not be processed if Org file data has no valid entry.
Parsing failed for row '1563' in User file for columnName 'orgSourcedIds'. Please check the length or enter correct value
Validation failed for row with SourceId '[…]' for columnName 'metadata.pearson.domainId' in Org file due to : InvalidFieldValue
Possible cause: The external ID in PCx doesn’t match the School Number in the SIS.
Next steps: Update the external ID in PCx for your schools or contact DSP for help making that change.
Example 5
Email body:
Following files did not get uploaded.
- orgs.csv does not have the required field values.
- users.csv does not contain headers in the correct format.
- categories.csv - The given key was not present in the dictionary.
Possible cause: Configuration issues within Elevate Data Sync
Next steps: Contact DSP for Pearson SIS Admin to resolve