Hi,
Does your escalation run on SHR:TmpMessages?
I would run it on some "scheduler" form, and it should trigger once (one
record).
The normal way to find out what the problem is would be to turn on logging.
What happens when you try to delete one record from the user tool?
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
> We are running an escalation nightly that runs this command:
> *Application-Query-Delete-Entry
> "SHR:TmpMessages" (( 'Status' = "Sent") AND ( 'Send Time' != $NULL$ ))*.
> The effect is to clear a form that contains records accumulated during the
> day, but which are no longer needed.
>
> Running this creates thousands of entries in the arerror.log file
> (roughly,
> but not exactly, equivalent to the number of records in the form) that say
> this: *Thu May 29 10:31:45 2008 390603 : Entry does not exist in
> database
> (ARERR 302)*.
>
> There are no errors that show up in the api or sql logs, and the records
> DO
> get deleted. Any idea why these errors appear? I'm kinda stumped as to
> where else to look for a cause.
>
> Rick
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
