To prevent this error message from being thrown, one should disable the execution of the script in the TrueLog Explorer.
Attached is a screenshot showing this option.
Thank you for the reply.
I did what you suggested and restarted Truelog. The error is still thrown 2 times at the same interval and the log shows that the login looks to have failed despite it works manually [human] out side of the script.
If this is only happening when you view the results in TrueLog, then it can be ignored. When you are viewing using TrueLog, you're sending the web page to an embedded Internet Explorer control. If there are scripts on the page or other client-side code, you can get odd error messages.
Examine the results after the login attempt to see if it actually succeeded. Do the pages which follow the login appear to be correct.
Also, for Remedy Mid-Tier, be sure you are using the special recording type for the appropriate version of Remedy.
Thanks VERY much it is always the simple things! I switched to "Remedy Mid-Tier" script type from std html and it is now working.
Great! That one is easy to miss as it's somewhat hidden.
Remedy has its own "AJAX-like" asynchronous protocol. Without the extras in that recording type, TM ART is pretty confused by the asynchronous traffic.