Cloned Patch Compliance report(s) displays "Unknown Error"

Products

• IT Management Suite

Issue/Introduction

After upgrading to ITMS 8.5 RU1 many previously cloned reports cannot be edited or deleted.  When attempting to view the cloned patch compliance reports in the Symantec Management Platform (SMP) a message "Unknown Error" is returned.

Note: Default compliance reports for Patch Management Solution for Windows are listed in the SMP Console under:

Reports > All Reports > Software > Patch Management > Compliance > Windows

The following message appears in the SMP logs when attempting to view the cloned reports: 

"Failed to load parameter from xml (skipped):
<parameter><name>FilterCollection</name><description></description><required>false</required><nullable>true</nullable><parameterTypeGuid>40d6ba82-776b-4d89-b1a8-8322b6ca64f5</parameterTypeGuid><testValue></testValue><defaultValue>01024956-1000-4cdb-b452-7db0cff541b6</defaultValue><order>10</order><valueProvider classGuid="891d9058-6b53-4a59-8aff-cf9b4ba13976"><configuration readonly="False" hideOnError="False"><style labelVisible="True" linkInSummary="True" showNoControls="True" allowMultiSelect="False" /></configuration></valueProvider><requiredParameters /><configurationControlClassGuid>73bded50-f1aa-4ff4-a80e-a6c9e047d472</configurationControlClassGuid></parameter>

The specified GUID does not refer to a registered class: 891d9058-6b53-4a59-8aff-cf9b4ba13976"

Environment

ITMS 8.5 RU1

Cause

The cloned reports were created before an upgrade to ITMS 8.5 RU1 and they apparently become corrupted due to the report's GUIDs being changed. After the upgrade was completed the database did not recognize the original GUIDs and the reports could not be display, edit, or delete from the SMP Console.

Resolution

Use the following SQL query to replace all cloned and corrupted report's GUIDs to the correct ones:

Declare @t as table (guid uniqueidentifier)

​Insert into @t 

 

select guid

from vitem 

where classguid = 'a968a2a6-c9b9-483b-b9e0-7f0b199f9da3' 

and 

(

ProductGuid ='B1338338-5575-4A27-9808-23BEC40D79FA' 

or ProductGuid = 'C6D19F78-1434-49AC-BEC8-D18255E99F58' 

or ProductGuid = 'C6D19F78-1434-49AC-BEC8-D18255E99F57' 

or ProductGuid = 'c6b52ec2-597c-4efe-8830-b92f11888a4a'

) 

and state like '%891D9058-6B53-4A59-8AFF-CF9B4BA13976%'

 

update item 

set state = replace

(cast(state as nvarchar(max)), 

'valueProvider classGuid="891D9058-6B53-4A59-8AFF-CF9B4BA13976"', 

'valueProvider classGuid="fd8b9293-29b1-42e2-bac5-7774df8143cc"')

where guid in (select guid from @t)

 

Once the above query is run then refresh the reports page in the SMP console. 

Note: It is always recommended to take a full backup of the database (Symantec_CMDB) prior to running any query on SQL database.