Adding computer to Filter results in an error "An error has occurred while displaying data" if the same resource is added twice.

Products

• Management Platform (Formerly known as Notification Server)

Issue/Introduction

The customer have created a custom computer filter.

And after adding a resource the 2nd time into the same filter, he is getting an error:

"An error has occurred while displaying data. Check server logs for details."

 

Steps for reproducing the issue:

1. Create a simple Computer Filter.
2. Add New resource (or use an existing one in current filter resource) into this filter, so it would be added separately in Include list:
   
   
3. Now if you would try to add this resource again using Right-Click on Computer > Add to Filter  - and adding to the same filter - you will receive the error message referenced above. Technically now this filter has this resource added 2 times (filtered by name, and then by resource GUID).

 

 

In a Profiler trace you can see that we try to add the same GUID a second time. Something like this:

EXECUTE spCollectionIncludesResourceInsert @CollectionGuid='f49a25e1-3cd3-4f39-b7a3-d2d05a7b4846', @ResourceGuidList=N'e6d221d0-10c6-44b5-b6d0-e999a1bcb684
e6d221d0-10c6-44b5-b6d0-e999a1bcb684', @cleanImport=1

Thus full error actually is:

Item save to DB failed: f49a25e1-3cd3-4f39-b7a3-d2d05a7b4846, (fromClone=False, user=domain\smpservice)

Violation of PRIMARY KEY constraint 'PK_CCollectionIncludeResource'. Cannot insert duplicate key in object 'dbo.CollectionIncludeResource'. The duplicate key value is (f49a25e1-3cd3-4f39-b7a3-d2d05a7b4846, a116b6b0-d314-4a91-b7a6-4d9fcdebcf00).
The statement has been terminated.

 

Might require to review the Stored procedure to exclude existing resources to be re-added or/and provide more detailed error/explanation why it fails (as this resource have been already added into this filter)

Cause

Known issue. There was an issue with ensuring the uniqueness for all include/exclude values.

Environment

ITMS 8.5 RU3, RU4

Resolution

This issue has been reported to the Symantec Development team. A fix for this is currently targeted to the next release after ITMS 8.5 RU4.

There is a workaround for this issue.  There are 4 updated stored procedures that needs to be applied:

• spCollectionIncludesResourceInsert.sql
• spCollectionIncludesCollectionInsert.sql
• spCollectionExcludesResourceInsert.sql
• spCollectionExcludesCollectionInsert.sql

Download the attached "UpdatedStoredProcedures.zip" and run them in Microsoft SQL Management Studio. These will drop the existing ones and recreate them with the necessary fixes.