General: Issue: Optical character recognition (OCR) does not work for multibyte characters. (38042) Workaround: None. Issue: The "What"s This" Help does not work on Windows Vista. (30163) Workaround: The Windows Help program WinHlp32.exe is no longer included with Windows Vista. A download for 32-bit .hlp files is available from the Microsoft Download Center. For more information, see: Performance Explorer: Issue: Compiling a MIB file does not work. (32039) Workaround: MIB files without an IMPORTS statement can not be compiled with Performance Explorer. Use the pre-compiled MIB files of Performance Explorer, or use MIB files with an IMPORTS statement. Issue: When an overview report is saved as MHT, images do not display when viewing the report with Internet Explorer 7. (32927) Workaround: View the report with Internet Explorer 6 or another browser. Issue: JMX Monitoring does not work on Windows 2003 systems that have Terminal Server installed. (31679) Workaround: None. The error has been reported to Eclipse; see bug #171413 on for more information. Issue: When monitoring performance counters on Windows 2003 or Windows XP systems, the "Browse NT Performance Counters" dialog sometimes displays the wrong host. (30163) Workaround: None. Since this is only a display error, you can still monitor performance counters on the target host. Issue: When using "Absolute" start time in the workload definition, the Overview Report will display data from the moment the test was set up rather than when it was started. (4988) Workaround: None. TrueLog Explorer: Issue: Oracle Forms TrueLog crashes after some transactions. (34040) Workaround: De-select the "Applet execution" setting in Settings -> Options -> Display -> HTML rendering. Issue: The rendered view of terminal emulation applications using non-ascii characters may display strange characters. (33416) Workaround: Change the default GUI font of the Workbench (Settings -> System -> Layout -> Font & Colors) to a font that better supports your character set. Restart TrueLog Explorer after changing the font to apply the settings to TrueLog Explorer. Issue: On-access virus scanner software may cause the TrueLog Explorer to crash. (32943) Workaround: Turn off the on-access scan functionality of your virus scanner software, or open a TrueLog in TrueLog Explorer after the test run has finished. Issue: TrueLog Explorer's Post Data and Form Data tabs may show incomplete form data if parameter types that require data type conversion (casting) are used for customization. (17060) Workaround: It is recommended to use parameters of data type "string" only for form data customization. Issue: TrueLog Explorer is unable to handle form submissions containing form fields with equal names. Tooltips in the Post Data tab may show incorrect data, value customization may result in customizing a wrong form field. (16807) Workaround: None. Issue: TrueLog Explorer crashes if more than 65k characters are selected in the Rendered tab. (17775) Workaround: None. Issue: Visual Script Modifications fail if the related transaction is in an include file. (10367, 16239, 19992) Workaround: Do not move transactions to bdh files. Issue: When the JavaScript execution is enabled, certain JavaScript statements inside the HTML contained in a TrueLog may lead to unexpected behavior in the TrueLog Explorer. For example, the JavaScript may close or resize the rendered HTML view in TrueLog Explorer. (4181, 5624) Workaround: Disable JavaScript execution (Settings / Options / Script execution). Issue: Certain non-ASCII characters may cause problems when customizing a script with TrueLog Explorer. For example, the HTML token "€" is rendered to the Euro symbol, ???. When selecting a text containing such non-ASCII characters and trying to insert a parsing or verification function, the TrueLog Explorer will respond with a message stating that the selected text is not contained in the visible part of the page's HTML code. (6482, 8085) Workaround: If you encounter this behavior, try to exclude such non-ASCII characters from the selection, and try again. Issue: TrueLog Explorer may crash if it is closed during an animated TryScript run, which may cause a memory access violation. This behavior only occurs with Microsoft Internet Explorer Version 5.00.3315.1000. Workaround: Install a newer version of MS Internet Explorer. Issue: Visual User Data Customization does not work for browser-level scripts. This behavior is by design as TrueLog Explorer only considers forms submitted by WebPageSubmit calls (Page-based Browser-level API), because the HTML form names are required to match HTML and BDL forms. Workaround: If you want to customize your script using TrueLog Explorer"s Visual User Data Customization feature, you have to have a page-based browser-level API script. Issue: Using the context menu (right mouse button) of the TrueLog Explorer you can view the Statistics reports of the TrueLog in the Web browser instead of in the TrueLog Explorer. However, the links in the Url column of the Page drill down section will not work in this case. This is by design, because the referenced HTML page is created on demand by the TrueLog Explorer. (7742) Workaround: Use the TrueLog Explorer to view the Statistics pages if you want to navigate between the different statistics pages via the links. SAPGUI Support: Issue: Replay a script fails with IDispatch error #619. This problem only occurs when you open a second session in SAP (recording "SapGuiCreateSession();", which results in an error on the following "SapGuiSetActiveWindow": "SapGui: 88 - An error occurred while setting the new active session., IDispatch error #619". SAP replay then hangs. This issue will be resolved in an upcoming patch. (38458) Workaround: Do not use the function SapGuiCreateSession and do not open a new session when recording. Issue: Recording SAPGUI actions on Windows XP 64-bit does not work. (37406) Workaround: None. 64-bit hooking is currently not supported. Issue: Errors occurr with SAPGUI client 640 when replaying scripts that use the picture control. (32431) Workaround: None. This control does not work in SAPGUI client 640. Issue: SilkPerformer"s SAP eCATT integration can be installed via SilkPerformer setup only after a SAPGUI client has been installed on the host machine. eCATT integration requires that some SilkPerformer files be copied to the SAPGUI client installation directory. If a SAPGUI client is not installed before SilkPerformer setup, the files cannot be copied. (23587) Workaround: Install SAPGUI client before installing SilkPerformer. Issue: Difference between Record and Replay TrueLog for SapGuiSelectTopNode calls: It is possible that a SapGuiSelectTopNode call during Replay occurs under the next Roundtrip node in the TrueLog compared to the Record Log. Workaround: None. Issue: SapGuiTreeChangeCheckBox is recorded incorrectly. Parameter sItemName is not scripted and parameter bChecked might not be recorded correctly. Workaround: Record the script with Log-Level Debug. Open the recorded log file and search for the SapGuiTreeChangeCheckBox call. Right above this call the 3 parameters for the call are listed. Copy the value for the 2nd parameter and use this value for the sItemName parameter. If bChecked is recorded incorrectly - change the parameter to true (if you have selected the checkbox) - otherwise change it to false. Issue: In rare cases control position information cannot be retrieved correctly from SAP. Therefore TrueLog Explorer might not be able to display the selected control rectangle at the correct position on the screenshot. Workaround: Use the control tree instead the screenshot. Citrix Support: Issue: Customizing CitrixKeyString input using multibyte characters sends corrupted input to the server. (37106) Workaround: When customizing input of CitrixKeyString functions, keep in mind that you are in fact simulating keyboard input. For multibyte characters, you have to enter the phonetic transcription of the desired character. There is no sense in entering a multibyte character directly, although the compiler will allow it if the codepage is set correctly. Issue: An invalid CitrixKey function is recorded for [hankaku/zenkaku] key. (37773) Workaround: Assign a different shortcut for switching between input modes or use mouse instead of keyboard shortcut. See Microsoft IME Advanced settings for details. Issue: On different operating system versions the text-conversion of an identical image may produce different results. (15982) Workaround: Use the identical OS on all agent computers. Issue: Screen synchronization/verification fails, if using an agent computer with a different color-depth than used on the controller machine during recording (Independent of the color-depth setting used for the Citrix session). Workaround: Apply the identical color-depth setting to all used computers. Issue: If the Citrix agent is used for the first time, a popup window prompts for the desired "ICA Client File Security". This is especially a problem when remote agents are used. Workaround: Log in to all used agents and confirm the dialog. Specify "Never ask me again for any application". Issue: If Caps Lock is pressed during a Citrix replay all virtual users send their keystrokes as if the Shift key is pressed. Workaround: Be sure that Caps Lock is not pressed. Issue: Using Windows XP or 2003, aborting a load-test may let the Citrix ICA clients (wfica32.exe) hang. Workaround: Manually terminate all hanging wfica32.exe or use Windows 2000 instead. Issue: If during recording more than one Citrix sessions are established using different screen resolutions, a script with more than one CitrixInit functions is recorded. This may lead to replay problems, because the CitrixInit function is executed just once per load-test. Workaround: One specific virtual user should only use one screen-resolution throughout its Citrix sessions. Issue: Connecting to an existing session during Citrix recording will result in not working scripts, because the Citrix client will not recognize any windows and therefore no synchronization functions will be scripted. Workaround: Always record a new session. Please click What are the known issues in SilkPerformer 2008 (Part2)? for Part 2 of the known issues.
↧