All,
I've just come across 2 issues with SLM 7.1 Patch 1
One is supposedly fixed in 7.5

Issue 1:
If you open an SLM Template from the Configure Templates form, and click the 
little dialog x close button in the upper right hand corner, and then try to 
re-open the same template you will get a unique index violation error.
This is a known defect: SW00292610
And is supposedly fixed in version 7.5
It doesn't seem to occur if you use the Save and Cancel buttons in the bottom 
left.

Issue 2:
We recently imported a bunch of Service Targets into our server.
They were all in a status of Could not be built.
When I looked at them, it looked like they were missing some actions and the 
milestones had errors when I tried to view them as well.
So I rebuilt the Templates by hand (as those errored out when I tried to view 
them as well).
I then deleted all the old Service Targets, and attempted to re-import them 
from the same files.
Well none of them came in.
I started looking at the log files and found all sorts of unique index 
violation errors.
It appears that when you delete an Service Target, it leaves a bunch of old 
association records out there and doesn't clean them up.
Here's the list of forms that I found have old association records that weren't 
cleaned up:

SLM:Association

SLM:Rule Definition

SLM:ServiceTarget

SLM:Milestones

SLM:RuleAction

SLM:RuleAction% (i.e. SLM:RuleActionSetValueItem)

You would think that when you delete a Service Target it would clean up all the 
records that are associated to the Service Target.
Isn't that kind of a basic thing?
Either way, it's real easy to duplicate (just be sure you have a Database 
Backup before you do it)
Import some service targets, delete the records, then try and import them again.

ITSM 7.1 Patch 9
SLM 7.1 Patch 1
Windows Server 2003
MSSQL 2005

Thanks
Matt P.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Reply via email to