Path translation might be required when storing scripts and runtime data results from a scenario on a shared network drive (Tools > Options > Runtime File Storage tab).
Path translation is a mechanism used by LoadRunner to convert a remote path name for the Controller so that all participating machines recognize the same network drive.
The scenario runs on a Windows-based machine and includes multiple Vusers running on both Windows-based and Linux load generators. One remote load generator may map the network drive as F, while another load generator maps the same drive as H. In a complex situation such as this, you need to ensure that all participating load generators recognize the same network drive.
The Scenario Groups/Scripts pane in the Design view contains a list of all the Vuser scripts associated with a scenario, and their locations. A script's location (path) is always based on the Controller machine's mapping of that location. If a load generator maps to the script's path using a different name, path translation is required.
For example, assume that the scenario is running on a Windows-based machine named pc2, and that a Vuser script is located on a network drive. The Controller machine maps the network drive as m:\lr_tests. If the remote load generator hosting the Vusers also maps the path as m:\lr_tests, no translation is necessary. However, if the remote machine maps the path as another drive or path, for example r:\lr_tests, you must translate the path to enable the load generator to recognize the script location.
Note: If the Controller and load generator machines are all Windows machines, consider using the Universal Naming Convention method instead of manually adding path translation information. On Windows machines, you can tell the Controller to convert all paths to UNC, in which case all the machines are able to recognize the path without requiring path translation. An example of UNC format is