Update 10/27/2025 8:50 AM: The issue has been resolved. myEMU is now available off campus.
10/26 myEMU is accessible on Campus and via VPN. myEMU is not accessible off campus.
Helpdesk, Moodle, and Navigate are still available while myEMU is not accessible. Here are links to use these products:
Service restored at 8:40PM
IT is currently working on restoring services on SISDB.
October 8, 2025, 9:00 pm:
October 1, 2025: IT has reached out to Space Theme support, requesting an update that will allow EMU to use the Space Theme and have a working Grader and File Picker. IT will implement the Space Theme once it has been updated by support.
September 30, 2025: Moodle support traced the File Picker issue to the Space Theme that was implemented in May. IT has reverted to the Boost theme in order to restore File Picker functionality.
September 29, 2025: The Helpdesk began receiving reports about issues using the File Picker and Grader in Moodle. IT staff reached out to Moodle support.
Progress Notes:
10:05 PM all VMWare servers are now available
9:30 PM J1 Web & the reportserver are now available. Other VMs are still recovering
9:25 PM J1 Desktop, myEMU, & PowerFAIDS are now available. J1Web is not currently available.
9:20 PM Progress is being made. But myEMU, J1, and PowerFAIDS are still not available
8:55 PM Maintenance is taking longer than originally planned. MyEMU, J1, and PowerFAIDS are currently unavailable.
Helpdesk, Moodle, and Navigate are all available. Here are links to use these products:
7:24 PM SISDB has been shut down for maintenance
Original outage message:
SISDB will be shut down this evening for a brief period for VMware maintenance starting at 7 PM. All databases hosted on SISDB will be unavailable while the server is down. Users will not be able to use J1, myEMU, PowerFAIDS, and other applications relying on SISDB databases.
Progress Notes:
10 AM There is a registry update script to fix installs for people having difficulty running J1 Desktop
8 AM some computes require reintall of client software.
12:30 AM Wednesday: Cashnet, myEMU, J1 Web, and J1 desktop are all usable. Some additional configuration work is needed on J1 Web for printing. J1 2024.2.0.3 desktop clients will be distributed to EMU computers connected to the school network starting at 6 AM.
Midnight: myEMU available. Cashnet not yet available. Still working on some J1 Web configuration issues.
11:30 myEMU upgrade still in progress. J1 Web is available, J1 desktop is available on RDS and Appstream. Desktop clients will be distributed to current users at 6 AM. If you need it before, then J1 2024.2.0.3 is available for download and installation from EMU applications.
10:15 PM J1 Web is available, J1 Desktop is only available on RDS. Still working on updating J1 to correctly include EMU settings & customizations
9:15 J1 Desktop is available on RDS. Some data was changed in the upgrade. Still working on restoring EMU configuration. MyEMU and J1 Web are not available. CashNET parent portal is available. Access for students is not yet available.
7:30 PM Upgrade in progress, but no additional systems are available
5:30 PM PowerFAIDS is available
4:10 PM Salesforce Integration to J1 has been stopped
Original post:
There is a planned outage of the Student Information System (Jenzabar J1) on September 30th (Tuesday) from 5:00 PM to 6:00 AM on October 1st (Wednesday). myEMU will be upgraded as well. myEMU will not be available from 5:00 PM until 11:00 PM on September 1st.
EMU payment processing (CashNET) depends on J1 and myEMU and will be down during the J1 outage. The PowerFAIDS interface to J1 will not work during the upgrade. Other systems may be affected.
If you use J1 Desktop, please quit J1 before 5 PM on Tuesday. If the Jenzabar client is running during the upgrade, you may need to restart your computer after the upgrade for J1 to work correctly.
EMU must upgrade to J1 before the end of September since Jenzabar will not support J1 2023.3 after September 30th.
Helpdesk, Moodle, and Navigate will all be available while myEMU is down. Here are links to use these products:
SISDB was slow to respond to requests.
Users were unable to log in to PowerFAIDS, J1, myEMU, and various other applications.
UPDATE: The FortiClient is working again now.
The IT department is aware of an issue regarding FortiClient and will work on resolving the issue as soon as possible. You may receive the following error window when trying to connect:
Thank you for your patience as we work towards a resolution.
On July 9th, SISDB will be restarted around 9:45 PM. All J1 sessions will be terminated at that time. myEMU may be unresponsive while SISDB is restarted. Other services relying on SISDB may be disrupted as well.
SISDB was rebooted at 9:46 PM
Update: The problem has been resolved.
The CData package EMU uses to transfer salesforce data to a SQL Server backup database is not working. EMU is currently working with the vendor to resolve this issue. Most end users will not notice the problem. Some J1 data will be out of sync with Salesforce data until the problem is resolved.
Update: This problem was resolved for most modules at 12:30PM. EMU is continuing to have problems with: Transaction Groups on the transfer of payment information from one system to another system.
Inserting new records into Jenzabar is failing on several screens. Jenzabar has been contacted. There is no estimate for recovery time.