System crashed

The CMS server responded to client connections with the following error:

An error occurred while retrieving the root node of the tree.
Error starting session:
Not enough storage is available to complete the operation.

After clicking okay the this error appeared:

Microsoft JScript runtime error “800a136f”
‘name’ is null or not an object
/upsweb/assignment_list.asp, line 69

At 0945, I:

  1. stopped IIS
  2. stopped PeerSync service
  3. deleted depgraph files
  4. restarted IIS
  5. performed a full publish
  6. restarted PeerSync service

System running okay, publishing is in process. I think the errors were symptomatic and not necessarily accurate; however, I’m logging them here in case they recur.

Cascade Web Unplanned Downtime

Cascade Web came down 3/26 at 4:40pm following a restart of the Apache server to restore the use of Banner and Famis to the camano server which had been running on a backup server since Friday.  Cascade Web was unable to start following this reboot and remained down until 10:30pm. 

Other components of the Application Server including Discoverer and Portal remain down as of 8:15am on 3/27.

Upgraded webserver2 to Ingeniux 5.2.36

I upgraded webserver2 to Ingeniux 5.2.36, the version needed to support the improvements to the Mac client. Barbara and I will test the client tomorrow morning.

Change to security settings:

Due to changes in how the Mac OS handles Windows authentication, the editlivejava directory security no longer is set to Integrated Windows Authentication; instead, it allows access by the Internet Guest Account, IUSR_WEBSERVER2. (The Ingeniux folks are having a hard time working out these settings; nevertheless, Sean feels that some of the problems we’ve had in recent testing of the Mac client may be related to authentication.)

redistributableseditlivejava is the location.

HTML Tidy option included in upgrade

This release comes with a version of HTMLTidy, the use of which is an option during the upgrade. Sean recommends using the report-only mode as well as the option that shows the original cdata block with the proposed changes. The resulting report is located in the upgrade directory (found at the same level as the xml directory in the site folder).