Transaction response time for Web Protocol with different Internet Explorer versions

Transaction response time for Web Protocol with different Internet Explorer (IE) versions. Here we are comparing IE 8 and IE 10.

1. Does the user agent setting in run time settings have any impact on response times in LoadRunner i.e. if we simulate IE10 browser with VuGen 11.52 compared to if we simulate MS IE 8.0 browser with VuGen 11.0x ?

Answer : User agent string does not change the response time. Some servers respond with a different resources depends on what user agent is sent to them (i.e. if you go to BBC.com or Facebook.com with your mobile device or with your desktop browser you will see a different page) – as a response to the different resources from the server, response time can be different

Read More »

Advertisements

Critical error “Unable to Determine AUT’s bit capacity” when recording a 64-bit .NET application

The following error is seen when launching a 64-bit .NET application during recording

Critical error "Unable to Determine AUT’s bit capacity"

LoadRunner does not support the recording of 64-bit .NET applications

The workaround is for customer to re-build and deploy the client as a 32-bit .NET application.

-OR-

Use CorFlags to set the application to run as a 32-bit .NET application.

Refer to the following link for more help on using CorFlags.exe

http://msdn.microsoft.com/en-us/library/ms164699(VS.80).aspx

Failure in trying to create Activation Context error

Getting "Failure in trying to create Activation Context" error when connecting from VuGen to Quality Center – ALM.

This is caused by using ALM client in Shared deployment mode.

To fix this issue

– Clear all (Full Cleanup) available ALM client files.

– Verify that there is no content in C:\ProgramData\HP\ALM-Client (C:\documents and settings\All users\HP\ALM-Client).

– Re-download ALM client by login against ALM URL through IE

Enable non-administrator users to remotely monitor a machine with Windows Resource Monitor

The following error appears when trying to add a Windows Resource Monitor:

"Monitor Name: Windows Resources. Cannot connect to Machine

Details: Access is denied."

Logging in as administrator fixes this problem.

Refer to Microsoft knowledge base article Q158438

By default, Windows machines enable monitoring only for users with administrator privileges. In order to allow monitoring for non-administrator users, you must grant read permission to certain files and registry entries. The following information was published under Microsoft knowledge base article Q158438

1. In Windows Explorer or File Manager, give the user at least READ access to the following files:

%windir%System32PERFCxxx.DAT

%windir%system32PERFHxxx.DAT

where xxx is the basic language ID for the system, for example, 009 for English. These files may be missing or corrupted. If you suspect this, expand these files off of the installation CD.

2. Start Registry Editor, and then give the user at least READ access to the following registry keys:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Perflib

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSetControl\SecurePipeServers\Winreg

3. Give the user at least READ access to the following key and allow Read permission to propagate down to the Services subkeys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSetServices

4. With Windows 2000, in addition to the access described above, the user must also have access granted by the following Group Policies:

Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment

Profile System Performance

Profile Single Process

5. If the user is neither a power user or an administrator, additional permissions might be needed to access SysMonLog services. To grant full access to SysMonLog services, run the subinacl /service sysmonlog /grant=tester=f command, where tester is the user account.

If you still not able to remotely monitor disk counters, refer to Microsoft Knowledge Base Article 812714 – Users cannot remotely monitor disk counters if they are not logged on as administrators

Cannot get Window Resources, IIS, SQL, or ASP performance data from the Controller

The Controller’s Monitors -> Add Online Measurement dialog box does not show the "Web Service," "SQL Server," or "Active Server Pages" performance objects. Other application server performance objects show up from the Controller, but not these specific ones.

These objects are displayed when the user runs perfmon directly on the application server.

LoadRunner’s monitor requires permissions to the Web server’s registry and system files to access the Web service and other objects. Without these permissions, the Controller cannot "see" the performance data on the Web server.