Getting the following message being thrown by an service target when an Incident is submitted:

 

ARERR (644) No Time Segment definition exists with the specified tag.

Getting the following message being thrown by an service target when an Incident is submitted:

 

ARERR (644) No Time Segment definition exists with the specified tag.

 Here is the error in the log:

 

> Checking SLM:Measurement:ReqProcOverallStartTimeUpdateSLODueDateX (0)
>    --> Passed -- perform actions
>         0: Set Fields
>                   Application-Bus-Time2-Assoc-Add 1191429744 30600 1 "" "" -e  "AG005056AC511091r9RgSdLwAAt9AH"
>                   Exit code: 1  Value:
>               No Time Segment definition exists with the specified tag
> **** Error while performing filter action
> **** Error while performing filter action
> **** Error while performing filter action
> /* Wed Oct 03 2007 10:31:57.0720 */     End of filter processing (phase 1)

>         0: Push Fields (ARERR 644)

The SET Fields run process is:

$PROCESS $ Application-Bus-Time2-Assoc-Add $zD_IntegerStartTime $ $zD_Integer $ 1 "$zD_BTHolidays $" "$zD_BTWorkdays $" -e  "$zD_EntityID $"

 

So the problem appears to be that there is no zD_BTHolidays or zD_BTWorkdays specified? Apparently there are NO tags being read for this so the calculation cannot be performed. Did you define business time segements for the SVTs?

 

In the end, deleting the business entity and time segments did the trick.  It seems that there is some stuff leftover from previous changes to these.  The customer seemed to recall an incident where the SLA's, when deleted, were not disappearing from the Escalations area and he had to manually go in and remove them, or just create completely new Service Targets. This must have affected the business time segments. Deleteing and recreating them resolved the issue.