SilkPerformer^® 2007 Release Notes Add-On

View the SilkPerformer 2006 R2 Release Notes Add-On.

This file contains important information that may not appear in online Help. Read this file in its entirety.

Tested Software

This section describes the software with which SilkPerformer 2007 was tested.

Resolved Defects

The following are resolved defects in SilkPerformer 2007.

Known Issues

This section contains lists of known issues and provides workarounds where available:

Topics:

• General
• Performance Explorer
• TrueLog Explorer
• SAPGUI Support
• Citrix Support
• Oracle Forms Support
• .NET Support
• Java Support
• Web Support
• Database Support
• ADO/COM Support
• Streaming Support
• GUI-Level Testing Support
• Workbench
• Monitoring
• Recorder
• Licensing
• Setup
• SilkCentral Test Manager Integration
• SilkPerformer Source Code Control Integration

General:

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: http://support.microsoft.com/kb/917607

Performance Explorer:

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 https://bugs.eclipse.org/bugs/ 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.

Issue: Older speed stepping CPU's may falsify high resolution timer. High resolution timer are dependant on the CPU steps. (25115)
Workaround: Disable speed stepping or don't use high resolution timers.

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: It may occur that a "File download" dialog pops up when viewing a TrueLog in the TrueLog Explorer. (7974)
Workaround: There is a mechanism integrated in the TrueLog Explorer that allows custom handling of special content types and/or URL file extensions.
This behavior can be changed by adding custom content-types and/or file extensions to some values in the Registry.
The relevant settings can be found in the Registry (HKEY_CURRENT_USER\Software\Borland\Silk TrueLog Explorer\7.5).

The following four registry values exist, among others:

• MaskContentTypes
• MaskExtensions
• SuppressContentTypes
• SuppressExtensions

These values contain lists of content-types and file extensions that need special handling. The Mask* values apply to textual data, which can be "rendered" as plain text in the HTML view. The Suppress* values apply to binary (non-textual) data, which cannot be properly rendered.

Steps to suppress the download dialog:

• Select the node where the download box pops up.
• Examine the in-hdr view. If the content-type seems unfamiliar, such as app/fireclick.x-hint.1, close the TrueLog Explorer, add this content-type to the MaskContentTypes value (strings are separated by semicolons), and start the TrueLog Explorer again (the registry settings are read on startup only). If the download box still pops up, add the previous content-type to the SuppressContentTypes value. The download box should not appear anymore, and you have finished.
• If the content-type seems ok, examine the URL. If you notice an extension other than .html, .js, .pl, .chtml, .jar, .class, or .vbs, examine the in-data view to see whether the response body consists of textual or binary data. If you see textual data in the in-data view, add the URL file extension to the MaskExtensions value. If the data seems to be binary, add the file extension to the SuppressExtensions value (extension again separated by semicolon). Again, note that you have to add the extension to the Registry value only after you have closed the TrueLog Explorer. Restart the TrueLog Explorer.

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 the TrueLog Explorer. For example, the HTML token "& e u r o ;" 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: When Customizing session information in a browser-level script with TrueLog Explorer, a WebParseResponseData function may be inserted at the wrong position within the script (i.e. before the corresponding WebUrlBeginPage function). This only happens for browser-level scripts which have been generated (recorded) with the options "Browser-level API (HTTP)" and "Automatic page detection" (Profile Settings/Record/Web/Recording) enabled.
Workaround: Do one of the following:

• Move the generated WebParseDataBound function to the correct line in the script just before the BDL function, which returns the session information).
• Disable Automatic page detection (if you need to have a browser-level script), re-record the script, and try session information customization again.
• Switch to page-based browser-level script generation, re-record the script, and try session information customization again.

Issue: TrueLog Explorer may have problems when a BDL script contains more than one API call per line (7486). TrueLog Explorer assumes that there is at most one API call per script line. Trying to insert visual verification or parsing functions with TrueLog Explorer on such a script may result in unexpected replay behavior (e.g., session customization may not find the session info, etc.)
Workaround: Stick to this convention and do not place more than one API call into a script line.

Issue: Under rare circumstances, a content verification function inserted with TrueLog Explorer may lead to false verification results, because the automatically determined boundary strings may not be appropriate for the selected text.
This behavior only occurs when all of the following conditions are met:
- The selected text (which is to be verified) is inside an HTML input control.
- The checkbox "Require boundary strings" is checked.
- The selected text occurs somewhere else in the respective page.
The problem is that the optional boundary strings are determined for the first occurrence of the selected text. So, if the selected text in the INPUT control also occurs somewhere else before the selection, the boundaries will be determined for the first occurrence of the selected text, and not the selected occurrence.
Workaround: You can either insert a verification without boundary strings, or use a data verification, which can be inserted via the Source tab.

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.

Issue: Visual user data customization may not work properly with Internet Explorer 5.0 HTML form control highlighting (the red and green borders) in TrueLog Explorer's Post Data view may not work reliably when Internet Explorer 5.0 is installed. (8185)
Workaround: Upgrade to Internet Explorer 5.5 or higher.

Issue: Customizing API functions in include (.bdh) files.
Script customization does not work if the section of the script which needs to get customized resides in an include (.bdh) file.
Example: The main script calls the function Lab(), which is declared in limfuncs.bdh. Inserting verifications for http://lab1 in TrueLog Explorer will result in an incorrectly placed verification function inside the main script.

  
benchmark Limitation
	  use "limfuncs.bdh"
      dcluser
       user
        VUser
        transactions
          TMain : 1;
      dcltrans
        transaction TMain
        begin
          Lab();
        end TMain;
      Include file (limfuncs.bdf):
      use "WebAPI.bdh" 
      dclfunc
        function Lab
        begin
          WebPageUrl("http://lab1");
        end Lab;

Workaround: Move those functions that actually request the documents which you want to parse or verify into the main script.

SAPGUI Support:

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: SAP replay is memory leaking due to certain SAPGUI client versions.
Workaround: Use the latest patch version.

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: 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.

Oracle Forms Support:

Issue: JDK version prior to 1.4 do not provide the necessary functionality for replaying and recording Oracle Forms.
Workaround: Use the latest JDK. At least version 1.4.

Issue: Hooking into the main Oracle Forms Applet classes might cause the JInitiator to be unable loading additional jar files that rely on the main classes.
Workaround: When recording Oracle Forms 6i or Oracle Applications 11i define the following Java Runtime Options in the JInitiator Properties Dialog:
"-noverify -mx128m"
NoVerify will prevent these loading issues.
Additionally the default Virtual Memory Size of JInitiator 1.1.7.x is between 16 and 64 MB. The option -mx128m will increase the virtual memory size to 128MB. This additional memory is needed as there is some extra memory overhead caused by recording. If you run into a OutOfMemory error you can further increase this value.

Issue: When recording Oracle Forms 6i, on either HTTP or Sockets, the jitting library of the Java Virtual Machine (symcjit.dll) may crash your browser.
Workaround: Disable the JInitiator JIT (Just In Time Compiler) Option. Review the Oracle Forms Tutorial or the Advanced Concepts Book about how to accomplish this.

.NET Support:

Issue: .NET Explorer projects can not be opened in .NET Explorer when running with a lower version of the .NET Framework than the one used to create the project. Example: When creating a .NET Explorer project with .NET Runtime 2.0, the project cannot be opened in .NET Explorer when running .NET Runtime 1.1. (27249)
Workaround: None.

Issue: A .NET Framework project will not execute successfully if the two depending DLL's (perfdotnetfw.dll and dnlogging.dll) are not in the data file section of the project or not in the project directory. When creating a .NET Framework project – either with .NET Explorer or with Visual Studio .NET Project Wizard – these two files are copied to the project directory but are not added to the data file section. When exporting the project or uploading it to SilkCentral Performance Manager, these two files will be missing during executing and you will receive an error that a depending DLL could not be found. (25472)
Workaround: Add the two depending .NET Framework DLL's perfdotnetfw.dll and dnlogging.dll to the data file section of your project before you export or upload the project.

Issue: The Visual Studio 2003 (VS2003) Add-In does not work if SilkPerformer version 7.2 or lower is installed on the same computer. Parallel installations of the VS2003 Add-In are only supported for SilkPerformer versions 7.3 or higher. (27277)
Workaround: Remove any SilkPerformer installations of version 7.2 or lower.

Issue: Accessing a WSDL file from a secure web site (https) might throw an error if the Web Service is hosted on IIS 6.0. The error message that will be displayed is “Could not establish trust relationship with remote server“. (24546)
Workaround: Download the WSDL file with your browser and save it to your file system. Then load the WSDL file from the stored file instead of the URL.

Issue: Running multiple instances of Visual Studio .NET with the SilkPerformer .NET Add-In might cause Visual Studio .NET (devenv.exe) to crash.
Workaround: Run only one instance of Visual Studio .NET

Issue: If additional .NET languages (C#, VB.NET, C++) are added to Visual Studio .NET, the SilkPerformer .NET Add-In Wizards do not work properly anymore.
Workaround: Re-install the SilkPerformer .NET Add-In.

Issue: When creating an Individual String random variable with SilkPerformer's Visual Studio .NET Add-In in a VB.NET Project, the generated RndInd declaration is not compilable and will also prevent the Add-In from creating further random variables.
Workaround: Replace backslashes ('\') with a quote (") in the generated RndInd declaration.

Issue: Not all .NET Samples run on machines with just .NET Framework 1.1 installed. Exceptions might be thrown.
Workaround: .NET Framework 1.0 needs to be installed in order to run the .NET Samples that ship with SilkPerformer. Can be installed parallel to 1.1.

Issue: Visual Studio .NET might crash on systems with Microsoft .NET Framework 1.0.
Workaround: Install Microsoft .NET Framework 1.0 Service Pack 1 or Microsoft .NET Framework 1.1 (recommended). You can find the service pack and the .NET Framework 1.1 on the SilkPerformer installation CD (%CD root%\\redist\dotnetruntime\) or at Microsoft MSDN (http://msdn.microsoft.com/netframework/).

Issue: If SilkPerformer .NET Explorer calls a WebService method and passes parameters via call by reference, the generated .NET code misses the ref keyword in the function that calls the Web service method. (8173)
Workaround: Specify the ref keyword for the parameters that are passed by reference.

Issue: Random Variable Wizard in Visual Studio .NET can only be used for C# and VB.NET Projects.
Workaround: For Managed C++ applications, random variable definitions have to be coded manually by applying the random variable custom attributes to the virtual user class.

Issue: Outgoing parameters in .NET test driver methods do not return their parameter when called from BDL.
Workaround: Do not call .NET methods that use outgoing parameters from BDL.

Issue: Methods that return a value of a public class/interface that is actually an object of a protected or private class implementing this base class/interface, can be called but the result cannot be stored in a variable. It would result in a non-compileable .NET code as a variable of the private class will be scripted instead of the public class/interface. (12449)
Example:
interface IComparable {}
private class PrivateImplementation : IComparable {}
public IComparable GetComparableObject() {return new PrivateImplementation();}
The method GetComparableObject can be called but the returned value cannot be stored in a variable as it would result in a non compilable .NET code.
Workaround: None.

Issue: It is possible to use an integer random variable with a range that exceeds the possible range of the parameter's data type where the value is used. Example: You can use a integer random value in the range from 1 to 1000 for a System.Char value that only allows a range from 1 to 255. If a random value is generated that exceeds the upper bound, the method cannot be called. (12458)
Workaround: Be sure to use random value boundaries that fit in the boundaries of the underlying data type.

Issue: The Web Settings dialog (Visual Studio .NET Add-On) - that allows to change the base class of web proxies in order to route the HTTP traffic over SilkPerformer's Web Engine - cannot be used for managed C++ projects. (12472)
Workaround: You have to change the base class of the web service proxy manually to "System.Web.Services.Protocols.SoapHttpClientProtocol" if you do not want to route the traffic, or to "SilkPerformer.SPSoapHttpClientProtocol" to route it over SilkPerformer's Web Engine in order to get a TrueLog for every Web Service call and to be able to use the features like Modem Simulation, IP Multiplexing, ...

Issue: Exporting a .NET Explorer project containing Web Service calls to a Web Service using a different SOAP-Stack than .NET can cause problems if:
* the return value is an array of complex objects and
* the return value is stored in a variable and
* the return value is used as input value for following calls
(14940)
Workaround: Export the project as SilkPerformer .NET Project.

Issue: NUnit Tests of older versions (1.x) cannot be imported as Unit Tests in SilkPerformer.
Workaround: They can be imported as normal .NET classes in order to call the test methods.

Java Support:

Issue: Weblogic 8.x monitor does not work with JDK 1.5. (28863)
Workaround: Use JDK 1.4.

Issue: Axis 1.2.1 and Axis 1.3 treat some datatypes like String[] differently. While Axis 1.2.1 generates an ArrayOfString helper class, Axis 1.3 directly works with String[]. Thus, existing Java Explorer projects using these problematic datatypes cannot switch Axis version. (29343)
Workaround: Create a new project for each version.

Issue: Java Recording of IBM Java VM: "automatic" doesn't work.
Workaround: The startup script of the client application must be manually edited to allow recording.

Issue: Loading jar files may take a long time. All jar files from the class path must be loaded and examined by Java Explorer at this time. This process cannot be interrupted. (11280)
Workaround: None.

Issue: Adding a directory to the class path by double-clicking the directory within the file browser will add a wrong classpath. (11862)
Workaround: Click the directory once and use the "Open" button.

Issue: A low invocation delay between method calls may cause an exception stack trace in the log file. The exception relates to the fact that the GUI cannot update as fast as needed. However, this doesn't cause any further problems. (12359)
Workaround: None.

Issue: A standalone console application cannot be compiled when JDK 1.2.x is used as current runtime version. This issue is related to a JDK 1.2.x limitation. (12484)
Workaround: Use a JDK >= 1.3.x.

Issue: Due to a bug in the MS .NetFramework 1.0 some WebServices using custom SOAP headers cannot be tested with Java Explorer. (12209)
Workaround: Upgrade the server to .NetFramework 1.1.

Issue: Java Explorer does not recognize, if the project directory was changed in SilkPerformer GUI. If Java Explorer is opened with an invalid project directory setting, an exception occurs. (12070, 13006)
Workaround: None.

Issue: If JRE 1.5 Plugin for Internet Explorer is used, a java.security.AccessControlException may occur. E.g. the ProductManager sample reports an ´Exception in thread "Thread-5" java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThread)
Reason: Security permissions have changed between JRE 1.4 and JRE 1.5. (17539)
Workaround: Add the following grants to the .java.policy file:

        grant { 

          permission java.lang.RuntimePermission "modifyThread"; 
          }; 
        grant { 
          permission java.lang.RuntimePermission "modifyThreadGroup"; 
          }; 

Note: The .java.policy file ususally can be found under: C:\Documents and Settings\<username>\.java.policy

Web Support:

Issue: Hooking of Firefox is not possible, if Firefox is open before recording. (25843)
Workaround: Close all firefox browsers before starting recording.

Issue: Recording form submissions of HTML forms with multiple identical named form fields, which’s values are changed, may result in a script, which sends a slightly different form (than sent at recording) at replay. (8744, 9947)
Workaround: Manual scripting may be necessary.

Issue: If STRING_COMPLETE is specified as 3rd parameter of the WebFormExpand function, the form is appended to the provided string (the string parameter is not cleared anymore). (12508)
Workaround: Provide an empty string as out-parameter to the WebFormExpand function.

Issue: When using Internet Explorer with the Recorder, a Security Alert Dialog may be shown for every embedded object (image) on the Web site. This can be very annoying when the Web site contains a lot of embedded objects.
Workaround: Open the "Internet Options" in the Control Panel or from the "Tools / Internet Options" menu in Internet Explorer. In the "Advanced" tab uncheck the option "Warn about invalid site certificates", and click OK.

Issue: In very rare cases, the browser may not load frame documents that are in the browser's cache during the recording. In this case, the recorder records one page-level API call for each frame, instead of one page-level API call for the complete frameset. (6422)
Workaround: Clear the browsers document cache and repeat the recording session.

Issue: Netscape 6.2 cannot be recorded, if QuickLaunch is enabled.
Workaround: Deactivate QuickLaunch (Edit -> Preferences -> Advanced) or manually exit Netscape 6.2 before recording.

Issue: Certain non-default Internet Explorer configuration options can result in the Recorder not being able to record Internet Explorer traffic. Because these options can only be changed by editing registry values, such problems occur only very rarely. (9779)
Workaround: Re-configure the two Internet Explorer registry settings listed below. Both registry entries must have the value "yes." Otherwise separate iexplore.exe processes won't be created when starting Internet Explorer, and Internet Explorer will be hosted by the explorer.exe process:
1) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
Explorer\BrowseNewProcess\BrowseNewProcess
2) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Explorer\BrowseNewProcess\BrowseNewProcess

Database Support:

Issue: If the last SQL statement in the dclsql section of the script is not followed by a blank or line break, then an error occurs during replay showing a misleading error message. (11881, 8224, 8555)
Workaround: Add a blank or line break behind the last SQL statement in the dclsql section of the script at the end of the script.

Issue: The Recorder generates a non-compilable script, if an SQL statement has been recorded that contains the character sequence /* not using it as open comment notation. In this case, the BDL compiler nevertheless interprets this as the beginning of a comment and misses the closing of the comment which leads to a compile error. (10726)
Workaround:
1. Remove the SQL comment or add an escape i.e /\**
2. Record the script again, but with unchecked option to generate SQL comments (Profile Settings / Record / Script / Protocols / SQL comment). This does not generate the SQL statement comments.
3. Check if the character sequence /*can be removed from the SQL statement without changing the semantic of the statement.

Issue: When recording an OCI 8 application that writes LOB data into the database, the Recorder generates files into the project directory that store these data in order to have these data available during replay. These files are named like the following name pattern: LOB_xxxxxxxx.dat. When recording a COM/ADO application that passes binary content (byte arrays) to an interface method, SilkPerformer is recording the new methods ComSetBinaryFromFile/AdoParamSetBinaryFromFile. The binary content will be stored in a file in the project directory that has the following name pattern: BINARY_xxxxxxxx.dat. But the files will not be available during replay on a remote agent and therefore cause a replay error unless the files will be added to the Data Files section of the project. (11860, 13408)
Workaround: Manually add the generated .dat files to the Data Files section of the project in order to run the script on remote agents.

Issue: For some cases, the ODBC Recorder generates a wrong parameter for the type of placeholder in the OdbcBind function if the prepared statement is a stored procedure. As a result, the TrueLog Explorer may show the corresponding data in the IN or OUT data table even if it is not an IN or OUT parameter. (12445)
Workaround: Check the type of the placeholder depending on the type of direction of the parameter of the stored procedure.

Issue: An Access violation error in the client application may occur during recording the function SQLPutData of an ODBC client application if the profile setting “Record / Results / Hook logging / Function parameters” is turned ON. The setting is turned OFF by default. The access violation is caused by a bug in logging the second function parameter of SQLPutData and does not take effect if the previous setting is turned OFF. (12444)
Workaround: Turn OFF the setting “Record / Results / Hook logging / Function parameters” in case your ODBC application to be recorded gets an Access violation during recording the function SQLPutData.

Issue: The TrueLog Explorer may show the OUT data columns of an OdbcFetch call whose result set was generated from an OdbcProcedureColumns call in a different order for the Record and the Replay TrueLog if the define calls were not made in ascending order of the position indices. In this case, the Replay TrueLog will show the OUT data columns in ascending order whereas the Record TrueLog will show the OUT data columns in the order as the corresponding define calls have been made. As a result of this, the TrueLog Explorer will most probably show a difference in the OUT data also if there may not be a real difference in the fetched data. (12446)
Workaround: Manually check for possible differences in the OUT data table in the above described situation.

Issue: If an SQL statement contains a comment in notation starting with “--" then the OCI replay engine generates an error showing a misleading error message. This is caused because the Recorder removes line breaks from the SQL statement string if the profile setting “Record / Script / Protocols / Trim SQL” is turned ON. (10790, 14985)
Workaround: Either find the end of the comment text and insert a line break there in the statement string of the dclsql section of the script or turn OFF the above described profile setting and record the application again.

ADO/COM Support:

Issue: If the recorded client application is using the IEnumVARIANT and the default Recordset interface methods to navigate through ADO recordsets - the ADO recorder will script an AdoFetch method and afterwards the IEnumVARIANT calls. Those calls will fail as AdoFetch is fetching all the recordsets first and the IEnumVARIANT method would operate on a non valid row in the recordset as AdoFetch will move the rowset cursor to EOF. (12465)
Workaround: Either comment the AdoFetch or the calls on the IEnumVARIANT.

Issue: If your client application is accessing the individual Field interfaces of a recordset and is freeing the interface for the Fields collection before freeing the individual Field interfaces, it might happen that the call to query for the Fields interface won't be scripted. (12472)
Workaround: Add a ComGetInterface(hRecordsetItf, "get:Fields", hFieldsItf, "Fields") prior to the functions that access the individual Field interfaces.

Streaming Support:

Issue: If the bandwidth of the server is restricted and the Media Streaming client has a higher bandwidth, then the Media Streaming engine (and also the perfrun.exe) hangs. (8298)
Workaround: None.

Issue: Real streaming does not work with RealPlayer 10.x. (17080)
Workaround: Use a previous version of RealPlayer.

GUI-Level Testing Support:

Issue: When too many terminal sessions run, or memory is too low, the agent computer gets very slow. (27876)
Workaround: Add more memory and/or run less parallel sessions.

Issue: Connection try times out when invalid login credentials are provided, without returning an error message providing directions. (29154)
Workaround: None. Valid login credentials must be provided.

Workbench:

Issue: Script modifications made with the Parameter Wizard or the SilkPerformer Unicode Text/HEX Editor cannot be undone using the Workbench Editor's Undo functionality. (15782, 15875)
Workaround: None.

Issue: After importing a project it may happen that baseline results are not recognized in the "Workflow - Calculate the Virtual Users" dialog, even if baseline results have been generated and accepted before importing the project. (14787)
Workaround: Re-compiling all scripts will resolve the issue. The "Workflow - Calculate the Virtual Users" dialog will then recognize the existing baseline results.

Issue: When mailing a project from SilkPerformer ("File / Email Project") with Lotus Notes, the "To" (recipient) field may be empty even if you supplied a valid e-mail address in the Email Project dialog. (5358)
Workaround: Either insert the e-mail address manually into the "To" field, or use another e-mail client. You can set your default e-mail client in the Internet Explorer options (Tools / Internet Options / Programs).

Issue: The Email Project functionality may not work due to configuration problems. (6490)
Situation 1:
There is no MAPI configured on the Windows system (no mapi32.dll is available in directory C:\WINNT\system32\). When clicking on the OK button of the EMail Project dialog the error message "Cannot open your email client, because MAPI32.dll couldn't be loaded. ..." occurs.
Situation 2:
Netscape Messenger is registered as mail program in the Internet Options dialog of the Internet Explorer, but Netscape Messenger is not configured correctly and is not your default mail client. When clicking on the OK button of the EMail Project dialog the error message "Your email address has not been specified. ..." occurs.
Workaround:
Situation 1:
Execute the fixmapi.exe application in the WINNT\system32 directory and try again. Then the Email Project functionality should work.
Situation 2:
Select the email client that you want to use for sending e-mails as defined in the Programs tab of the Internet Options dialog of the Internet Explorer. The Email Project functionality should then work.

Issue: When creating a new project, the settings of the default profile will be set depending on the selected Application type for the project. These settings are different for some Application types. But when creating a new profile for projects of such Application types, the settings will be initialized with the system default settings and not with the Application type specific settings as done for the first default profile. Also when clicking the Default button in the Profile Settings dialog, the settings will be reset to the system default settings and not to the Application type specific default settings. (8122)
Workaround: Use the Copy Profile command instead of the New Profile command to create new profiles as copies from the default profile. Keep in mind that clicking the Default button in the Profile Settings dialog resets the settings to the system default settings and not to the Application type specific default settings.

Issue: When you start an automated load test using the command line interface and open a menu from the menu bar while the simulation is running, then SilkPerformer will crash at the end of the simulation unless you do close the menu before the simulation is finished. (2782)
Workaround: Do not open any menu from the menu bar, or if you do ensure you close it again before your load test is finished.

Issue: An array of string parameter cannot be passed to a native function of aruntime extension dll.
Workaround: Convert the BDL string array to a simple string variable and pass it to the native function as a character pointer.

Issue: The System Configuration Manager is not able to correctly display the amount of memory of a machine with more than 4 GB RAM. (16882)
Workaround: None.

Monitoring:

Issue: Monitoring of perfmon counters does not work on Windows Vista. (34587)
Workaround: To monitor Vista's perfmon counters, the remote registry service must be running. On Vista this must be done manually (via Service Control Manager).

Issue: If you collect data in a smaller PDCE interval (BDL functions: PdceClientInterval, PdceClientRegister) than 1000 milliseconds, your result measures may have incorrect values.
Workaround: Do not specify interval values smaller than 1000 milliseconds.

Issue: If WebSphere 3.5 Application Servers are restarted while they are being monitored, the Performance Explorer will not be able collect further performance data.
Workaround: Change the collection interval. For example, change the collection interval from 10 seconds to 11 seconds. If WebSphere performance data is written to tsd files, save and close the Monitor Report. Change the tsd write interval, for example, from 10 to 11 seconds and have performance data again written into tsd files. The easiest way to continue monitoring WebSphere once it has been restarted is to save the current workspace and restart Performance Explorer.

Recorder:

Issue: The Recorder is not able to record any traffic, though it may have previously worked.
Under certain circumstances the file PerfShk76.dll.install still exists in the directory \WINNT\System32, even though it should have been deleted. This file is temporarily copied into the directory and should be removed when you close the Recorder.
Workaround: Manually delete the file PerfShk76.dll.install from the directory \WINNT\System32. You may have to reboot the computer in order for this to take effect.

Licensing:

Issue: If you are running different versions of SilkPerformer on the same machine, they must use the same SilkMeter License Server.
Workaround: None. As designed.

Setup:

Issue: Remote agent setup does not work on Windows Vista. (34015)
Workaround: None.

Issue: SilkPerformer Remote Setup will not work on a computer on which SilkPerformer is installed on a mapped drive. Since Remote Setup cannot detect the mapped drive, the checks for installed products will fail and a new SilkPerformer Installation will begin because an update was not allowed.
Workaround: None.

Issue: If the default project directory is changed, some SilkEssentials may not work due to broken links. (12955)
Workaround: Use the default project directory.

Issue: At the beginning of the Setup following error might occur: "Error -1607: Unable to install InstallShield Scripting Runtime".
Workaround: For more information please refer to
http://support.installshield.com/kb/view.asp?articleid=q107070
or
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b324906

SilkCentral Test Manager Integration:

Issue: Upload Project or Results to TM with insufficient permissions results in a "server returned 500" error. (22072)
Workaround: None.

Issue: If the IE option "Advanced Internet Options / Do not save encrypted pages to disk" is checked and you are using a secure connection (HTTPS), it is not possible to open the command file, downloaded through the links to "Open Project" and "Analyze Results". (21240)
Workaround: Uncheck this IE option.

Issue: If a project is opened via the "Open Project from TM" feature, the workload configured in TM is not taken over by the SilkPerformer workbench. Instead the default workload configured in the actual SilkPerformer project is taken. (21329)
Workaround: Use "Import Project" or "Run Attended" if you attend to execute the project.

Issue: Uploading a project to a wrong URL does not report an error. This occurs if e.g.: http://localhost:19120/upload is specified as upload URL instead of http://localhost:19120/project_upload
Workaround: Specify the correct upload URL.

Issue: If a SilkPerformer project is opened from SilkCentral TestManager the wrong workload may be active.
Workaround: Activate the correct workload via the SilkPerformer Workbench.

SilkPerformer Source Code Control Integration:

Issue: When adding a project (or single project files) to source control using StarTeam as source code control provider an informational message box may appear stating: "A server entry in your starteam-servers.xml file named <specified starteam host> does not exist.". The following sequence of upcoming message boxes and dialogs may be confusing.
Workaround: If the mentioned informational message box appears:

• Select "Yes" on the next message box prompting whether to select a different existing server, project, or view.
• Log on to the server you've specified to act as your StarTeam host on the following "Open Existing StarTeam Project" dialog.
• In the "Project" list, select the StarTeam project you've specified to put your files into.
• Click "OK" to close the dialog.

Issue: The option "Apply to all items" does not work if multiple files are involved in a Source Code operation. The user will be prompted for each of the files. (23118)
Workaround: None.

Issue: When SilkPerformer projects and/or files are linked to a defined SCC directory, and the directory is changed via the SCC client, SilkPerformer does not reconnect to the new directory.
Workaround: Remove the existing source control linkage and add the affected projects/files to the new directory.
Note: It is generally not recommended to use SCC client functionality for maintaining linked SilkPerformer projects.

Issue: MS VSS 8.0 introduced a security setting that, when activated, requests the user to enter their username and password each time they check in or check out a file from VSS. This request also appears in SilkPerformer when performing file operations with VSS.
Workaround: To disable MS VSS manual login:
1. Open SourceSafe Administrator.
2. Open the database where your SilkPerformer projects are saved.
3. Select the Options command from the Tools menu (Tools/Options).
4. Select the General tab.
5. Check the Use network name for automatic user login checkbox.

Note: This procedure only works if the username in VSS is identical to the network username.

Issue: Checking out a file followed by a immediate check in may cause an error caused by the Source Control provider that says that the file is currently not checked out. Despite the error message and the remaining "Checked-out" Source Control state of the file, the operation succeeded and the file was checked in. It will not be possible to check out this file again since Workbench assumes the file already to be checked out.
Workaround: Select the "Synchronize" command from menu "File / Source Control" after waiting for about 60 seconds. This will update the Source Control state of all the files of your project.