Troubleshooting: WebInspect Macro Recorder unable to load page or not performing as expected


If the WebInspect Macro Recorder is unable to parse a page or is "stuck" during a redirect (i.e., SSO), try narrowing down the issue (proxy, browser version, TC modifications). In troubleshooting these types of issues you can use the following steps to narrow down where the challenge is. 

  1. Run it through the WI Web Proxy tool and a regular, working browser (Chrome, Edge, Firefox, etc.) to see if that is the cause of the situation. If it works, then the problem is not with the macro recorder, but with the WebInspect Proxy.
  2. If 1 is successful, try opening the site in the truclientbrowser.exe.
    1. The default location of the executable is C:\Program Files\Fortify\Fortify WebInspect\truclientbrowser
    2. It is preferred you open the executable in a new profile using the statement as an example:
      truclientbrowser.exe -no-remote -profile c:\temp\profile
  3. If 1 & 2 are successful then it is not the WI Proxy nor the version of Firefox causing the problem. To further troubleshoot, copy the user.js file from C:\Program Files\Fortify\Fortify WebInspect\datTCB\ASCMasterProfile to the new profile (c:\temp\profile) and see if the issue is reproducible. If it is reproducible,
    1. Press Ctrl + Shift + J to open the Browser Console Log and look for anything that may indicate the cause of the issue
    2. Press F12 to open the Developer Tools and look at the network tab for any indication of the issue.
  4. Open a ticket with Fortify Support and report your findings.

NOTICE: If you are using version 20.x, the steps are the same; however, the location of truclientbrowser.exe is C:\Program Files\Fortify\Fortify WebInspect\browser59 and the location of the user.js file is C:\Program Files\Fortify\Fortify WebInspect\dat59\ASCMasterProfile.


Support Tip
Comment List