Approximately 4:35pm telephone service to and from the campus was lost. The problem has been identified as a failure in the telephone provider’s network. They are aware of the problem and are working to find resolution. Intra-campus telephone service is operating normally.
January 11, 2009: Cascade Web unavailable (back online at 12:15 pm)
Cascade Web is experiencing some unexpected complications related to yesterday’s Cascade database upgrade. Technology Services staff are working to resolve the issue as quickly as possible.
Cascade Web was brought back up around 12:15 pm.
January 8, 2009: Issues contacting University of Washington
We are currently experiencing problems getting e-mail to the University of Washington and viewing their web site. TS is aware of this problem and working with the University of Washington IT staff to resolve this issue.
The problem has been resolved and tested, as of 10:15am 01/09/2009
Databases unavailable, 1/10/2009
Campus email text:
Saturday, January 10, Technology Services will be performing important updates on our database systems. There will be two groups of outages:
5 AM until 8 PM – Cascade and Cascade Web will be unavailable.
9 AM until Noon – Banner, Famis, Basis, and Millennium will be unavailable.
Email, network files and shares, and other network services will not be impacted.
Details:
Cascade database is switching to new hardware and upgrading to 10g. Administrative toolset is being upgraded to 10g and deployed on new hardware.
Banner, Famis, Basis, and Millennium will be patched to make them compatible with 10g.
December 18, 2008: Alexandria unresponsive
At approximately 5:15 PM the academic file server Alexandria started becoming unresponsive, causing problems with student logins and file access. the server was rebooted at approximately 6 Pm, after attempts to troubleshoot the problem failed because the server’s console became unresponive as well. Service was restored at approximately 6:15 PM.
December 18, 2008: Merlin2 Reboot, 7AM
Merlin2 will be rebooted around 7AM on 12/18 in order to clear up some access issues on the server. We will update this post when it is available once again.
CRM down 12/17/2008 (Update: Back online)
The CRM server was down most of the day, but is now up and functioning again.
Changes were made to the server that are expected to prevent this problem from recurring.
CRM is down, 12/15/2008 (update: back online)
The CRM server is down, so attempting to access CRM results in the Page Not Found error. Service could not be restored Monday afternoon, as expected. A team is continuing to focus on this issue.
Update:
The application is now back online and available for use as of 6:00PM 12/15/2008.
12/13/2008 Blackboard unresponsive
Reportedly at 3 PM Saturday, 12/13/2008 the Backboard server became unresponsive to login requests. At 4 PM, Technology Services staff were notifed by Security Services. The Blackboard services and database were restarted at about 4:20 , which restored service.
Cascade Web was not responding for 3 minutes
Cascade Web was not responding for 3 minutes due to database connection issue. Corrected the issue and now it’s fully operational.
Wireless Outage
The Wireless network has been restored. 12/2/2008 18:05pm
At various locations across campus, we are experiencing a wireless network outage. Those building affected include Wheelock, Wyatt, Field House, South Hall, Trimble, Library (upper floors), and Regester. Our network manager is aware of the issue and working with our vendors to resolve it as soon as possible.
November 24, 2008: Blackboard & Alexandria (Faculty & Student File Share) Down Wednesday 11/26 5:30-6:00am
From 5:30am to 6:00am on Wednesday, November 24th, Blackboard and Alexandria will be offline. Alexandria contains student, faculty, and department file shares which will be unavailable for this short outage.
November 24, 2008: CRM downtime, 6 am – 8 pm
CRM will be down from 6 am – 8 pm on Monday, November 24. The database instance will be patched then moved from Rainier to Grace.
Cascade Batch Processing outage 11/19
Cascade Batch Processing system was down for approximate 30 minutes, from 3:00 pm to 3:30 pm.