Troubleshooting Warning/Failed Messages for Imports in the System Log

The status of scheduled imports can be found in the System Log area, on the left hand side of the page under System Log. The queue activity lists the "Successes," "Warnings," and "Failures" that occurred during scheduled imports.

Go to the System Log

  • Click System Log in the left navigation area.

See cause of any failures

If there are failures listed, and you would like to see what caused these, you can click the Completed tab at the top of the page. Scrolling through the log, you can find queued jobs marked as ‘Failures,’ indicated by a red circle to the left of the entry. The following list includes common error messages and solutions that can accompany a Failure status:

User Integrations

  • 'Validation failed: Login has already been taken' : The Login entered for this user is taken; to correct this, assign a new Login for this user.
  • 'Validation failed: Login can't be blank' : The Login was left blank for this user; please enter a unique Login for the user.
  • 'Validation failed: Password can't be blank' : All users must be assigned a password for their accounts.
  • 'Validation failed: First Name can't be blank' : The user's first name must be provided.
  • 'Validation failed: Last Name can't be blank' : The user's last name must be provided.

Course Integrations

  • 'Validation failed: Course can't be blank' : Please provide a course name to correct this error.
  • Line 936 could not be imported. Error: \'Validation failed: Url has an invalid format\'. Occurs when URL is formatted incorrectly.
  • Line 14029 could not be imported. Error: \'Validation failed: Name is too short (minimum is 1 characters)\'. Occurs when course name is blank.
  • Line 2 could not be imported. Error: \'uninitialized constant Path\'.
  • Line 3 could not be imported. Error: \'wrong constant name evEnt\'.
  • Line 4 could not be imported. Error: \'uninitialized constant LINK\'. Occurs when activity type is not in all lowercase letters during import.

Enrollment Integrations

  • Line 145 could not be imported. Error: \'Validation failed: User can\'t be blank\'. Occurs when importing enrollments for users who are not in the LMS.
  • Line 3752 could not be imported. Error: \'Validation failed: Completed On date can not be null unless status is in-progress, assessment-completed, grading-peers or awaiting-peers, Status must be one of the following \'in-progress or assessment-completed or grading-peers or awaiting-peersorpassed or failed or no-showorincomplete, and dropped\', Occurs when importing completed enrollments without a Completed On date.
  • Course can't be blank. Occurs when importing enrollments with no value for course code or if course does not currently exist in the LMS with the listed course code.

Group Membership Integrations

  • Line 3 could not be imported. Error: \'Validation failed: User can\'t be blank\'.

General Integrations (can apply to any type of Import that has run)

  • 'Validation failed: Code must be unique' : The code that was entered for this line of an import is identical to another line's given code.

NOTE: Course/User/Enrollment Codes must always be unique!

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.