e2e_appmon Troubleshooting

This section contains some troubleshooting points for the e2e_appmon probe.
uimpga-ga
This section contains some troubleshooting points for the e2e_appmon probe.
NimRecorder is not Deployed or Installed.NimRecorder+is+not+Deployed+or+Installed+vGA
Symptom:
I am using the e2e_appmon probe deployed on my robot. However, the NimRecorder is not getting deployed to record new script and to edit existing scripts. The probe is deploying the script executor only.
Solution:
Instead of deploying the e2e_appmon probe, deploy the e2e_appmon_dev (1.91 or later) probe. The NimRecorder is deployed automatically.
OR
For the e2e_appmon probe (standard edition), install the NimRecorder manually.
Follow these steps:
  1. Go to 
    Start > All Programs > Nimsoft Monitoring > E2E Scripting
     and select the 
    Uninstall NimRecorder
    .
    The Script Executor is removed.
  2. Go to 
    [Nimsoft Installation drive] > Nimsoft > probes > Application > e2e_appmon > Install
     folder.
  3. Double-click the 
    nimrecorder.msi
    .
    Icon
    Note:
     The name of .msi installer file is based on the NimRecorder version. For example, it is 
    nimrecorder51.msi 
    for installing the NimRecorder 5.1.
  4. Follow the instructions and install the NimRecorder.
    The help file of the NimRecorder is accessible at 
    Start > All Programs > Nimsoft Monitoring > E2E Scripting > Help
    after installing the NimRecorder.
Scripts not Working after Upgrade
Symptom
My existing scripts have stopped working after upgrading the probe.
Solution
Recompile your existing scripts with the new NimRecorder to make them compatible.
Drop an email to  for troubleshooting your script-related issues and support on NimRecorder 5.1.
Scripts not Working due to Synchronization
Symptom
My existing scripts have stopped or lose focus while running the script through NimRecorder because of synchronization of text.
Solution
The 
UsePage
 and 
Web 
functions are used for synchronization process. The Internet Explorer (IE) uses the window name instance for the bitmap synchronization and it varies with each IE execution. Therefore, the wintask recommendation is to use the 
TopInstance
 function of NimRecorder instead of providing a constant instance number.
For example:
Pause 10 secs until Bitmap("test.bmp") InWindow("IEXPLORE.EXE|Internet Explorer_Server|WinTask_x64 Help - Internet Explorer|1",2) InArea( 101, 172, 26, 41 )
For Topinstance, the constant instance number can be replaced with:
Pause 10 secs until Bitmap("test.bmp") InWindow("IEXPLORE.EXE|Internet Explorer_Server|WinTask_x64 Help - Internet Explorer|1",Topinstance()) InArea( 101, 172, 26, 41 )
Drop an email to  for troubleshooting your script-related issues and support on NimRecorder 5.1.