KNOWN ISSUE: Failure running Report ''Windows Compliance by Bulletin''. Please check the configuration of the query.
|Article:TECH127228|||||Created: 2010-03-25|||||Updated: 2010-03-25|||||Article URL http://www.symantec.com/docs/TECH127228|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Running the Windows Compliance by Bulletin report and getting the following error:
Description: Failure running Report 'Windows Compliance by Bulletin'. Please check the configuration of the query.
Exception Details: Altiris.DataSource.Exceptions.DataSourceRunException: An unexpected SQL error occurred when running the RawSqlDataSource. ---> System.Data.SqlClient.SqlException: Arithmetic overflow error converting float to data type numeric.Note: Sometimes the error is not thrown, but the Compliance Reports show 'No Results'
Patch Management 7.0 SP2
SQL Server 2005
Found an error on line 88 of the Stored Procedure where the script was converting Float to Numeric.
This issue will be resolved in a future release of the Patch Managament Solution.
Work Around: Changed the following line in the stored procedure:
[Compliance] = CAST((CAST(compliance_by_bulletin.Installed AS FLOAT) / CAST(compliance_by_bulletin.Applicable AS FLOAT)) * 100 AS NUMERIC(4,1)),
[Compliance] = CAST((CAST(compliance_by_bulletin.Installed AS FLOAT) / CAST(compliance_by_bulletin.Applicable AS FLOAT)) * 100 AS NUMERIC(6,2)),
This is also changed in the attached scripts that can be run against the 'Symantec_CMDB' Database, with Application ID Credentials logged on, to update the Stored Procedure. There is an updated Stored Procedure for each of the 3 Compliance Reports if needed.Note: The Filter Update schedule will take a little while to run, and during that time you may see 'No Results'.
|Description||Logged in Etrack (Symantec) database|
Article URL http://www.symantec.com/docs/TECH127228