Third Party Integration - SIS Integration

Instructions that include troubleshooting steps to help determine where potential issues may reside in the data exchange
  • Testing Accelerate Queries Directly on the Connect Server

    Overview This article can help the SS&E Administrator/local IT/organization's SIS Integration data lead determine whether there are issues in the Accelerate query itself or whether there are issues in the Connect Job configuration. If the query runs successfully by itself in Drill, this means that the Connect2 task settings need additional troubleshooting in the Connec...

  • The Connect Job is Failing with Schema [[dfs, root]] is not valid

    Reported Issue Connect2 is failing with: java.lang.Exception: VALIDATION ERROR: Schema [[dfs, root]] is not valid with respect to either root schema or current default schema. Current default schema: dfs Due to the error, the Connect job is not running and all data feeds are out of date. From SS&E > Admin > Advanced Administration > External Logging > The Connect2 Appl...

  • How to clear space on the Connect Server C: drive

      **This article only applies to institutions that send CSV files and are using Drill** If the C: drive on the Connect server needs space cleared up, all files can be deleted from the C:\tmp\drill\profiles directory. In addition, this can also be done by updating the file found at C:\Aviso\Connect2\Connect2.ps1 so that the system manages this and clears out files that a...

  • How to Remove a Data Feed from the SIS Import Process

    In order to exclude a data feed from the SIS Import job, from SIS Integration Administration -> Datafeeds, scroll to the data feed you wish to exclude, select the Name and uncheck "Enabled". Enabled data feeds will be executed during the SIS Import Job. Disabled data feeds will NOT be executed during the SIS Import Job. The data feed will still appear in the Connect Jo...

  • Data Feed Actions

    Overview SS&E Enterprise supports various data feeds. Each data feed, while focused on specific types of information, supports various actions (Insert, Update, or Delete). While all data feeds support Insert and Update, only a subset support deletion. Below find a description of the action type, as well as which data feeds support these actions. Action Type Insert : Thi...

  • Data Stream Out of Date Troubleshooting

    Overview Who is notified? When SS&E detects that a data extract(s) is out of date, the system will notify SS&E Administrators by displaying a warning in the SS&E Administration and notifying the SIS Health Notification email address set in Institution Administration. What does this mean? When a data feed(s) is out of date, it means that data is delayed and can explain w...

  • Drill Service Troubleshooting

    Overview For institutions that use Drill to extract data from the SIS, the user/password assigned to the Drill service must be active and the service itself must be running properly. For example: If the user password expires, this will prevent current ALL data from importing into SS&E. If some data streams are executing, and the error shows "Connection refused", there m...

  • Extract/Transfer Phase Troubleshooting (data stream out of date)

    1. The first place to check for Connector issues is in Administration -> Advanced -> External Logging, filtering by Log Level "Error".  If there are no errors, check for issues that display when searching by Info or other log levels. If the information isn't helpful, proceed with the following steps. 2. If every data stream is out of date: Connect 1: Remote int...

  • Import Error Message "Group/Role null not found"

    Import Error message "Group/Role null not found" indicates that the role included on the Person record in the person.json data extract is not being found in SS&E. Most likely, the reason for this is that the role is case-sensitive and does not match the role assigned in Role Administration. In order to resolve this, the imported role on the person data feed must have an...

  • Informer Report Specification

    The purpose of this article is to document the default Informer Report specifications for institutions using the Informer reporting solution as an export option from their SIS. This specification is built specifically for Accelerate file formats. If your institution is not using Accelerate, please contact your SS&E representative.   NOTE: This article is a working draft...

  • Phone Numbers are Missing or Incorrect

    Overview Click here to see how Student Success & Engagement determines which staff phone number display as their single "Preferred" phone number. Troubleshooting Phone Data By default, phone numbers import into SS&E from the SIS on the Person Phone data feed. Upon implementation, the Person Phone data extract definitions are usually set up so that for staff members, th...

  • SIS Data Deletion Integration Configuration and Troubleshooting

    Overview The SIS Data Deletion configuration is an integral part of the SIS Import Job for data streams that are set to synchronize data deletions from the SIS with SS&E. Click here for a complete list of data feeds. "Delete = Yes" means that the data feed supports SIS Data Deletion integration. A few data feeds integrate data deletion by a different method. These data...

  • SIS Integration Troubleshooting Guide

    Overview There are different situations where troubleshooting the SIS integration with Student Success & Engagement is required, such as: The SIS data does not display in SS&E as expected The SIS data appears to be delayed in SS&E The SIS data is missing from SS&E The SIS data displays in SS&E yet it does not match the data found in the SIS In all cases, the initial t...

  • SIS Import Error "Could not parse file:"

    Overview To view Import Errors in SIS Integration Administration, click here. Import Error "Could not parse file: " means that there is an issue in the source data/csv file that is causing the data extract (Json file) to be invalid or missing from the SIS Import Job process, preventing "fresh" data from importing into SS&E. New data will not import from the SIS into S...

  • SIS Integration Webinar Part I - Introduction and Technical Overview

  • SIS Import Validation

    Overview For an overview of the SIS Data Import Process, click here. The above article describes how data moves between the SIS system via the Connect Job into SS&E. The Connect job processes the SIS data and generates data extract (Json) files that are used to import data into SS&E. Import errors occur during the import job that runs after the Connect job has processe...

  • SIS Integration Webinar Part II - Data Import Troubleshooting

  • SIS Integration Webinar Part III - Data Extract and Data Transfer Troubleshooting

  • Connect Server Update to Java 8

    If prompted to update Java and run the Connector on Java 8, please reference the following steps that describe how to install and uninstall Amazon Corretto 8 on a host or container running the Windows 7 or later operating system. https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/windows-7-install.html    

  • Connect SFTP Auto-Updates Deployment Guide

    In December of 2020, improvements were made to the Connect product utilized during the SIS data import process. These improvements converted the Connector from a web service to a scheduled job running on the Connect server. Removing dependencies on Apache Tomcat and HTTP was a main motivation for these changes. Prior to this change, issues with Tomcat crashes and the...

  • Connect Job - SS&E External Logging

    Connect Job Overview Modern versions of Connect include an auto-updater that automatically updates the Connector and direct access to view logging from within Student Success & Engagement. This allows SS&E Administrators to view the most recent Connect Job Application Log. As soon as the Connect Job completes, the most recent Connect2 Application Log is transfered fro...

  • Validation Error: Schema [[dfs, root]] is not valid with respect to either root schema or current default schema.

    Reported Issue All Data Feeds are Out of Date and External Logging shows the same schema error on every data feed. After googling the error message, it appears to be related to something that is causing the drill service to be unable to write files to S3. Error Message Details VALIDATION ERROR: Schema [[dfs, root]] is not valid with respect to either root schema or curr...