Well...the manual has this to say
 
Application-Bus-Time-Diff <start_time> <end_time>

[<holiday_schedule_name> [<workday_schedule_name>]]

Returns an integer that represents the number of seconds between the start
and stop time, taking business hours into account.

So it looks like your using it properly...have you verified that the Holiday
and Workday schedules exist by the name in the Assigned Group field? (Yes I
know they were working fine before)

then check the records themselves...I don't recall what version they
introduced it...but in 6.x they have in upwards of 4 start and stop times
per day...I remember in previous versions it was only one start and stop
per...which may not have converted over properly on the upgrade


  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE
Sent: Tuesday, May 29, 2007 12:24 PM
To: [email protected]
Subject: Re: $PROCESS$ Application-Bus-Time-Diff and ARERR 4568


** 

$PROCESS$ Application-Bus-Time-Diff $Tech Start$ $Tech Stop$ "$Assigned
Group$" "$Assigned Group$"

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of L. J. Head
Sent: Tuesday, May 29, 2007 1:16 PM
To: [email protected]
Subject: Re: $PROCESS$ Application-Bus-Time-Diff and ARERR 4568

 

Could you copy the exact runprocess here so we can try to help?

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE
Sent: Tuesday, May 29, 2007 11:53 AM
To: [email protected]
Subject: $PROCESS$ Application-Bus-Time-Diff and ARERR 4568

** 

Hi everyone:

 

I've searched the list archives on this issue and saw some discussion of
this issue but no solutions.

 

Last week we upgraded our 5.1.2 server to 6.3 patch 21.  Ever since then
users are getting ARERR 4568 any time they perform an action that requires a
business time calculation.  The exact error is.

 

ARERR [4568] The start or end time provided for the command is not valid.

 

This occurs whenever a specific filter performing a $PROCESS$
Application-Bus-Time-Diff function is executed.  I can't figure out what's
wrong.  It just looks like a Remedy bug, especially considering the
application in question has run for the past two years at four different
sites with hundreds of users and almost a million tickets without a hitch.
The only change we made was upgrade the server, Java, and clients.

 

Here's our environment specs:

 

Windows Server 2003 SP 2

Microsoft SQL 2000 SP 4

J2RE 1.4.2_14

J2SDK 1.4.2_14

Remedy ARS 6.3 patch 21

Remedy User client 6.3 patch 20

 

Any ideas?

Norm

__20060125_______________________This posting was submitted with HTML in
it___ 

__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted with HTML
in it___

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

Reply via email to