Initialization Errors

This section describes troubleshooting for the following initialization errors:

Initialization Error - Driver Failed to Initialize

Communication is not active!

There has been a problem initializing the driver.

Troubleshooting

  • Reboot the Controller machine. If this does not solve the problem, reinstall LoadRunner.
  • If that fails to solve the problem, contact customer support and provide them with an explanation of the problem, and the error message returned.

Initialization Error - Online Process Failed to Initialize

Failed to create Online: 'process'

The online process has not been initialized.

Troubleshooting

  • Check that the Controller COM objects are registered in the Registry Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\LoadRunner\CurrentVersion.
  • If they are not registered, run register_controller.bat from the <LoadRunner root>\bin directory to register the COM objects.
  • If this fails to solve the problem, contact customer support and provide them with an explanation of the problem, and the error message returned.

Initialization Error - Transaction Monitor Failed to Initialize

Transaction monitor not available: 'error description'

The Event Server has not been initialized.

Troubleshooting

  • Make sure you are logged into the Controller machine using an account with local administrative rights. The installation of LoadRunner should also have been performed using such an account.
  • Check that the Controller COM objects are registered in the Registry Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\LoadRunner\CurrentVersion.
  • Run the following files from the <LoadRunner root>\bin directory: register_controller.bat, set_mon.bat, and register_vugen.bat, and reboot the machine.
  • If this fails to solve the problem, contact customer support and provide them with an explanation of the problem, and the error message returned.