Wiki Page: Why am I unable to capture JMX measures during monitoring when I...
If this problem is affecting a Windows 2003 machine, it may be caused by the following known issue in SilkPerformer 2007 & 2008: JMX Monitoring does not work on Windows 2003 servers that have...
View ArticleWiki Page: What issues were fixed in SilkPerformer 2008R2?
The following issues are fixed in SilkPerformer 2008R2: Issue 36687: SilkPerformer reports a cache hit although the requested document has already expired. Issues 37206, 39736: record.log writes...
View ArticleWiki Page: Why does the SapGuiCloseSession() function not close all open SAP...
There is a known issue in SilkPerformer 2007 where the SapGuiCloseSession function does not work if "null" is specified as the parameter. Instead it is necessary to specify the actual session to be...
View ArticleWiki Page: Why do I get an installer dialog appearing when trying to open...
Occasionally, when starting SilkPerformer a dialog may appear saying "please wait while Windows configures or installs the required component". This can occur if the installer reports that the initial...
View ArticleWiki Page: Product Support Matrix - SilkPerformer SOA Edition 2008 R2
This describes the software with which SilkPerformer SOA Edition 2008 R2 was tested. System Area Tested With Operating system Windows 2000 with Service Pack 3 Windows 2000 (German) Windows XP with...
View ArticleWiki Page: Using wildcards in X-Path queries used by Browser-Driven Web Load...
All API calls that interact with DOM elements take XPath query strings as input parameters. Currently Silk Performer uses a subset of the XPath query language to identify DOM elements and wildcard...
View ArticleWiki Page: Error "The procedure entry point could not be found in dynamic...
This error can occur if a hotfix or patch has been applied to the wrong version of Silk Performer. Please review the ReadMe.txt within the hotfix or patch for the "Software requirements" section...
View ArticleWiki Page: SilkPerformer support for Windows 7.
Since the release of Silk Performer 2009R2 now runs under Windows 7, both 32bit and 64bit. Additionally, it makes full use of the Windows 7 new taskbar context menu. Along with the standard...
View ArticleWiki Page: Error "Could not start Java Hooking Engine, reason: cannot load...
When attempting to record, the recorder displays the message: "Could not start Java Hooking Engine, reason: cannot load jvm, unknown error". This can occur when the -Xms and -Xmx parameters are...
View ArticleWiki Page: Getting an ‘Agent Locked’ message when manually assigning agents
Silk Performer 2010 SP1 may report the message "Assignment of load to agents has failed because at least one of the agents is locked, unavailable, or has insufficient capabilities." if agents are...
View ArticleWiki Page: Silk Performer Help does not load as the primary Window
When Silk Performer Help is launched, the Help screen loads on the taskbar but does not get focus or brought to the front of the Silk Performer Window. This is actually caused by a Windows setting...
View ArticleWiki Page: AMF traffic is not displayed as XML in the Silk Performer TrueLog
AMF response data may not be XML formatted and displayed correctly in TrueLogs. This behaviour can occur if the Server's response header does not contain a "Content-Type: application/x-amf" element....
View ArticleWiki Page: The Select Region button of the Citrix Recorder does not allow...
To generate screen region synchronization during recording, the user must press the Select Region button on the SilkPerformer Citrix Recorder then click the mouse onscreen, draging it to select a...
View ArticleWiki Page: Unable to edit random data files within Silk Performer 2010.
When editing the file for the first time via SilkPerformer these changes are stored as expected. However, subsequent attempts to modify the data will result in the new data not being stored. This is a...
View ArticleWiki Page: "Warning: hooking not properly configured. PerfHK_Name environment...
This can occur if the environment variable PERFHK_NAME81 has been changed, deleted or become corrupt. Follow the steps below to check this environment variable: · Close the SilkPerformer Recorder and...
View ArticleWiki Page: What are the ST_PROJECT_TimerX timers generated when running a...
When running a SilkTest script, you may find Custom Timers called ST_PROJECT_TimerX which are not explicitly defined in the SilkTest script. These timers can be generated if the optional sTimerName...
View ArticleWiki Page: Is it possible to replace the default timer names with the...
By default the Silk Performer recorder uses the title of an HTML page for the timer name, or "Unnamed page" if no title exists. For example, in the following WebPageUrl call the title of the HTML page...
View ArticleWiki Page: Is it possible to automate session handling during the recording...
Silk Performer 2010 R2 will have built-in functionality that improves the automation of some session handling during the recording process. In order to avoid duplicate session errors when replaying...
View ArticleWiki Page: Is Browser-level API recording supported for use with Silk...
Browser-level API recording is not supported for use with Silk Performer Diagnostics (AKA dynaTrace). To test at the protocol level with Silk Performer Diagnostics enabled, Page-based browser-level...
View ArticleWiki Page: Correct behaviour of a "revisiting user" for Browser Driven Load...
In the Silk Performer 2010 Help there are conflicting statements regarding Browser Driven Load Testing (BDLT) user behaviour for a revisiting user. The second statement below is the correct one. This...
View Article