[RESOLVED] PeopleSoft Campus and myPugetSound are back up and running.
______________
Users have reported that they are experiencing issues logging into or running processes in myPugetSound and PeopleSoft Campus.
We apologize for the inconvenience and are working to resolve the issue as quickly as possible. Please contact the Technology Service Desk at servicedesk@pugetsound.edu or 253-879-8585 if you have any questions.
This is an announcement from Technology Services about an upcoming scheduled PeopleSoft outage. Please see details below. We will add to this post when updates become available.
Please contact TS-PMO@pugetsound.edu if you have any questions
[Update 06/22/2017 6:00 PM] Our scheduled maintenance has been completed successfully.
[Original] Pre-Production Server Patch Maintenance is scheduled for Thursday, 06/22/2017, from 9 am. to 6 pm. This should NOT affect any production services such as email, individual and departmental file shares, database applications, or web services (Moodle, vDesk, etc.). If an issue is encountered, please contact the Technology Service Desk at 253.879.8585 or servicedesk@pugetsound.edu.
Technology Services schedules regular maintenance windows to ensure a secure, reliable computing environment. Thank you for your patience as we conduct this important work!
Our backup internet provider will be doing maintenance on 6/30/2017 from approximately 9 AM to 5 PM. This should not affect normal internet for the campus as this is only our backup internet link. However, if you are experiencing issues during this time please contact the Service Desk.
Thank you!
There was a brief K20 internet outage that lasted about 10 minutes this morning from 4:50 am to 5:00 am. Everything appears to be restored and K20 our main internet provider is investigating the cause of the outage. We will update this post if there is any additional information.
[update 06/03/2017 1:15 PM] File services have been restored.
[original] We’re currently experiencing issues with the merlin2/stafffiles file server. We’re looking into the issue and expect to have it resolved shortly.