Obtaining the Latest Release Notes
Contacting Micro Focus Customer Care
If you accessed this document from the product CD, you may not be reading the latest release notes. For the most recent information, go to SupportLine, the Micro Focus Customer Care Web site. The first time you access SupportLine, you are required to register and obtain a password. After logging onto SupportLine, click the Product Documentation link and select your product from the list. You will find the latest release notes listed with the other product documentation.
On June 1, 2009, Micro Focus purchased Quality Solutions products from Compuware Corporation. Newbury, England-based Micro Focus provides enterprise application management and modernization solutions. Compuware and Micro Focus will continue to collaborate to ensure that customers receive uninterrupted service and obtain the full value of both companies’ product capabilities.
While service and product quality are continuous during this transition, there are a few changes to consider:
For the most recent product updates and information, go to SupportLine, the Micro Focus Customer Care Web site. You can find the Customer Care contact information posted for your specific location at www.microfocus.com/AboutMicroFocus/Contact/.
The default installation paths for the Quality Solutions products have changed from x:\Program Files\Compuware\<Product Name> to x:\Program Files\Micro Focus\<Product Name>. Correspondingly, the Start menu paths also have changed to reflect the move from Compuware to Micro Focus. If you have installed with a customized path that does not have Compuware in it, you will not experience any changes to the installation directory during migration.
QALoad can now record and playback against Adobe Flex applications that use the AMF data format, allowing users to test the latest generation of Web/RIA applications. AMF data is decoded and displayed in an easy-to-read tree-view format that allows users to view AMF data structures. Users can use QALoad's Visual Script interface to quickly and easily modify the scripts without requiring in-depth programming knowledge. Additionally, users can monitor and generate reports on Adobe server messages and Java server components in order to fully understand and tune the performance of Adobe Flex applications.
QALoad now installs an integrated compiler which allows users to compile WWW and Winsock EasyScripts. The integrated compiler removes the requirement to license and install Visual Studio for compiling scripts, lowering the cost of QALoad ownership.
QALoad now automatically replaces values in URIs which assist users in scripting complex Web environments. Users can now use QALoad's parameterizataion wizard to replace data (such as dynamic port numbers or session values) contained in URI. Rules can be created to fully automate the replacements when recording new scripts. These improvements further enhance users' ability to rapidly create robust performance testing scripts.
QALoad supports monitoring WebSphere 7 environments. Users can leverage WebSphere 7's Performance Monitoring Infrastructure in conjunction with their performance tests to understand WebSphere performance bottlenecks.
QALoad 5.9 is also day-1 compatible with Windows 7. Because Micro Focus expects to deliver QALoad prior to the general avaialbitliy of Windows 7, it may be necessary to deliver an update once the Windows 7 GA debuts.
QALoad has the following minimum system requirements:
User Locale affects how some programs format and display numbers, currencies, dates and time. QALoad only supports native operating systems locales. Switching your User Locale to something other than that of the native OS may result in improper functioning of QALoad components.
(*See the Technical Notes section for more information about using Windows Vista and IE 7.0.)
The system requirements for each individual QALoad component follow:
Visual Studio .NET 2003 (7.1), Visual Studio .NET 2005 (8.0), or Visual Studio .NET 2008 (9.0) for script compilation and script validation, or
Visual Studio Express 2008 for WWW script compilation and script validation. or
MinGW 3.4.5 for WWW and Winsock script compilation and script validation. This is installed by default with the product when Script Development Workbench is selected.
Note: Visual Studio Express 2008 supports WWW middleware only and MinGW supports WWW and Winsock middleware only. When in the Universal session, select only WWW for Visual Studio Express 2008 compilation or WWW or Winsock for MinGW compilation. If you plan to test middleware other than WWW or Winsock, you must install one of the supported Visual Studio .NET versions.
Note: See the Technical Notes section for more information about compiler compatibility.
cdo.dll
must be installed on the machine to use the send utility. CDO is an optional
messaging component of Microsoft Outlook. When you view the options for
Office or Outlook setup, CDO is listed under the options for Outlook.
Note: If you are using Microsoft Office 2007, you must download cdo.dll from the Microsoft website.
Java 2 Runtime Environment 1.5 or 1.6 for running Java scripts.
Mid-level Pentium 4 PC with 1GB of RAM.
The QALoad Player and associated utilities are supported on Linux and Solaris. Compilers that are 32-bit compatible are required. The system requirements for each operating system follow:
Micro Focus requires the Linux system-provided GNU GCC & G++ version 3.4.5 compiler for RedHat Enterprise Linux AS Version 4 and GNU GCC & G++ version 4.1.1 compiler for RedHat Enterprise Linux Version 5
ANSI C compiler for compiling scripts. Micro Focus requires Sun Studio 11 or 12. Micro Focus also supports GNU GCC & G++ compilers version 4.2.4.
In addition, your Windows system may need to meet specific requirements to support the middleware you will be testing. The Winsock middleware does not have any additional QALoad Windows Player requirements.
QALoad supports load testing of ODBC environments when the following requirements are met:
QALoad supports load testing under Citrix when the following requirements are met:
Citrix Web Interface 4.2, 4.5.1*, or 4.6*, or 5.0*
JavaScript set to Limited or None when using Citrix Web Interface 4.6 or 5.0
(*When running Citrix ICA client 10.x or 11.0 against the Web Interface 4.5.1 or later, the Web Interface site should not be set as a Trusted Site in Internet Explorer security settings, or the server should be set to have a preference for embedded ICA files. It may be necessary to change WebInterface.conf on the server from "LaunchClients=ICA-Local,ICA-Embedded" to LaunchClients=ICA-Embedded,ICA-Local". Also, when performing a QALoad recording in this configuration, an error message may appear on the Web Interface page indicating "An error occurred while making the requested connection." The error should have no effect on the recording and can be ignored.)
QALoad supports load testing under .NET when the following requirements are met:
Visual Studio 2005 with Microsoft .NET Framework version 2.0 SP1 or Visual Studio 2008
QALoad supports load testing under TestPartner 6.1, 6.2, and 6.3
Supports QALoad Windows Player only.
QALoad supports load testing under SAP when the following requirements are met:
Supports QALoad Windows Player only.
(Note: See the Technical Notes section for information about using Windows Vista.)
QALoad supports load testing under Oracle Forms Server when the following requirements are met:
Java 2 Runtime Environment 1.5 or 1.6
Note: Micro Focus recommends using the Java HotSpot Client VM
QALoad supports load testing of J2EE components when the following requirements are met:
QALoad supports load testing of WWW environments when the following requirements are met:
QALoad supports Flex under WWW when the following requirements are met:
Note: The JDK must be greater than or equal to the version used for any custom .jar files.
QALoad supports Streaming Media under WWW when the following requirements are met:
RealOne Player Version 10.x or Windows Media Player 9.00.xx.
Note: Windows Media Player is not currently supported on Windows Vista.
QALoad supports integration with ApplicationVantage version 10.1, 10.2, and 11.0.
Integration with ApplicationVantage is supported on the Windows platform only.
You must install the ApplicationVantage agent that is packaged with the QALoad software. The agent must be installed on the same Windows machine as the QALoad Player.
(Note: See the Technical Notes section for information about using Windows Vista.)
QALoad supports integration with the full installation of ServerVantage (SVI Monitoring) version 10.1, 10.2, and 11.0.
QALoad Remote Monitoring only supports integration with the version of ServerVantage shipped with QALoad.
For Performance Monitoring of Application Servers for JVM, OAS, SAP, WebLogic, WebSphere, WebSphere MQ, and WMI, you must install the ServerVantage agent that is packaged with the QALoad software. The agent should be installed on a non-production machine that does not currently have a ServerVantage agent installed.
QALoad supports integration with ClientVantage. QALoad is packaged with the current version of ClientVantage at time of release.
QALoad supports integration with Vantage Analyzer 10.1 SP1, 10.2, and 11.
The following environments and middlewares are not supported in QALoad release 5.9:
Windows 2000
To migrate previous QALoad OFS scripts for use with QALoad 5.9, recompile the scripts.
To migrate previous QALoad Java scripts for use with QALoad 5.9, manual change the following namespace:
To migrate previous QALoad .NET scripts for use with QALoad 5.9, manual change the following namespace:
Do not use \, /, :, *, ?, ", <, >, |, ^, # in the file name when using MinGW Compiler. If a file name contains a special character, the compile process will fail.
In order for WWW or Winsock C-scripts generated prior to QALoad 5.9 to work with MinGW, update the rhobot_script function statement as follows:
int rhobot_script(PLAYER_INFO *s_info)
or
int rhobot_script(s_info)
PLAYER_INFO *s_info;
#ifndef __MINGW__
int rhobot_script(PLAYER_INFO *s_info)
#else
extern "C" int rhobot_script(PLAYER_INFO *s_info)
#endif
If using Security-Enhanced Linux (SELinux), perform the following procedures to allow QALoad to run in this environment. In these procedures, <installDir> is the fully-qualified name of the directory where QALoad is installed on your Linux system.
Log on to the Linux system.
Change directories to <installDir>/lib.
Type chcon -t textrel_shlib_t lib*.so.
Log onto the Linux system.
Change directories to <installDir>.
Type chmod 755 Rmake.
Open the Rmake script in your preferred editor, and find the function, setupLinux().
At the bottom of the function, find the section, Create the normal link command.
Add the following statement as the last line in
this section:
LINK=”$LINK; chcon –t textrel_shlib_t $TGT_SHARED_LIB”
Save the Rmake script and close the editing program.
Type chmod 555 Rmake.
Additionally, if using SELinux, open the ports that your have designated in the Conductor using the SELinux management tool.
Regardless of what operating system you are using to run QALoad Players, if there is a firewall in your environment, open the UDP and TCP ports that you have designated in the Conductor.
Using XenApp Plugin (Client) Version 11.x with QALoad Workbench
When installing the XenApp Plugin for Hosted Applications, install the Program Neighborhood option to allow QALoad access to published applications on XenApp servers.
When capturing against a secure site, you may receive security alerts. To avoid security alerts, import the QALoad cacert.pem certificate and set the trust option to allow this certificate to identify websites. The cacert.pem certificates is located in the <installation path>\QALoad\Certificates directory. Refer to your browser help for further information on importing certificates and setting the trust option.
There is a bug with McAfee Virus Scan 8.5 patch 1 where it resets the reboot flag. QALoad installation checks for a reboot flag and prompts the user to reboot. Consequently, the combination of McAfee resetting the flag and QALoad checking for the flag creates an infinite loop. To avoid this loop, install a later patch of McAfee Virus Scan 8.5. If you do not have McAfee Virus Scan 8.5 Patch 1 and you still receive a reboot message, refer to the Reboot Known Issue.
Note the following considerations with Microsoft Windows Vista:
The use of Compuware ServerVantage Agent in Admin mode or Compuware ApplicationVantage Agent on the Microsoft Vista platform is not currently supported. To use these integrations, you must be running Conductor on Windows XP, Windows Server 2003, or Windows 2008.
When you install the Compuware ApplicationVantage Agent on Microsoft Windows Vista, the following Windows security dialog box appears during file transfer: “Would you like to install this device software?” Click Install.
For SAP middleware replay on Windows Vista, SAP GUI 7.10 patch level 6 or later is required.
Currently, Oracle Forms does not support Windows Vista.
Windows Media Player is not currently supported on Windows Vista.
If you are using QALoad on Microsoft Windows Vista, you must make the following configurations for proper operations of capturing in Winsock, performance monitoring, and Remote Monitoring for SNMP and Windows Registry:
When using the Winsock middleware with Internet Explorer 7.0 or 8.0 on Vista, the Enable Protected Mode setting must be disabled. This option is managed in IE7 and IE8's Internet Options on the Security tab.
When using the WWW middleware with Internet Explorer 7.0 or 8.0 on Vista, the Enable Protected Mode setting must be disabled. This option is managed in IE7 and IE8's Internet Options on the Security tab.
When using any monitoring capabilities, the logged in user must be a member of the Performance Monitoring Group.
When using SNMP monitoring, you must enable the following options:
Enable SNMP feature.
Enable the SNMP service.
Specify an appropriate community.
Assign access rights to SNMP.
Enable access to SNMP through the firewall.
To enable Windows Registry remote monitoring, you must start the Remote Registry service (defaults to manual startup in Vista).
When you install QALoad on a Windows machine, the Windows Firewall is automatically configured to include various QALoad .exe's as an allowed exception. This configuration is required for communication between the Conductor and Player machines during a load test.
If you are migrating from a previous version of QALoad, you must re-compile your existing scripts in the Script Development Workbench to use them in this release.
When using QALoad, do not use the "Switch User" Windows feature. Using this feature allows multiple user sessions to be active simultaneously, which can cause problems with script playback. If you need to use a different Windows profile, log off Windows and log on as a different user.
certdb.txt for OFS recordingFor the SSL support provided in this release, QALoad modifies
the client machine's JInitiator certdb.txt file to include
QALoad's CA certificate during the initial SSL recording process
for an Oracle Forms Server application. This certificate authority information
is internally validated by Oracle during the OFS-SSL session. If you want
to remove the QALoad CA certificate, delete the following text
from the certdb.txt file:
#qaload
-----BEGIN
CERTIFICATE-----
MIIC1jCCAj+gAwIBAgIBADANBgkqhkiG9w0BAQQFADBXMQswCQYDVQQGEwJVUzER
MA8GA1UECBMITWljaGlnYW4xEDAOBgNVBAcTB0RldHJvaXQxEjAQBgNVBAoTCUNv
bXB1d2FyZTEPMA0GA1UECxMGUUFMb2FkMB4XDTA1MDYyMzE3MDEyN1oXDTE1MDYy
MTE3MDEyN1owVzELMAkGA1UEBhMCVVMxETAPBgNVBAgTCE1pY2hpZ2FuMRAwDgYD
VQQHEwdEZXRyb2l0MRIwEAYDVQQKEwlDb21wdXdhcmUxDzANBgNVBAsTBlFBTG9h
ZDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA07Q/tlwx4wQezY5UY92v+NdQ
WI1yjlbWrkFFBTVWtvb/M+SdHGHXntDxGF378058hHND95wQsADCnJmPQNIoqj1c
elHl+4hkMtioMSb8IiEMs4OCgOaoBTtFrRgffZxoWJHAlh2k/MUcbFc1oiSZGdcT
Ua7keQ5NtahHRputc0MCAwEAAaOBsTCBrjAdBgNVHQ4EFgQUXUtOUAp/U8TV4p75
AA8ybai1080wfwYDVR0jBHgwdoAUXUtOUAp/U8TV4p75AA8ybai1082hW6RZMFcx
CzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjEQMA4GA1UEBxMHRGV0cm9p
dDESMBAGA1UEChMJQ29tcHV3YXJlMQ8wDQYDVQQLEwZRQUxvYWSCAQAwDAYDVR0T
BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQBEmh3S2ktyRu7pn9PaqgZS2v1o2PhH
5XYZI8YKs9ZeWJotebtgmu/5xJj4I48neWE45kA/akYbUsW491UEZ609Pf2cw3JO
xBZ8MOyT7z3RzAhBFe8CpHrQjmc6Vh8Mzcv6vVYRCDlIGlk2CguQ3WQWF8w3zNA/
I53OD9PZjisIlA==
-----END
CERTIFICATE-----
#qaload
To use the SAP or Citrix middleware, you must ensure that the VC++ MFC and Template Libraries option is selected when you install Visual C++. This option installs the headers, libraries, sources, and browser database for MFC and ATL, which are required for both the SAP and Citrix middleware.
To prevent performance issues, Micro Focus recommends that you increase your system paging file size to a fixed size:
Micro Focus recommends that you turn off the IE 7 or IE 8 Anti-Phishing Filter to avoid inaccurate test results.
To support Internet Explorer 8.0 with QALoad Winsock middleware, perform the following:
IE 7 introduced methods for gathering additional information for ActiveX controls which are missing details and lack fully defined codepaths. IE now queries Microsoft's own ActiveX repository to look for additional detail as well as other sites based on information gathered from the control.
You should decide if these additional requests are desirable for your testing scenario in QALoad and create traffic filters to reflect your preferences. You may find your test results are more consistent if you add http://active.microsoft.com/ to the Blocked Traffic filter.
In order to successfully test Siebel with Internet Explorer 7.0, you must modify the following settings:
Note: Siebel does not support Internet Explorer 8.0
For all Windows Environments:
For Windows Vista only:
In addition to the steps above, you must disable the Enable Protection Mode setting for Internet, Local intranet, Trusted sites, and Restricted sites with IE 7.0. By default IE8 disables Protected Mode in the Intranet Zone. You will have to disable it for all the other zones.
In the IE browser window, go to the Tools menu, and select Internet Options>Security.
Under Select a zone to view or change security settings, select Internet.
Under Security Level for this zone, ensure that the Enable Protected Mode is not selected.
Repeat for Local Intranet, Trusted sites, and Restricted sites.
Click OK.
QALoad JavaScript support requires that all form elements (for example, buttons and text fields) must be inside of HTML forms in order to execute associated JavaScript. JavaScript that depends on time or date information may require the user to parameterize the script. QALoad's windowless replay does not support certain specific JavaScript functions listed below.
setTimeout
clearInterval
clearTimeout
setInterval
showHelp
showModalDialog
showModelessDialog
As of QALoad 5.5.1, modified Citrix scripts should not have waitpoints placed directly after BEGIN_TRANSACTION markers. For best use of system resources, Micro Focus recommends that you place DO_SetTransactionCleanup before the END_TRANSACTION marker.
When setting up remote monitoring to capture and report ServerVantage data, you can now configure the port used for the SQL Server database. The Configure Monitor Dialog in the New Monitoring Task wizard, now includes a field for Database Server Port, so that you can override the default SQL port, 1433.
This section describes known issues related to the current release of QALoad.
A known issue exists with the Microsoft Operating System that may cause new programs to appear behind other already open programs. When you start a program from another program, the new program window may appear behind all other open windows. Additionally, the new-window icon flashes on the taskbar. This symptom occurs on a Microsoft Windows XP-based computer. Microsoft has documented a procedure that details how users can modify the value of the ForegroundLockTimeout registry entry in Registry Editor to correct the issue. For specific instructions and more information on this issue, please refer to the following article located at the Microsoft Help and Support website for details: http://support.microsoft.com/default.aspx?scid=kb;en-us;886217
When upgrading to QALoad 5.8, a .dll file is loaded in memory. To release the file, click yes to reboot through the error message. Do not perform a manual reboot as it will not release the file and the error message will reappear. The warning message that appears is:
"Setup has detected a previously installed QALoad file is loaded in the memory. A system reboot is required to free this file and continue with the installation.
To reboot the machine and continue with the installation, click ‘Yes’. To abort the installation, click ‘No’."
If you have uninstalled all previous versions of QALoad but the installation process indicates that a previous version of the product is still installed, you may need to remove a registry key. In the Windows Registry Editor, delete the following registry keys if they exists on your system:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90C9114B-ED44-4AB9-B32F-1B9EA363FBEF}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A04EA354-388F-4235-A3A0-B49B11F43DAE}
When you are installing or re-installing QALoad, you may be required to reboot your system before installation proceeds. You will be prompted with the following message :
"Setup has detected a pending system reboot from a previous install. A system reboot is required to continue with the installation.
To reboot the machine and continue with the installation, click ‘Yes’. To abort the installation, click ‘No’."
If you are unable to install QALoad because of recurring requests to reboot your system, you should do the following:
In the Windows Registry Editor, go to the registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Delete the data in the string PendingFileRenameOperations.
Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
If you have McAfee VirusScan 8.5 patch 1 installed on your machine and you continue to receive the reboot message, refer to the McAfee VirusScan 8.5 Technical Note.
If you are running McAfee's VirusScan 8.0 with the "Buffer Overflow Protection" option enabled, Internet Explorer may fail to launch when you start a Winsock recording or when you record OFS socket mode. To prevent this issue, disable the "Buffer Overflow Protection" feature within McAfee VirusScan.
If you are running your application with Internet Explorer, Micro Focus recommends you turn off the 'pop-up blocker' feature before recording a transaction. The feature can be disabled using the browser window's Tools menu in Internet Options>Privacy.
If you switch JDK versions after validating an AMF script, the Workbench crashes. To avoid this issue, switch JDK versions, then restart the Workbench.
Out of memory errors appear during replay when using extractstring for AMF scripts. To avoid these errors, reduce the number of threads per player or run in process mode.
The Send utility in Analyze does not always work properly with Outlook 2003. If you experience problems when clicking the Send button in the email that is generated by the utility, you can use the utility to create a .zip file of the results and manually attach that file to an email you create directly in Outlook.
Timing file names containing multi-byte characters do not display the file name correctly in Analyze tabs. The multi-byte characters are removed from the name and, if containing all multi-byte characters, the tab reads “TimingFile.tim”. Annotation Objects for Graphs do not support MBCS either, so some characters may be displayed incorrectly in annotation object text for languages utilizing MBCS.
In order to properly record monitoring tasks for Windows Registry and WMI monitoring types, you must have installed the following:
For Windows Vista - You must install Microsoft Windows Vista SP1 on the client machine.
All other supported operating systems - You must install Microsoft .NET Framework version 2.0 SP1 on the client machine.
Note: Although service packs are not typically required for target machines, Microsoft recommends that these service packs be installed on both source and target machines.
When running HTTP and HTML scripts together in thread mode, you may receive the error message:
WWW_ABORT_00009 - Script was converted in HTTP/HTML mode. Replay mode does not match the convert mode.
To avoid receiving this error, set the number of Virtual Users per process to the lowest number of VUs specified for all the scripts in the session.
There is a network/configuration issue with Citrix client v. 10.150 that can cause an intermittent Protocol Driver Error. This error has been reported when attempting to connect to Citrix Web Interface (CWI) applications or when validating CWI scripts in QALoad. To avoid this, either turn off the "Use automatic configuration script" option in Internet Explorer LAN Settings, or un-install client version 10.150 and upgrade to client version 10.2. If the problem continues, Micro Focus recommends that you contact Citrix.
When you select Repair for ServerVantage in the Add/Remove Programs utility, you must stop the ServerVantage Agent and disable the service.
User Locale affects how some programs format and display numbers, currencies, dates and time. QALoad only supports native operating systems locales. Switching your User Locale to something other than that of the native OS may result in improper functioning of QALoad components.
When opening a .NET session in the Workbench, an error message stating the addin failed to install appears. To avoid this message, launch Visual Studio once outside of QALoad and configure it for C# scripts when prompted.
QALoad supports load testing of Traditional Chinese, Simplified Chinese, Japanese, and Korean Web applications that use Double Byte Character Sets (DBCS). Viewing timing files and Summary reports with International versions of Microsoft Windows is only possible if the timing file is viewed on the same Windows language platform on which the timing file was created.
A file descriptor limit exists on the Solaris platform if a script is running in threaded mode, logfile generation is turned on, and there are more than 250 virtual users. To avoid this limitation, modify the Logfile Generation parameters so that logfiles are not generated by all virtual users:
The Visual Navigator's Find/Replace functionality will not find and replace XML tree items.
The Checkpoint view may be blank when applying an existing saved template.
If you are running a Japanese Operating System, you may see invalid characters in the file names in the drop-down list on the Series tab of the Conductor Runtime Graph. There is no known resolution at this time. The improper interpretation of the characters involves a third-party tool that the software uses to display this information. Check SupportLine for future updates to resolve this issue.
There are limitations to the size of a Central Datapool that the QALoad Conductor can handle when starting a test. When attempting to use a Central Datapool file that is approximately 20MB or greater, the QALoad Conductor may fail to start. To avoid this problem, create a smaller Central Datapool file, or use a local or shared Datapool for the test instead.
In Windows XP SP2 and Windows 2003 Server environments, you may experience problems with receiving the following error message during installation:
"The instruction at 0x... referenced memory at 0x00000000. The memory could not be written"
If you receive this message during installation or if your applications crash while capturing, perform the following steps:
Right-click on My Computer and select Properties.
Click the Advanced tab and select Settings in the Performance field.
Click the Data Execution Prevention tab. By default, it is set to guard system processes. To stop your application from crashing, click the second radio button Turn on DEP for all programs and services except those I select.
Add the link to your program's executable file (.exe) to the list of programs that are allowed. Add the following executable files: iexplore.exe, javaw.exe, webproxy.exe, wsockexe.exe, MSIExec.exe.
Restart your machine.
QALoad may not capture WWW content correctly, or WebProxy may intermittently fail while capturing on a Microsoft Windows Server 2003-based computer or Windows Server 2008-based computer. For example, you may receive the following Application Error while capturing WWW with Microsoft Internet Explorer, "The instruction at 0xzc8224b2 referenced memory at 0x00000001. The memory could not be read."
This can occur when the Internet Explorer Enhanced Security Configuration component is enabled, which is the default state in Internet Explorer on Windows Server 2003-based computers and Windows Server 2008-based computers. This can prevent certain Web sites from displaying as expected in Internet Explorer. Programs that require the browser also may not work as expected because scripts, ActiveX controls, and download capabilities are disabled.
To avoid this behavior on Windows Server 2003-based computers, use the following steps to remove the Internet Explorer Enhanced Security Configuration components in Windows Server 2003:
Click Start, then select Control Panel.
Double click Add or Remove Programs.
On the left side of the screen, select Add/Remove Windows Components.
In the Components list, clear the Internet Explorer Enhanced Security Configuration check box, then click Next.
Click Finish.
To avoid this behavior on Windows Server 2008-based computers, user the following steps to remove the Internet Explorer Enhanced Security Configuration components:
Click Start>Settings>Control Panel.
Click Programs.
On the left side of the screen, select Turn Windows features on or off.
In the Security Information section, click Configure IE ESC.
Click Off for both Users and Administrators.
Click OK.
The Internet Explorer Enhanced Security Configuration component configures security settings that define how you browse the Internet and your corporate intranet, and helps reduce exposure of your server to Web sites that could pose a security risk. For more information about this component, refer to Enhanced Security Configuration>Internet Explorer Enhanced Security Configuration in the Internet Explorer help on your Windows Server 2003-based computer and Windows Server 2008-based computer.
In the Visual Navigator, when you click a Page Node that has JavaScript content that causes the same page to reopen recursively, the QALoad Workbench may disappear. This also occurs when you open the same Web page in Microsoft Internet Explorer. The C++ script that is generated compiles and executes properly, but no modifications can be made on the page in Visual Navigator. To make modifications to the C++ script, use the following steps:
In the Workbench menu bar, select Visual Navigator>Create Editable Script File...
In the Save As dialog box, type a name for the script file, then click Save.
Edit the C++ script file.
When upgrading to a newer version of QALoad, using the "Run as Administrator" feature in Windows XP and Windows Vista may cause the upgrade to fail. Use one of the following options to perform the upgrade:
Manually stop the Player agent by right-clicking the tray icon and selecting Stop Player Agent.
OR
Login to Windows using an account with Administrative rights.
OR
Uninstall your current version of QALoad before installing the new version.
Micro Focus Customer Care can assist you with all issues, from installation to troubleshooting.
Prior to contacting customer care, gather the following information:
1-800-538-7822
Refer to the Micro Focus SupportLine support web site for fast access to critical information about your product. You can read and print documentation, download product fixes, review frequently asked questions, or directly e-mail Micro Focus with questions or comments. The first time you access SupportLine, you are required to register and obtain a password.
Refer to Micro Focus's corporate web site at https://www.microfocus.com/ for information about Micro Focus customer support policies and problem resolution process. For contact information for your specific location, refer to www.microfocus.com/AboutMicroFocus/Contact/.
End
of QALoad Release Notes
Copyright © Micro Focus (IP) Limited 1998-2009. All rights
reserved. The software and information contained herein are proprietary to, and
comprise valuable trade secrets of, Micro Focus (IP) Limited, which intends to
preserve as trade secrets such software and information. This software is an
unpublished copyright of Micro Focus and may not be used, copied, transmitted,
or stored in any manner. This software and information or any other copies
thereof may not be provided or otherwise made available to any other person.