e2e_appmon script runs but returns NULL QOS entries after some time

Document ID : KB000034020
Last Modified Date : 14/02/2018
Show Technical Document Details
A - 4 error code means that the script was killed before execution completed. In this case you
would also get an alarm telling you that the script did not complete on time and had to be killed.

Using the Teamviewer (instead of VNC), we observed that the "Save password" window on Internet Explorer was causing an error on the script execution, so the QOS on SLM was returning null due to this issue. The script would run fine for some time and then the password prompt would popup and stall the script.

If you don't not use a remote viewer, it is difficult to catch exactly what is happening when a script fails. Sometimes the option 'dump screen on timeout' will show you the root cause but using VNC/Team Viewer/LAN Manager or some other remote viewer software is highly recommended.

After we select the IE to not save passwords from that site, the script ran consistently without any more issues.

Also not that no other users can be logged onto the system except for the e2e probe user otherwise the script will fail.

See also:
https://na4.salesforce.com/articles/Case_Summary/e2e-appmon-2-0-TaskEdit-Browser-error-add-on-failure-Check-that-the-WTBho-add-on-is-enabled?popup=true

keywords:? WTBHO WTBho add on NULLS null nulls error code -4 -987654321 QOS SLM script stops fails