Make that ARAPILOGGING=88 and you get some extra information too. However... Just to verify...
You are looking at the API and SQL logs (again server side)... You are saying that the API action does not start until the end of the "client frozen" time period. ( Your getting that from watching with a wall clock and checking the server log files.) You are also saying that the total time for the API call and the SQL portion of that call is always "normal" for that action. hum... Is it possible that the lag is due to a windows memory swap to disk? Maybe the User Tool application is being swapped out of memory on the client? -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/26/07, Michiel Beijen <[EMAIL PROTECTED]> wrote: > ** Tony, > > If you create user side logging by setting the ARAPILOGGING=1 environment > variable and then starting aruser.exe? > Or are there no timestamps in these logs? > > -- > Michiel _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
