MI Listener: Additional Trace Logs For Debugging

Did you know there is a deeper level of logging in the MI Listener Aganet? The following can be done if you are having problems with the MI_Listener and the Generator to determine connectivity issues.

  1. kill the agent processes on all the machines
  2. append to [launcher] section at launch_service\dat\mdrv.dat the following line:
    ExtCmdLine=-drv_int_msgs -drv_log_flush
  3. Activate agents on all the machines and try to connect.
  4. collect log file generated (%TEMP%\LoadRunner_agent_startup.log).

You will need these logs when submitting a ticket with support.

What's Next?

Did you enjoy this article? Help spread the word by sharing:

Join the Northway Navigator Club today and get access to restricted content including our best tips and tricks. Membership is free! You will also receive free email updates by registering.

Engage in the conversation and leave a comment:

Scott Moore

About Scott Moore (153 articles)

With over 20 years of IT experience with various platforms and technologies, Scott has tested some of the largest applications and infrastructures in the world. He is a Certified Instructor and Certified Product Consultant in HP’s LoadRunner and Performance Center products. He currently holds HP certifications for ASE, ASC, and CI. A thought leader in the APM space, he speaks regularly at IT conferences and events