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
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.
Users should logout out of J1 desktop at the end of their workday on January 7, 2025. This will allow Jenzabar to Patch our servers for changes. Maintenance is to be performed between 7 PM on January 7th and 4 AM on January 8th.
If users forget to log out before the maintenance begins, their J1 Sessions will be kicked out. Any unsaved transactions will be lost.
Update:
There is a planned outage of the Student Information System (Jenzabar J1) on November 12th (Tuesday) from 5:00 PM to 3:00 AM on November 13th (Wednesday). myEMU will not be upgraded, but because the myEMU portal relies on Jenzabar, it will not be available from 5:00 PM until 9:00 PM on November 12th.
This outage is for J1 and myEMU. 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 should not be affected.
If you use J1 Desktop, please quit J1 before 5 PM 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 the year since Jenzabar will not support the old version in 2025.
Helpdesk, Moodle, and Navigate will all be available while myEMU is down. Here are links to use these products:
11:43 am: Internet service has been restored.
We are currently working with our vendor to get this back up and running as soon as we can. Please check back for updates.
Update: our Moodle server should be working again. Please e-mail helpdesk@emu.edu if you still have trouble. Thanks!
Moodle is currently down due to what appears to be a DNS issue. Please standby for updates. We apologize for the inconvenience.
Updates: 5:20 PM backup of database completed
6 PM Jenzabar indicates work is complete
The most noticeable activity is on J1 Web there will be an IIS restart. People using J1 Web will lose connections and the ability to communicate with the J1 Web server during the upgrade.
On myEMU (different than J1 Web), Web Application Services (WAS) and Client Application services will be stopped and restarted. myEMU should remain available but some data will either not be refreshed or be unavailable while the services are restarted.
Patch 7 will be available to any desktop users that want it on 2/1/2024. The patch affects 1098 and 1099 forms so folks in the business office are the people that need it.
Sorry for the short notice.
Progress Updates:
There is a planned outage of the Student Information System (Jenzabar J1) on March 5th (Tuesday of Spring Break) from 5:00 PM to 3:00 AM on March 6th. myEMU will also be upgraded and will not be available 5:00 PM until 5:30PM and from 7:30PM and until 9:30PM on March 5th.
This outage is for J1 and myEMU. EMU payment processing (CashNET) is dependent on J1 and myEMU and will be down some during the J1 outage. The PowerFAIDS interface to J1 will not work during the upgrade. Other systems should not be affected.
If you use J1 Desktop, please quit J1 before leaving the previous week. If the client is running during the upgrade, you may need to restart your computer after the upgrade for J1 to work correctly.
We are updating to J1 2023.2 at this time because the J1 2022.2 version we are currently running is nearing its end of life.