Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What are the known issues in SilkPerformer 2006?Pt2

What are the known issues in SilkPerformer 2006?Pt2

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.

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: 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 Silk Performer .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 Silk Performer .NET Add-In Wizards do not work properly anymore.
Workaround: Re-install the Silk Performer .NET AddOn.

Issue: When creating an Individual String random variable with Silk Performer's Visual Studio .NET Add-In in a VB.NET Project, the generated RndInd declaration is not compliable 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 Silk Performer. 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 Silk Performer installation CD (%CD root%\\redist\dotnetruntime\) or at Microsoft MSDN (http://msdn.microsoft.com/netframework/).

Issue: If Silk Performer .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-compliable .NET code as a variable of the private class will be scripted instead of the public class/interface. (12449)
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 Silk Performer'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 "Silk Performer.SPSoapHttpClientProtocol" to route it over Silk Performer'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
Workaround: Export the project as Silk Performer .NET Project.

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


Java Support:

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: Weblogic 8 Client stub classes may not work with the custom classloader. The custom classloader is used, if java archives are added to the normal project classpath. Java Explorer will report unexpected ClassNotFoundExceptions. (12608)
Workaround: Add the problematic client stubs to application server classpath, so the system classloader is used.

Issue: Java Explorer does not recognize, if the project directory was changed in Silk Performer 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 4Exception 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\\.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\
2) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:39
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.