With Sloopy, there is only one thing that can go wrong – we stop receiving the data imports. Common causes include a Windows Task stops running Sloopy, SMTP port 2025 is blocked, or a configuration file has incorrect values. We provide school administrators, School Loop System Administrators, and district IT personnel with tools to monitor data imports. These tools are accessed from each user’s School Loop account.
After three days have passed without a successful import, school administrators will see a data alert in the dashboard on the homepage of their accounts. If you have not configured imports to run automatically over long weekends or school holidays, the alert can be ignored. Otherwise, it is time to troubleshoot Sloopy and, if necessary, contact School Loop for support.
A brief inspection of the import logs can tell you when the most recent imports were received by the School Loop server and whether or not new data was included in the import. In the highlighted section of the sample below, the import received on 4/30 at 4:32 AM contained records for 48 teachers. The number in parenthesis indicates the number of new records in the import.
These logs are available to those with admin accounts. Look for the “Imports” on the school homepage portal.
Sloopy uses SMTP port 2025 to send data from your SIS to our servers. If Sloopy appears to be running correctly, but the import logs show no successful import, you should run the following simple test to see if port 2025 is blocked.
Open the command-line interface window and enter the following:
telnet import.schoolloop.com 2025
If the port is open and properly configured, you should see:
Connected to import.schoolloop.com.
Escape character is '^]'.
220 import.schoolloop.com ESMTP schoolloop.com
If the port is blocked, please check district firewall and server settings.