Flex Correlation

Flex Correlation

Flex is a cross platform framework for creating rich internet applications. LoadRunner can be used to record flash applications using flex protocol. There are various steps involved in correlating dynamic values generated in flex scripts.

Please follow the below process:

1. Open the script in VuGen in script view

2. Select the value that you think as dynamic (for example DSId)

3. Go to Generation Log tab

4. Search for the first occurrence of the dynamic value

5. Make sure that the dynamic value falls under Response Body

6. Press F3 to check for the next occurrence and make sure that it is under AMF Response XML

7. Check for the snapshot file detail in the previous “Add to Transaction” part and go to script view.

8. Search for the same snapshot file name in the script view and identify the function where it falls.

9. Go to the tree view

10. In the right column, select the response tab

11. Search for the dynamic string in the tree view

12. Identify the string and right click to select “Save value to parameter”

13. Give a XML source name

14. Navigate to the script view and you can find that Response Parameter value has been created for that function.

Advertisements

Unable to generate an analysis report for large result sets

Unable to generate an analysis report for large result sets

Problem

Getting Parsing error with large result sets (less than 2 GB).:

Parse Command line error:

Unable to cast COM object of type ‘System._ComObject’ to interface type ‘Borland.Vcl.Fields’. This operation failed because the QueryInterface call on the COM component with IID ‘{XXXXXXXXXXXX}’ failed due to the following error:

No such interface supported. (Exception from HRESULT XXXXXXXXX (E_NOINTERFACE)).

Note: Small result sets work just fine on the same machine.

Cause

The cause is due to taking a lot of resources.

Fix

The workaround is to change Data collection option from "Generate Summary data while generating complete data’ (third option which is the default) to "Generate Complete data" which is the second opton in the Analysis.

For this, go to Analysis —-> Tools

How to verify the arguments provided in web_set_certificate_ex() are correct

How to verify the arguments provided in web_set_certificate_ex() are correct

a) On the vugen machine, open a DOS window and navigate to LoadRunner Installation bin folder (i.e. <LoadRunner>\bin).

Type in: openssl and hit <enter>

b) Type in: s_client -connect <host:port> -cert <certificate name along with path in PEM format> -key <the path to the private key to use in PEM format> -passwd <the private key password>

If the above command works, then the arguments provided in web_set_certificate_ex() are valid.

Example: s_client -connect ivorde.ro:443 -cert example.pem -key keyex.pem -pass 1234

VUGEN gives exception error at the end of the recording or during replay due to thumbnails

VUGEN gives exception error at the end of the recording or during replay due to thumbnails

Problem

Getting the following pop-up error at the end of the recording:

AXWIN Frame Window: thumbprocess.exe – Application error

The instruction at " 0x7dc995fe" referenced memory at "0x02b87cf4". The memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.

Cause

The cause of this issue is unknown.

Fix

The workaround is as follows:

1. Press "start" -> "run"

2. Type "regedit"

3. Press "Ok"

4. Navigate to "HKEY_LOCAL_MACHINE/SOFTWARE/Mercury Interactive/LoadRunner/Vugen/Thumbnails"

4. Double-click on "GenerateThumbs," and set the value to 0.

Now try doing a recording (or replay if the issue was during replay) with Vugen.

When recording a DB2CLi application, VuGen.exe crashes half way into the recording

When recording a DB2CLi application, VuGen.exe crashes half way into the recording

Problem

When recording a DB2CLi application with VuGen, VuGen.exe crashes half way into the recording

Cause

This could happen if the application is running under multithreaded mode and the process tree involves input from multiple processes during recoding. There is a known limitation within LoadRunner where the database record/replay solution within VuGen does not support multithreaded applications however there is a workaround available

Fix

Here are the suggested steps to make VuGen recording thread-safe:

Replace the file <Install_drive>:\Program Files\HP\LoadRunner\bin\dbir32.dll with the attached dll dbir32

Edit the file <Install_drive>:\Program Files\HP\LoadRunner\config\vugen.ini and add a new line "THREAD_SAFE=1" under [Inspector] section as shown below:

1. [INSPECTOR]

2. TRACE_FILENAME=C:\Documents and Settings\dpereir_infosys\Local Settings \Temp\noname21\data\sqltrace.txt

3. TRACE_LEVEL=3

4. ASCII_LOG_LEVEL=6

5. THREAD_SAFE=1

Restart VuGen and record the application again

“ERROR 01S00 INTERSOLVODBC SQL Server driverInvalid attribute in connection string: User.” when connecting to a Sybase database

"ERROR [01S00] [INTERSOLV][ODBC SQL Server driver]Invalid attribute in connection string: User." when connecting to a Sybase database

Problem

The following script action was used to attempt to connect to a Sybase database:

lr_db_connect("StepName=Connect",

"ConnectionName=DatabaseConnect",

"ConnectionString=Driver=Sybase System 11;Server=<server_name>;Database=<db_name>;Trusted_Connection=False;User=<uname>;Password=<pword>",

"ConnectionType=ODBC",

LAST);

However this resulted in error messages being reported as follows:

Action.c(6): Error: DB Connection failed {"ERROR [HY000] [INTERSOLV][ODBC SQL Server driver]Insufficient information to connect to the data source.

ERROR [01S00] [INTERSOLV][ODBC SQL Server driver]Invalid attribute in connection string: User.

ERROR [01S00] [INTERSOLV][ODBC SQL Server driver]Invalid attribute in connection string: Server.

ERROR [01S00] [INTERSOLV][ODBC SQL Server driver]Invalid attribute in connection string: Trusted_Connection.

ERROR [HY000] [INTERSOLV][ODBC SQL Server driver]Insufficient information to connect to the data source.

Cause

The connection string specified in the lr_db_connect() function:

"ConnectionString=Driver=Sybase System 11;Server=<server_name>;Database=<db_name>;Trusted_Connection=False;User=<uname>;Password=<pword>",

is not valid and cannot be used to connect to a Sybase database.

Fix

The correct connection string to use when connecting to a Sybase database is as follows:

"ConnectionString=DRIVER={Sybase System 11};UID=<uname>;PWD=<pword>;SRVR=<server_name>;DB=<db_name>",

While the above connection string is applicable when accessing a Sybase database, other connection string formats are applicable for other database technologies.