Fixing Common Errors in Access Manager
Fix common errors in Access Manager related to content assignment and access.
This article applies to districts that use the SSO and Auto-Rostering Access Service. SSO applies to districts that use an SSO portal, district website, or Learning Management System (LMS) to access McGraw Hill digital programs. Auto-Rostering means that account creation, class setup, and roster management are automated through a process handled by your district.
Not sure which Access Service your district uses? Click here to learn more about the four Access Services that we support.
Introduction
This article provides information about how to fix common errors that occur when uploading OneRoster® files to Access Manager or when Access Manager processes your data for use on McGraw Hill platforms. The information about errors applies to both OneRoster® versions 1.0 and 1.1 with the exception of Manifest errors, which only applies to OneRoster® 1.1.
Once your OneRoster® files have been imported, you can see the status of the import and view errors by clicking the Alerts tab on Access Manager. We recommend that you download the error report and use this guide for reference.
After making the necessary changes to resolve each error, re-upload your files on Access Manager. Repeat the process until your upload is successful.
For reference purposes, view the McGraw Hill OneRoster® instructions. The table relation diagrams will help you understand how values in one file affect or relate to other files.
OneRoster® 1.0
OneRoster® 1.1
Alerts
Access Manager alerts fall into three levels of severity. Errors may negatively impact rostering or content distribution. You can view this information on the Alerts page in Access Manager.
This alert indicates an issue with an optional field and will be ignored.
This alert indicates an import error for a required field that prevents the entire affected row from being processed.
This alert indicates an import error for an entire file or batch and prevents all data in that batch from being processed.
Processing Errors
The table below identify the error messages you may encounter on Access Manager. For each error, both the reason for the error and the resolution are provided.
| Error Message | Reason | Resolution |
| The data in your current upload is significantly different than your previous upload. | There are more than 99 changes between data syncs. | To continue with processing the data, click Continue Uploading. To review the data before continuing with the upload, click Cancel. |
Batch Errors
Batch errors occur when Access Manager begins to process your data. If one of these errors occur, the entire process fails. Your action is to fix the errors and resubmit your zip file for processing.
| Error Message | Reason | Resolution |
| This file was not found in the zip file. | One or more required files are missing. The zip file may be:
|
Select the required files and zip them into a single zip file. Do not put the files in a folder and zip the folder. |
File Errors
File errors identify issues with specific files. If a file error occurs, processing the file fails. Your action is to fix the errors and resubmit your zip file for processing.
| Error Message | Reason | Resolution |
| File is not a valid CSV file. May contain invalid or missing quotes or extra columns without headers. | Formatting of one or more .CSV files is incorrect. | Correct the formatting of each .CSV file. Ensure that each file has the correct number of columns with the required headers. The common cause for this error is an extra comma. |
| Column is missing. | A required column is missing in at least one .CSV file. | Ensure that each file has all required columns in each file. |
| Your import has been stopped due to an unusually large amount of change compared to the previous import. | The change threshold has been exceeded. | The change in the file may be intentional or accidental. This is a safety feature that you can override on the Alerts tab. Ignore and override the alert if the change is intentional. If the change was accidental, fix the files as needed. |
Column Errors
Column errors identify issues with columns or the data in specific cells. These errors do not cause a failure when processing the file; however, the affected data fails to process successfully. Depending on the error you encounter, there will likely be issues that negatively impact the user, course, or other. Your action is to fix the errors and resubmit your zip file for processing.
The error now includes the field causing the issue which will make errors easier to spot without downloading the error report. The errors will also be listed in order of severity, so that the errors that could be causing other cascading errors will be listed first.
| Error Message | Reason | Resolution |
| Missing required field. | A required field is missing in one or more files. | Certain fields are required to build account profiles. Locate the indicated required fields within the indicated file type and add the appropriate field value. |
| Field must be unique. | A field value is not unique. | Provide unique field values where required. Look for duplicated values or rows of data accidentally entered twice. |
| Invalid value for format type. | The wrong type of value was used (e.g.: string, integer, enumeration, GUID). | Change the incorrect values to the proper type. |
| Unsupported value. | The value sent for an enumerated field is not supported. | The proper enumeration must be sent. 'Enumeration' denotes a fixed set of values that must be provided for a specific field. Ex: Acceptable values for the enumerated 'role' field in the users .CSV. The role must contain one of the following values: 'teacher' | 'student' | 'guardian' | 'relative' | 'aide' | 'administrator'. Another example is misspelling a supported value. Ex: entering 'unactive' instead of 'inactive'. |
| Referenced key not found. | A referenced sourcedId is not present in the relevant file. | Update the sourcedId value to match the referenced sourcedId value or add the new sourcedId to the appropriate file. Keep in mind, sourcedIds are case sensitive. Ex: an enrollment references a user sourcedId that is not in the users file. |
| Length violation. | The character length maximum is exceeded. | Adjust the length to be 255 or few characters. |
| Unsupported character or formatting. | An unsupported character is used. | Remove all unsupported characters. |
| Only one primary teacher allowed per class. | More than one teacher is designated as the primary teacher for a class. | Each class can have one primary teacher. Find the class with more than one primary teacher listed in the enrollments.csv file and remove the primary designation from all but one teacher. |
| Number of items is not the same. | The number of items indicated does not match number of items referenced. | For corresponding fields, the same number of items should exist in both fields. Ex: the number of subjects specified must equal the number of subjectCodes provided. |
| The matching value does not exist. | The resource does not match the Master Code. | Update the vendorResourcedId value in the file to the correct value or remove it. |
Refer to the PRE K-12 Digital Technical Support self-help site for more articles, documents, and videos on how to use Access Manager.
If additional assistance is needed, contact our Digital Integration Support team at integrationsupport@mheducation.com, call 1-855-315-6417, or contact the team through the chat in Access Manager.