Some of the SharePoint services failed to start after Production Patch Maintenance on Sunday. I will be rebooting the server at 9pm on 7/18 to resolve this issue.
-John
Soundnet server rebooted successfully and services have started up.
-John
Some of the SharePoint services failed to start after Production Patch Maintenance on Sunday. I will be rebooting the server at 9pm on 7/18 to resolve this issue.
-John
Soundnet server rebooted successfully and services have started up.
-John
Members of the campus community have reported that they’ve experienced difficulty logging into their Windows computers this morning. Symptoms include either being stuck at the “Welcome” or Ctrl Alt Delete screens. We apologize for the inconvenience and are working to determine the cause of this issue as quickly as possible.
[Updated 5:07 p.m. 6/11/2015] The maintenance has been completed successfully. Internet connectivity is fully restored.
[Original] Thursday evening from 5-5:10 p.m., TS staff will need to perform some urgent maintenance on critical network infrastructure. During this time all outside network services will have no availability.
Thank you for your patience.
Due to the storage migration and expansion we are experiencing issues with Alexandria and selected VM test/development servers. Some files saved after the 9th of August, 2012 on Alexandria may not be accessible until 8 am tomorrow morning due to the server backup restores.
Also, some servers located in the test and development portion of VM, may also not be accessible until further notice, in part caused by storage array issues.
The middle tier on San Juan will be restarted after a configuration update on 2/5/2010 between 5:00 am and 5:30 am PST during the regular maintenance window. The configuration update will help in troubleshooting.
Beginning at 6:00 p.m on Monday, July 27, 2009, Technology Services will deploy Microsoft Office 2007 to opt-in faculty and all staff computers. Office 2007 will be installed on all campus labs and e-classroom computers for the 2009-2010 academic year.
To facilitate a successful installation, staff and faculty opting in to the deployment should “Restart” their computers when leaving work on July 27. PCs should be left on and at the “CTRL+ALT+DEL” login screen. For more information on the deployment, including training and what to expect after deployment, visit our Office 2007 Web pages.
We set the debug level back to 63 to troubleshoot the password sync errors due to AD password policy problem. Here are the commands, executed as oracle on whidbey:
oidctl connect=AS1012P server=odisrv instance=1 configset=1 flags=”port=3636 sslauth=2″ stop
oidctl connect=AS1012P server=odisrv instance=1 configset=1 flags=”port=3636 sslauth=2 debug=63″ start
Gehenna is experiencing a physical memory issue and will be off-line 3/5/09 between 6:45 AM and 7:30 AM for maintenance and troubleshooting. There is no expected impact to campus users as services will be re-routed to another server.
Some users were not getting IP addresses when connecting to Aruba Wireless. This was do to a shortage of IP addresses in DHCP. I expanded the scope on Saturday to make more IP addresses available. This problem should not reoccurr.
We are experiencing reduced round trip times to the internet. This is effecting browsing and downloading of files. I am working with Cisco to find the cause and resolve it as soon as possible. You may notice messages when trying to browse to some websites “unable display page”. We are experiencing unusually heavy data traffic, which has brought these issues to the surface. We will work through the problems and keep you posted.
The redirector web application at http://webmail.ups.edu/redirector was found to fail with a user’s full name containing an apostrophe. Refactoring is underway.
There were reports last night and this morning that user were having problems connecting to webmail. The problem appears to be linked to the Sophos PureMessage software and the timing of the quarantine digest messages and the slow disk array.
We updated our PureMessage configuration to send on digest messages instead of having each server send individual messages. The result being that all the messages hit the mail server and the same time and overwhelmed it with e-mail and client access with the start of the business day.
We are modifying the interval for digest messages from twice a day to once per day and moving the time to 1:30 am each morining.
Over the last few weeks a pattern has appeared in the cpu load on the sophos server: over the course of time the cpu load increases and stays high (
Some user reported this morning the inability to send messages to users. They received a common error,
Final-Recipient: RFC822; username@ups.edu
X-Actual-Recipient: RFC822; username@ups.edu
Action: failed
Status: 5.3.0
(reason: Can’t create output)
This error was the result of poor deactivation of the quotaing system. The quota system had been turned off, but not removed from the fstab file. When the system was rebooted yesterday, the quota system was re-enabled and locked account in excess of their time limit. This issue has been corrected.