This document describes the changes introduced by Symantec (tm) Compliance Accelerator 6.0 Service Pack 1 (SP1), Build Rg3227a.

Table of Contents:
1. New or changed features
2. Performance improvements
3. Fixes to known issues

Note:  This file replaces the previous Compliance Accelerator 6.0 SP1, Build Rg3227, as described in the following TechNote:    http://support.veritas.com/docs/285102


1. New or Changed Features
New facility to import and export exception employee details [Ref: A6P003, E519231]
The facilities with which you can transfer configuration data between the Compliance Accelerator database and an XML file have been enhanced to let you import and export the details of exception employees.

In your import/export XML file, you can now add an Exception attribute to the DepartmentMember element to indicate whether the employee is an exception. You can also define the Exception Reviewers for the exception employee, together with other custom roles for the employee, by specifying them in the DepartmentMember element. For example, the following element identifies Hancock as the Exception Reviewer and Williams as the Escalation Reviewer for employee Davis in the Finance department:

<DepartmentMember EmployeeID="Davis" Monitored="true" Exception="true" CustID="Finance"... />
<ExceptionEmployeeRole EmployeeID="Davis" ReviewerID="Hancock" CustID="Finance" ID="110" Name="Exception Reviewer"/>
<ExceptionEmployeeRole EmployeeID="Davis" ReviewerID="Williams" CustID="Finance" Name="Escalation Reviewer"/>
</DepartmentMember>

The following table lists the elements with which you can define Exception and Escalation Reviewers in your import/export file.

 

Element	Attributes	Description	Mandatory
	EmployeeID	The unique ID of the exception employee. This must match the value of the EmployeeID attribute in the element.	Yes
	ReviewerID	The unique ID of the reviewer for this exception	Yes
	CustID	The ID of the department of which this exception is originally a member. This must match the value of the CustID attributes in the and elements.	Yes
	ID, Name	The ID or complete name of the role that you are assigning to the reviewer for this exception	At least one required
	Remove	When set to 1, removes this reviewers role for the exception. The default is 0, which instructs Compliance Accelerator to retain the role assignment.	No
	EmployeeID	The unique ID of the exception employee. This must match the value of the EmployeeID attribute in the element.	Yes
	ReviewerID	The unique ID of the reviewer for this exception.	Yes
	CustID	The ID of the department of which this exception is originally a member. This must match the value of the CustID attributes in the and elements.	Yes
	ID, Name	The ID or complete name of the role that you are assigning to the reviewer for this exception.	At least one required
	Remove	When set to 1, removes this reviewer's role for the exception. The default is 0, which instructs Compliance Accelerator to retain the role assignment.	No

New facility to filter the options in the System Configuration pages [Ref: A6P017]
You can now filter the options in the System Configuration pages of the Compliance Accelerator Web interface by typing a character string in the Filter on box at the top right of the page.


Full support for SQL Server 2005 [Ref: A6P018]
Compliance Accelerator is now fully compatible with SQL Server 2005.


Changes to the search functionality [Ref: A6P024]
This service pack introduces a change to the default behavior of Compliance Accelerator when you enter the criteria for a new search. Previously, if you specified a word for which to search in both the subject lines of messages and the contents of the messages then, by default, Compliance Accelerator would only find messages that met both criteria. For example, messages that contained the specified word in their subject lines, but not in the message content, would not be included in the search results. If you have upgraded to Compliance Accelerator 6.0 SP1 from an earlier version then this continues to be the default behavior. However, in a first-time installation of Compliance Accelerator 6.0 SP1, the application now finds messages that meet one or both of the criteria; it is no longer necessary for both the subject line and the message content to contain the specified word. In effect, Compliance Accelerator now applies an OR condition to the search criteria for the subject and content, and not an AND condition.

1. In the Application Administration column of the Compliance Accelerator Web interface, click System Configuration.

2. In the Settings for box in the System Configuration page, click Search.

3. Click the Edit hyperlink at the right of the Combine subject and content fields with OR row.

4. Check the box in the Value column to apply the OR condition, or uncheck it to apply the AND condition.

5. Click the OK hyperlink at the right of the row to save the change.

6. Click OK at the bottom of the page to return to the home page.

7. Restart the Enterprise Vault Accelerator Manager Service.

Product rebranding [Ref: ACP026, ACP029]
This is the first version of Compliance Accelerator to be branded as a Symantec product rather than a Veritas product. In addition to changes to the Web interface and documentation, note that the reports you can generate with Compliance Accelerator are now branded with the Symantec logo.


Usability improvement to the New Search page [Ref: A6P031]
In the New Search page of the Compliance Accelerator Web interface, the box in which you can type email addresses for which to search now has the label Freeform email addresses (independent of Departments) to better identify its purpose.


Changes to scheduled searches in personal folders [Ref: A6P036]
When creating a scheduled search in a personal folder, you can no longer choose the <Decide later> option in the Where do you want save the results box. Similarly, if you do choose <Decide later> for an immediate search, you cannot change the search type from Immediate or choose a scheduled search as the template on which to base the new search.


2. Performance Improvements
Performance improvement when using guaranteed sampling to capture messages [Ref: A6P002]
With guaranteed sampling, Compliance Accelerator captures all messages for every monitored employee throughout the day. Then, after midnight, it picks a random sample from each employee's messages, based on his or her monitoring percentage, and adds them to the department review set. Customers with a large number of departments and monitored employees may have experienced a performance issue where, because of the very large number of messages processed, Compliance Accelerator captured randomly sampled messages but failed to add them to the review set.

This issue has been fixed, and customers should notice an improvement in the performance of guaranteed sampling. Note the following:

Performance when bulk-marking messages [Ref: A6P007, E540252, A6P027]
For operations that are susceptible to SQL deadlocks, such as assigning review status marks to a large number of messages simultaneously, Compliance Accelerator now detects any deadlock conditions and retries the operations until they are successful.


Performance improvement when creating searches in personal folders [Ref: A6P008]
When defining the criteria for a new search to find messages to add to a personal folder, you may have experienced very sluggish performance in the New Search page of the Compliance Accelerator Web interface.  This has been fixed.


Improvements to search performance [Ref: A6P021, A6P045]
To improve search performance, Compliance Accelerator now archives the records of old searches in a separate SQL table (tblSearchVaultsArchived) from that in which active searches are stored (tblSearchVault). This helps to keep the tblSearchVault table as small as possible, thereby minimizing the amount of time that Compliance Accelerator takes to retrieve data from it.

You can set various configuration options in Compliance Accelerator to automate the deletion of old records from the tblSearchVaultsArchived table. By enabling the deletion of these records, you can minimize the time that Compliance Accelerator takes to open and display old searches. However, the searches no longer display the details of each vault searched. Instead, the search page displays the message "Vault search results have been deleted from the system".


To control the scheduled deletion of old records from the tblSearchVaultsArchived table
1. In the Application Administration column of the Compliance Accelerator home page, click System Configuration.
2. In the Settings for box in the System Configuration page, click Search.
3. Set the following options as required:

 

Use this option	To do this	Default Value
Enable Search Vaults Items deletion	Specify whether to delete old records from the tblSearchVaultsArchived table. Compliance Accelerator checks the last-modified dates of the records to determine whether they are old or not. If you choose to delete the records, you can configure how Compliance Accelerator does this by setting the following configuration options.	Disabled
Search vaults deletion synchronisation interval (mins)	Set the frequency in minutes with which to delete old records from the tblSearchVaultsArchived table.	720
Search vaults deletion retention period (days)	Specify how long to keep records in the tblSearchVaultsArchived table. The maximum value is 3650 days (10 years). The default value of 0 means that records are kept indefinitely.	0
Search vaults deletion run time	Set the time of day at which to search the tblSearchVaultsArchived table for old records.	23:59

4. If you change the setting for any option, restart the Enterprise Vault Accelerator Manager Service to put it into effect.


Changes to System Configuration options to improve performance [Ref: A6P051]
This service pack introduces some changes to the default values for a number of System Configuration options, which are designed to improve system performance. To access these options, click System Configuration in the Application Administration column of the Compliance Accelerator Web interface.

 

Category	Option	New Default	Notes
Employee Synchronization	Number of synchronization threads	1	Specifies the number of threads committed to synchronizing employee profiles with the corresponding Active Directory accounts. Formerly 5. The reduction in value helps to minimize the impact of Active Directory synchronization on the Compliance Accelerator database server.
Employee Synchronization	Synchronization interval (hours)	8	Specifies the frequency in hours with which Compliance Accelerator synchronizes employee profiles with the corresponding Active Directory accounts. Formerly 4. The increase in value helps to minimize the impact of Active Directory synchronization on the Compliance Accelerator database server. As a result, however, Compliance Accelerator may now take up to eight hours to synchronize employee properties with the corresponding Active Directory attributes.
Random Capture	Stale config timeout (mins)	60	Specifies the frequency in minutes with which the Journal Connector synchronizes with the Compliance Accelerator database. Formerly 3. The increase in value should greatly reduce the load on the database server, but changes to department sampling may now take slightly longer to take effect.
Vault Directory Synchronization	Synchronize thread checking period (sec)	21600	New option with which you can specify the frequency in seconds with which Compliance Accelerator synchronizes with the Enterprise Vault archives. The default value causes Compliance Accelerator to take up to six hours to recognize new archives, vault stores, and retention categories.

If you are upgrading to Compliance Accelerator 6.0 SP1 from an earlier version of the software, and you previously changed the value of any of these options, the upgrade process respects the values that you have set. However, Symantec recommends that you revert to the new default values.


General performance improvements [Ref: A6P015, A6P020, A6P022, A6P030]
This service pack introduces a number of Compliance Accelerator enhancements that improve response times, reduce CPU usage, and eliminate memory leaks or out-of-memory exceptions when you do the following:

See also, the Read Me First file:  http://support.veritas.com/docs/283656 for other ways to improve the performance of Compliance Accelerator.


3. Fixes to known issues
Access to large number of departments caused system failure [Ref: A6P005, E514911]
If you gave users access to a large number of Compliance Accelerator departments (400 or more), those users may have been unable to access some pages of the Compliance Accelerator Web interface, such as the Review Items page.  This has now been fixed.


Incorrect Sampled and Hits counts for scheduled searches in Department Searches page [Ref: A6P009]
The Department Searches page of the Compliance Accelerator Web interface, which you can access by clicking the Searches link in the home page of a department, provides summary details of the searches that you have created for that department. In the case of scheduled searches, however, the page did not show the correct number of messages in the Hits and Sampled columns. The values shown did not reflect the hits and sampled counts of the last run of the search.  This has been fixed.


Failure to create a Compliance Accelerator customer after upgrading from version 5.1 [Ref: A6P010]
After upgrading from Compliance Accelerator 5.1 to 6.0, you may have encountered the following error messages if you tried to create a Compliance Accelerator customer using an existing database:

Event Type: Error
Event Source: EV Compliance Accelerator
Event Category: Server
Event ID: 41989
Error:
APP Undefined - Error Executing : c:\program files\kvs\business accelerator - compliance\AcceleratorDataUpdateV6.sql
Line: 231
Failed to Execute the following command:
if not exists (select * from tblintRolePermission where RoleID = 210 and PermissionID = 265)
insert into tblintRolePermission(RoleID, PermissionID) values (210,265)

Event Type: Error
Event Source: EV Compliance Accelerator
Event Category: Server
Event ID: 41990
Error:
APP Undefined - Failed to update database
Description:
System.Exception: System.Data.SqlClient.SqlException: INSERT statement conflicted with COLUMN FOREIGN KEY constraint
'FK_tblintRolePermission_tblRole'. The conflict occurred in database 'EVAccelerator', table 'tblRole', column 'RoleID'.
The statement has been terminated.

This has been fixed. Note: After performing a database upgrade, you must manually assign the following permissions to any role with which you want to associate them:

 

This permission	Lets you
Manage Department Users	Implement Chinese Walls security by assigning the role of Department User to selected employees.
Manage Reviewing Comments	Add, modify, and delete predefined comments that reviewers can choose to apply to the messages they are reviewing.

Wrong department properties updated with XML dataload facility [Ref: A6P013]
If you used the dataload facility to import the properties of a department from an XML file then, if you failed to specify values for the Disable Monitoring and Monitoring Policy Percentages attributes in the XML file, Compliance Accelerator would set them to the default values ("true" and "2%" respectively) instead of respecting any existing values that you had set for the attributes.  This has been fixed. Compliance Accelerator now preserves any values that you set previously.


Fixes to the "All Departments" link in the home page of the Compliance Accelerator Web interface [Ref: A6P014]

Prefetch cache fixes [Ref: A6P019]
This service pack fixes the following issues with the prefetch cache mechanism.

Incorrect warnings in Event Viewer when running scheduled searches [Ref: A6P023, E505898]
Each time you ran a scheduled search, an incorrect warning message like the one below may have been added to the Application log in Event Viewer:

SQL Server Scheduled Job '<schedule_name>' (0x62A00D0A54313F4A92788FDF52622E4D) -
Status: Failed - Invoked on: 2005-11-18 11:08:21 -
Message: The job failed. JobManager tried to run a non-existant step (3) for job <schedule_name>.

This has been fixed.


No page breaks between messages when printing multiple messages from the Review Items page [Ref: A6P025]
If you used the facility in the Review Items page to view a printable version of multiple messages, and then sent those messages for printing, Compliance Accelerator failed to add page breaks between each one.  This has been fixed.


Permission histories not updated reliably [Ref: A6P035]
If you changed the permissions for many thousands of users at a time when loading configuration data into the Compliance Accelerator database from an XML file, it was necessary to restart the Compliance Accelerator server several times before all the permission histories for those users were up-to-date. Note: The permissions themselves were applied immediately; only the permission history for each user would briefly be out-of-date.  This has been fixed.


Department owners could be de-assigned from User Admin role in their departments [Ref: A6P043]
In the Role Assignment page for a department, it was possible to remove the User Admin role from the owner of the department.  This has been fixed. When you select the department owner in the Role Assignment page, the User Admin role is now read-only.


Reviewers without Apply Bulk Review Action permission could mark multiple messages simultaneously [Ref: A6P044]
In List View mode in the Review Items page, users who had the Apply Review Action permission but not the Apply Bulk Review Action permission could still apply an action status mark to more than one message at a time.  This has been fixed. Reviewers who try to mark multiple messages simultaneously are now warned that they can mark single messages only.


Incorrect permission history in Employee Properties page [Ref: A6P048]
The Employee Properties page of the Compliance Accelerator Web interface, which lets you enter the details of a new employee or modify the details of an existing one, did not show the correct permission history for that employee.  This has been fixed.


Membership of a group did not give employees access to folders associated with the group [Ref: A6P049]
Employees who should have been able to access personal folders because of their membership of an employee group were nonetheless unable to do so.
This behavior has been partially corrected. Those employees who acquire the permission to create folders through their membership of an employee group can now access those folders without problem. On the other hand, it is still the case that assigning a folder role such as Review to an employee group does not give the group members automatic access to a folder. To work around this problem, assign the required role to the individual employees rather than the group.


Inability to generate more than one report simultaneously [Ref: A6P050]
If you tried to generate a new report while Compliance Accelerator was still processing an earlier one, Compliance Accelerator failed to generate the new report and sent the following messages to the event log:

WARNING: Crystal Reports

A Crystal Reports job failed because a free license could not be obtained in the time allocated. More licenses can be purchased direct from Crystal Decisions or through the Crystal Decisions Online Store.
ERROR: EV Compliance Accelerator

Error:
An error occurred during the initialisation of report

Description:
CrystalDecisions.CrystalReports.Engine.OutOfLicenseException: A Crystal Reports job failed because a free license could not be obtained in the time allocated. More licenses can be purchased direct from Crystal Decisions or through the Crystal Decisions Online Store.
at _._N(String _-, EngineExceptionErrorID _0)
at CheckLicenseStatus()
at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String reportName, OpenReportMethod openMethod, Int16 parentJob)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String reportName)
at KVS.Accelerator.Reports.Engine.Document(String ReportName, String P1, String P2, ArrayList P3)
ERROR: EV Compliance Accelerator

Error:
An error occurred saving the report

Description:
System.NullReferenceException: Object reference not set to an instance of an object.
at KVS.Accelerator.Reports.Engine.SaveCrystalReport()

This has been fixed. Compliance Accelerator now adds the reports to a queue and processes them when resource become available.