Novell SENTINEL LOG MANAGER 1.0.0.5 - RELEASE NOTES Release Note page 12

Issues Fixed
526143
526119
524994
525099
525075
524606
524453
12 Novell Sentinel Log Manager 1.0.0.5 Release Notes
Description
Issue: The communication links between the Sentinel Log Manager server
and either Tomcat or Collector Managers do not always recover when the
link is dropped temporarily. The link may get dropped temporarily due to
network outage, system load, or a variety of other reasons. If this occurs to
the link with Tomcat, the Web Server becomes unresponsive. If this occurs
to the link with Collector Managers, data from the Collector Managers no
longer flows to the Sentinel Log Manager, although the data is cached on
the Collector Manager file system.
Fixed: The communication links between the Sentinel Log Manager server
and either Tomcat or Collector Managers recovers even when the link is
dropped temporarily.
Issue: Online data storage graphs are not displayed when the nfs archive
location is unshared.
Fixed: The Online data storage graphs are being displayed even if the
archive location is not accessible.
Issue: In Internet Explorer 8 browser, an error message is displayed on
entering a search criteria and hitting enter instead of clicking on Search
button.
Fixed: The search results appear as expected.
Issue: Sentinel Log Manager does not need to listen on port 1099.
Fixed: Sentinel Log Manager does not listen on port 1099.
Issue: On the Firefox browser if you log in to Sentinel Log Manager with
the Administrator or Report Administrator credentials, perform a self edit
and save the user details twice, then by default it takes the Auditor
permission.
Fixed: On performing a self edit of the Administrator or Report
Administrator user accounts, the settings will not change to Auditor
permission.
Issue: The scheduled report is getting deleted when it is edited and invalid
start time is entered.
Fixed: After editing the scheduled report and giving invalid start time, the
scheduled report will not get deleted.
Issue: The Data Archive user interface always reports the following error
when setting the archive location, even if the save succeeded:
Failed Data Archive Configuration Save.
Archive could not be configured, as archive was already configured.
Fixed: No error message is displayed when archive location is set
successfully.