A Managed Software Delivery policy will time out when opening with the generic "Symantec Management Server Error" message if there are many Supersedes associations. Customer states that he was able to add multiple Supersedes association types and a detection rule to a SW resource 7.1 SP2 MP1 and use that resource in a MSD Policy but now that he has upgraded to 7.5 he cannot do it.
Customer reported steps:
1. Create a Software Resource. He used Java 7 Update 45. 2. On the Associations tab add multiple Supercedes associations. 3. Add that Software Resource to a Managed Software Delivery policy. 4. Note that after adding that SW resource to the policy you can still open that policy. 5. Now add a detection rule to the SW Resource. 6. After adding the detection rule you can no longer open the MSD policy, it times out and throws the generic "Symantec Management Server Error" page.
My steps to reproduce:
1. I created a Software Resource for Java 7 Update 45 x86. 2. On the Associations tab I added all the available i586 software components (15 of them) as an association type of Supercedes. 3. Create a new Managed Software Delivery policy. 4. Add the newly created SW resource to the MSD policy. 5. Now, nine times out of ten I receive the same generic error when I try to open the MSD policy for editing or scheduling. I do not even have to add a detection rule to the SW resource.
Date: 01-Jan-01 00:00:00
Tick Count: 121254631
Host Name: xxxxxx
Process: w3wp (9724)
Description: Failed to create Superceding Component list :
System.Threading.ThreadAbortException: Thread was being aborted.