Troubleshooting and Limitations for Recording
the recording can crash or severely malfunction in the presence of antivirus code change prevention mechanisms.
In particular, McAfee Host Instrusion Prevention (HIP) is one of these mechanisms.
The only workaround possible is to uninstall such programs.
After the uninstall procedure, the LR recording should be started again (no computer's reset is required).
If you have an antivirus code change prevention program installed, it may prevent you from recording your application or Web site. In particular, McAfee Host Intrusion Prevention (HIP) may block the recording.
Workaround: Uninstall the program and restart the recording.
- If a client-side certificate is required during remote proxy recording, the dialog box requesting the certificate, opens on the VuGen machine, and not on the client machine.
- NTLM authentication is not supported for proxy recording.
Issue: When recording a session in Chrome, the browser may appear to hang as it continually searches for external links.
Workaround: Manually set the environment's proxy settings in Chrome—do not enable Automatically detect settings.
Issue: "Trusted sites" appears in every recorded snapshot.
Solution: Open Internet Explorer at least once before recording a script in VuGen.
Issue: The most common problems seen in Web recording.
The following blog post lists five tips to solve the most common Web recording issues: http://h30499.www3.hp.com/t5/HP-LoadRunner-and-Performance/5-tips-to-solve-the-most-common-problems-seen-in-Web-recording/ba-p/6357387.
Issue: Your script is missing steps you recorded.
You encounter the following warning in the Output Pane > Code generation tab:
Warning: One or more responses are missing or have missing packets. Therefore, a step may appear to be missing in the script. This issue can be caused if the recording was stopped before all the responses were received. If the script is generated from a .pcap file, check if the file has missing packets.
This can be caused when you click Stop Recording before all the traffic has been received.
Steps to Resolve: Record the script again. Make sure all pages and resources have been downloaded before clicking the Stop Record button.
Issue: When recording on Internet Explorer (IE) 10, the browser uses cached pages, and may not record all of the steps.
Steps to Resolve: Each time you begin recording, configure IE 10 to always refresh Web pages from the server. After you begin a recording session, in IE, click F12 to open the Developer Tools pane. In this pane, usually located at the bottom of the browser window, select Cache > Always refresh from server.
When you open VuGen as a non-administrator user, during the recording process you may see a certificate pop-up warning message. The message is automatically closed and does not affect the recording.
If you record a script in the Init section and then re-record in the Actions sections, compilation may fail. This happens because VuGen creates new header files with each code generation, removing the old ones.
Workaround: Re-record the new session in the same section as the first recording.
When recording a Web HTTP/HTML script using WebSockets, if you stop the recording and then resume the recording session, the new data overwrites the original data in the buffer. This is true even if you perform the second recording into a new action.
If Firefox is set as the default browser, the Obtain the proxy settings from the default browser option (Runtime Settings > Internet Protocol > Proxy) does not work, and a direct connection is used.
FTP Active SSL mode is not supported for record or replay.
An FTP recording may generate an empty script.
Workarounds: Perform one of the following:
- Configure the FTP server to include the string "FTP" in the welcome message.
- Open the Network > Mapping and Filtering recording option node. In the Port mapping area (upper section), click New Entry. In the Server Entry - Port Mapping dialog box, set the Service ID to FTP and specify the FTP server's port number.
In general, 64-bit applications ported from a 32-bit client version should work identically to the 32-bit client. There is a small risk that new clients will use the power of native 64-bit applications. For example, when using 64-bit long types for Identifiers in DB tables, the identifier value will be cut and the query will fail.
The following guidelines apply:
- The environment for 64-bit recording must be a Windows 7 x64 or Windows 8 x64 (Windows 8 x64 added in Service Pack 11.52), and a 64-bit Application Under Test (AUT).
- Recording on 64-bit operating system for 32 and 64-bit applications (running as a 64-bit application) is supported.
- You cannot record a page requiring a client certificate with 64-bit version of Internet Explorer.
- Replay is only supported for 32-bit.
- For the Java Over HTTP protocol: JVM 32-bit is required for replay.
- Oracle 2-Tier: Both 32-bit and 64-bit clients need to be installed (the 32-bit client is required for replay).
For the .NET protocol: There are two available 64-bit types for .NET applications (AnyCPU and pure 64-bit). LoadRunner only supports AnyCPU. There is currently no solution for pure 64-bit applications.
For replay, LoadRunner uses the same AnyCPU dlls that were used for Recording.
Note: With LoadRunner 11.50 and higher, .NET Framework 4 should be installed. This package carries both versions of the libraries for 32 and 64-bit systems.