What is the way to EXPORT the Controller Messages from the result (*.lrr_) or the Microsoft Access database file?

Hello,

In 2023R1 Output Logs are stored in SqliteDb.db under the result folder.

The error messages could be checked through SQLite tool like below:

You may use the [Save...] button above to export the table as csv file.

Thanks,

I looked at the directory path that is specified in the Controller's Results Settings. On my 2023 R1 system there is an .MDB file for the Microsoft Access database, but there is NO .DB file or any file starting with Sqlite*.*,

My main point here is that the Controller's Output Window, for many Loadrunner software versions prior to Version 2022 R2, there has ALWAYS been an ICON at the top of the Controller's Output WIndow that allowed for the EXPORTING of any Controller messages to a CSV file. Why this very useful feature has been removed from 2022 R2, and especially the latest Loadrunner software (which is supposed to be the best one) in Version 2023 R1 or  2023 R1 Patch 2... does NOT make any sense whatsoever.

Customers should not have to use a third party tool, like SqLiteDb to EXPORT Controller Output messages that used to be provided by using the software within the Controller in many prior versions of the Controller software.  The removal of this feature is an oversight caused by the introduction of the new user interface for the Output Window, which does not provide any VALUE ADD to the customer that I can tell. It also makes the Controller and the Analysis software look "UNFINISHED" since ONLY a few parts of the Controller / Analysis software use this new user interface (ie. the Controller's / Analysis's Output Window and the Controller's Transaction Window). 

This problem is not limited to the Controller either since the Analysis software uses the same or similar software to display the Controller's messages from WITHIN the Analysis softrware (when you select the option within the Analysis software to view the Controller Messages).

I looked at the directory path that is specified in the Controller's Results Settings. On my 2023 R1 system there is an .MDB file for the Microsoft Access database, but there is NO .DB file or any file starting with Sqlite*.*,

My main point here is that the Controller's Output Window, for many Loadrunner software versions prior to Version 2022 R2, there has ALWAYS been an ICON at the top of the Controller's Output WIndow that allowed for the EXPORTING of any Controller messages to a CSV file. Why this very useful feature has been removed from 2022 R2, and especially the latest Loadrunner software (which is supposed to be the best one) in Version 2023 R1 or  2023 R1 Patch 2... does NOT make any sense whatsoever.

Customers should not have to use a third party tool, like SqLiteDb to EXPORT Controller Output messages that used to be provided by using the software within the Controller in many prior versions of the Controller software.  The removal of this feature is an oversight caused by the introduction of the new user interface for the Output Window, which does not provide any VALUE ADD to the customer that I can tell. It also makes the Controller and the Analysis software look "UNFINISHED" since ONLY a few parts of the Controller / Analysis software use this new user interface (ie. the Controller's / Analysis's Output Window and the Controller's Transaction Window). 

This problem is not limited to the Controller either since the Analysis software uses the same or similar software to display the Controller's messages from WITHIN the Analysis softrware (when you select the option within the Analysis software to view the Controller Messages).

Hello Richard
I just want to clarify a few things for you.
You are correct in that the output UI was changed in the last release. This is part of our on-going modernization efforts and you will see incremental updates to many more UIs in the future versions. 

As part of the effort to replace some older UIs we are not only providing a fresher look and feel but also reducing any technical debt and also providing better stability. However, thanks for pointing our that this option was removed.
I have added this to the backlog and we will re-instate this soon.

Cheers David