Compliance Center 2.1 Rollup Hotfix 011-PSWE221150 Release Notes

Note: You must install both the Web Server (PWE) and Compliance Center Server (PSE) portions of this Hotfix. You may install them in any order as long as both are installed. Before performing the installation, please review the installation instructions in the Readme file for both the PWE and PSE Hotfix components.

Note: This Hotfix is delivered as a compressed file. The file contains both component Hotfixes in separate folders, named and numbered to indicate the Hotfix's purpose and installation target. For information on installing each Hotfix, please consult the Readme file for each Hotfix.

This Hotfix addresses the following issues:

• After installing Hotfix PSWE216040 for the BindView Compliance Center v2.10, the Web Service methods "RetrieveEvaluationResults" and "RetrieveEvaluationResultSummary" in the modules BVExecute.exe and BVExecute.dll may fail to complete correctly. When they do, one of the following errors appears:
• System.Web.Services.Protocols.SoapException: Invalid attempt to read when no data is present.
• System.Web.Services.Protocols.SoapException: ResultHandler::OnRecord()-Requested value Initialized was not found.

This Hotfix corrects the errors, and the methods will now complete correctly.

If a user-created program calls one of these Web Service methods, you must ensure that the program has a proper handler for the "System.Web.Services.Protocols.SoapException" that will occur in the case of a valid error.

Hotfix PSWE221150 adds the new result status "Initialized" to the existing "Pass," "Fail," "NotExecuted," "Ignored," "Indeterminate," and "NotApplicable" result statuses in the result summary section. The "Initialized" status represents an internal failure of the Check Evaluation engine similar to the "NotExecuted" status.

• Previously, when a Data Import Job scope did not resolve to a valid target, the Data Import Job would stop, but not all threads that composed the Job were released properly. This caused an exception message to be written to the computer's Application Log multiple times, and caused a slowdown of all subsequent Data Import Jobs. This Hotfix corrects the error, and all threads of a Data import Job will now be released correctly.
• When the Compliance Center Server runs in the context of a non-Administrator user account, the computer's Application Log contains many copies of the error message "Error storing public key. Reason : System.InvalidOperationException: Couldn't get process information from remote machine." This Hotfix corrects the error, and this error message will no longer be written to the Application Log when running in the context of a non-Administrator account.

Note: This is a rollup Hotfix for the BindView Compliance Center v2.10, which includes the following related Hotfixes that address these issues:

PSWE216040

• This Hotfix allows you to install Technical Standards Packs and Regulatory Views Version 2.10 – March ‘06 Update and later. If you will upgrade your existing Platform and Application Support or Technical Standards Packs to TSP V2.10 – March ’06 Update or later, you must install this Hotfix before performing the upgrade.
• When creating or browsing a collection with a several hundred or more objects, one of the following error messages can appear:
• "Exception of type System.OutOfMemoryException was thrown."
• "Unable to Retrieve Collections"
• "The operation has timed-out."
• "The underlying connection was closed: The request was canceled."
• "The underlying connection was closed: An unexpected error occurred on a receive."

When one of these errors appears, the collection will be created with incomplete data. In addition, in the Windows Task Manager, memory usage for the w3wp.exe process (or the aspnet_wp.exe process if you are using IIS 5.0) will continually increase, even if the BindView Compliance Center is closed. You must stop and restart IIS to release the memory. This Hotfix corrects the error, and collections with large numbers of members can now be created successfully.

• Previously, if a check used a procedure in the repository, and that procedure called another procedure, the first procedure always passed arguments to the second in uppercase, regardless of how they were passed to it. If the second procedure evaluated the arguments using the 'EXACT' operator, the check would fail incorrectly. This Hotfix corrects the error, and arguments will be passed among procedures using the original case.
• The BVExecute command-line tool has been enhanced, and now includes the following Web services:
• Return a list of all Compliance Evaluation Jobs
• Return a list of all Compliance Evaluation Jobs filtered by Collection Name
• Return a list of all Compliance Evaluation Jobs filtered by Policy Name
• Return Job Evaluation Summary
• Return Job Evaluation Results
• When the BVExecute command-line tool was used to evaluate against UNIX machines or to import data for UNIX machines, the evaluation or import would fail, with the following error message:

"System.ApplicationException: Error at Line Number:<line number> . Expected 2 parameter(s) in each line in the file in the format:

UNIX_SERVERS_UID , HOSTMACHINE

Found 1 parameters.

Collection Import was aborted."

This Hotfix corrects the error, and the BVExecute tool can now correctly complete evaluations against and data import for UNIX machines.

PSWE214270

• An updated version of the Compliance Center Collection Import Utility is installed by this Hotfix. The utility allows you to import a list of targets from an external file to create a new collection or update an existing collection.
• A new optional argument has been added to the Collection Import Utility. When the new option, /P[rintFormats], is used, the tool displays the import file format for all Application and Support Packs installed on the Compliance Server.
• When a user imports a file for a UNIX Machines collection using the Import a Collection wizard or the command-line based BindView Collection Import Utility, the collection import will fail and one of the following error messages will appear:

If the Import a Collection wizard is used, the following error message appears:

"The collection could not be imported. Reason: * Unable to get unique field values for the specified target type. Invalid operator for data type. Operator equals add, type equals uniqueidentifier."

If the command-line based BindView Collection Import Utility is used the error message that appears is:

"System.ApplicationException: Error at Line Number: <line number> . Expected 2 parameter(s) in each line in the file in the format:

UNIX_SERVERS_UID , HOSTMACHINE

Found 1 parameters.

Collection Import was aborted."

This Hotfix corrects the error and importing a UNIX Machines collection in the Import a Collection wizard and in the command-line based BindView Collection Import Utility will now complete correctly.

• In the Compliance Center's Import a Collection wizard, the format for the target type "UNIX Machines" is incorrectly displayed as "UNIX_SERVERS_UID," "Machine Name." The correct format is "Machine Name." This Hotfix corrects the format for a UNIX Machines collection in the Import a Collection wizard. Imports performed using the format now correctly specified will successfully complete.
• If a user attempts to import a list of targets into a section of an existing Collection using the Import a Collection wizard in the Compliance Center Web Portal, the following error message appears:

"* Cannot get value because it is DBNull. * Specified cast is not valid."

This Hotfix corrects the error, and it is now possible to import a list of targets into a section of an existing Collection using the Compliance Center Web Portal.

• When a user views the status of a failed Data Import Job, the Compliance Center filters its database of error and exception messages to display only those relevant to the most recent run of the Data Import Job. As a result, the status display can take an excessive amount of time. This Hotfix changes the way error and exception messages are stored, and only the most recent Data Import Job's error and exception messages will be stored. Because of this, display of error and exception messages for the Data Import Job is much faster.
• If a Check is scoped to a specific version of a target type (e.g., Oracle 8i Databases) using the Object Filter drop-down list, and the Check is evaluated against a collection that includes objects of the same type but with a different version (e.g., Oracle 9i databases) but no objects with both the correct type and version, the check's results should display "Not Applicable," but actually displays "Unknown." This Hotfix corrects the error, and the result "Not Applicable" is displayed in this circumstance.
• Previously, users were unable to change the Object Scope in the Object Filter drop-down list on the View Standard page for any user-defined checks based on a custom algorithm. This Hotfix corrects this behavior, and users can now change the object scope for user-defined checks based on a custom algorithm.

PSWE211960

• Under certain circumstances, BindView Compliance Center 2.10 does not import user-defined standards, and the error contains this message:

"The Standard could not be imported.

Reason: Only '=' and '!=" are valid for string comparisons with special values. "

This Hotfix corrects the error, and Compliance Center will now import checks correctly.

• Under certain circumstances, when you install or import some Standards and then attempt to export the same Standards using the Compliance Center UI, the export of some checks fails. This Hotfix corrects this error, and Compliance Center can now export checks correctly.
• In some instances after upgrading the Platform and Application Support, when you create a check using the Check Builder the following error may occur:

"Unable to initialize category tree

* Key already exists, key: <GUID>"

This Hotfix corrects the error, and the Check Builder will now create checks correctly.

PSWE209612

• When the BindView Compliance Center 2.10 imports a standard, checks using the NOT logical operator are not imported correctly. This Hotfix corrects the error, and Compliance Center now imports checks containing the NOT logical operator correctly.
• If a check's value for non-Windows targets contains any "%" variable, such as %servers% or %workstations%, and the Windows Platform Support Pack is not installed, all target outcomes report as "Unknown," and the check evidence contains the text:

"Error executing check algorithm 'BindView.Assessment.CheckAlgorithm.Generic' for target '‹target name›'. Reason Error evaluating predicate Error getting Windows Environment Variables."

This Hotfix corrects the error, and checks will now evaluate correctly for non-Windows targets when % variables are used.

• Under certain circumstances, some check outcomes incorrectly appear as "Unknown," and the check evidence includes the error message:

"Error executing check algorithm 'BindView.Assessment.CheckAlgorithm.Generic' for target '‹target name›'. Reason Error evaluating predicate Error evaluating predicate Object reference not set to an instance of an object."

This Hotfix corrects the error, and check outcomes will not be incorrectly reported as "Unknown."

• If the BindView Compliance Center is processing a Data Import Job, and the top-level collection selected as the scope includes more than one sub-collection, the Data Import Job will fail. The Job Status panel will display the error message:

"Could not resolve scope ‹GUID›. Reason: BindView.Assessment.Data.MissingDataException: No data found for ‹FieldName› on ‹TargetName›"

at BindView.Assessment.Data.TargetDataCacheImpl.GetData(ITargetInstance target, String fieldName, String tableName, String[] segKeyList)

This Hotfix corrects the error, and Data Import Jobs will now complete correctly when the top-level collection selected as the scope includes more than one sub-collection.