"OraForms: 21 - Communication Error., class java.io.EOFException java.io.EOFException java.io.DataInputStream.readUnsignedByte" is one error reported when the server does not accept SilkPerfomer's default response to a GET message sent by an Oracle Forms server. Oracle Forms Servers can spontaneously initiate GET messages to the client, for example, if the server's cache was emptied and it needed to request the value of button XYZ again the server would send a GET message. When a GET message is encountered during record SilkPerformer scripts the necessary functions to send the correct response to the GET message. However, if the GET message was not encountered during record, SilkPerformer can only provide a default response, such as null for strings and 0 for numeric values etc. This may not be accepted by the server and the "OraForms: 21 - Communication Error., class java.io.EOFException java.io.EOFException java.io.DataInputStream.readUnsignedByte" error is reported. To resolve this error you must manually script the OraFormsSet* and an OraFormsOnMessageGet functions preparing the appropriate response for the server’s GET message. To manually script these functions, analysis of the in-data and out-data tabs in TrueLog Explorer which logs the underlying Oracle Forms communications between server and client is required. This communication is only logged if you have set SilkPerformer’s logging level to debug. If the logging level was not set to debug change the setting and perform a fresh record / replay. To set SilkPerformer logging to debug level go to: SETTINGS | ACTIVE PROFILE | ORACLE FORMS | LOGGING tab | Select "Debug" from the Log level drop list. Once you have completed this review the replay TrueLog, specifically TrueLog Explorer's in-data tab for GET messages sent by the server. These look like: If you find these messages in the in-data tab you then need to inspect the script for an OraFormsOnMessageGet function that references the control. This should be scripted prior to the API on which the GET message was received. If you find an OraFormsOnMessageGet that references the control it could be that you need to move the function to another location in the script. If you do not find an OraFormsOnMessageGet function that references the control you will need to manually script the function prior to the API on which the GET message is received. To determine the appropriate response open the record TrueLog (record.xlg) and again search TrueLog Explorer"s in-data tab for the GET message sent by the server. The response to this GET message will appear in a subsequent communication from the client terminated by a Terminal 3 message so you need to search TrueLog Explorer's out-data tab. The response for the above GET message from the server looks like: From this we can script the necessary OraFormsSet* and an OraFormsOnMessageGet functions preparing the appropriate response. The important parts of the client communication are: TYPE: PROP_TYPE_STRING Name: COMBOBOX_USERITEM/338 Value: This tells us that we need to prepare a string response using OraFormsSetString with property name COMBOBOX_USERITEM and the value is an empty string. The functions that need to be inserted prior to the API where the GET message is received are: OraFormsSetString("COMBOBOX_USERITEM", "", ORA_SET_TYPE_MESSAGEGET); OraFormsOnMessageGet("317");
↧
Wiki Page: "OraForms: 21 - Communication Error., class java.io.EOFException java.io.EOFExceptionjava.io.DataInputStream.readUnsignedByte..." error reported on replay of script
↧
Wiki Page: "PDCE: 905 - JMX deployment failed., Monitor will be restarted."
BMC TMART now ships with a JMX monitoring essential which can be used to monitor the system health of execution servers. However if using JDK 1.6 on the execution server the deployment of the monitor may fail. To resolve this issue there are two methods: Revert to JDK 1.5 Uninstall JDK 1.6 Install JDK 1.5 Re-install the execution server to pick up the new settings. Modify XML files The second method involves modifying two configuration files on the execution server as follows: Locate C:\Program Files\BMC Software\BMC TM ART Central 3.6\bin\Core\perfJvm.xml At line 3 change: JVMCONFIGFILE version="%SUN_JVM_VERSION_15%" javahome="%SUN_JVM_HOMEPATH_15%" to: JVMCONFIGFILE version="1.6.0_12" javahome="C:\Program" Files\Java\jre6 Locate C:\Program Files\BMC Software\BMC TM ART Central 3.6\bin\Core\Working\Include\jmx-config\jmx-config.xml copy lines 36-38 1.6.0_12 SUN C:\Program Files\Java\jre6 over lines 6-8, so 1.5 and 1.6 point to the same path. Then restart the Execution Server service and the System Health essential should now work.
↧
↧
Wiki Page: "Page Cannot be Displayed" when recording a HTTPs site with Silk Performer after applying Windows update
Windows update KB2661254 blocks the use the use of RSA certificates that have keys that are less than 1024 bits long. During recording of secure traffic the recorder presents its own certificate rather than than the actual server certificate of the application you are recording to the browser (note it is not possible to forward the server certificate). This recorder certificate contains an RSA key that is 512bits in length, therefore with Windows update KB2661254 applied, Internet Explorer blocks the connection. The recorder certificate have been updated increasing the encryption key length with hotfix SP90_HF9_CERTS. Please upgrade to the latest version of SilkPerformer to resolve this issue.
↧
Wiki Page: "REQUEST: AMF3: Java based XML generation failed, using fallback, reason: java.lang.NullPointerException" gets scripted even with all jars present.
This exception will be reported and content not transformed to XML when Silk Performer is unable to transform some AMF3 traffic where short names setting is enabled on the Flex server. Short names allows the server to use an alias instead of the full class name and Silk Performer expects the full class name to identify the name and location of the class within the jar files specified for transformation. The correct class may exist within the jars but Silk Performer cannot map to the class from the alias. It is possible to diagnose this issue in two ways: In the Silk Performer script the alias is displayed in the comment beside the untransformed data: In the record log the full stack trace is displayed and this highlights both the full name of the class Silk Performer is expecting and again references the alias in the raw data: SP811_Hotfix08_AMF3ClassAliases.zip enables Silk Performer to map additional aliases to the full class name.
↧
Wiki Page: "RESERR: 94 - random file > too large to open (maximum length = 65279)" error when reading csv file
Reading of a CSV file is done using an 'Integer' variable to receive the file handle used to access the file. Therefore, the length of CSV file which can be read is limited by the maximum length of the 'Integer' variable type (65279). If you are reading from a CSV file which has more rows than the variable maximum length, you will get an error such as the following: "RESERR: 94 - random file too large to open (maximum length = 65279)" The limitation (65279) with the ‘Integer’ number type in general is discussed in the following Wiki article: http://en.wikipedia.org/wiki/Integer_(computer_science) To workaround this limitation will require some custom logic such as use of a second file or handle.
↧
↧
Wiki Page: "SYSTEM: 2 - The system cannot find the file specified" when testing after application of Hotfix 07 for Silk Performer 2011
This error is reported when the ‘Encryption (SSL)’ option in agent communication is enabled as shown below. You can access this dialog under TOOLS | SYSTEM CONFIGURATION MANAGER, and connect to the agent machine showing the issue. To work around the issue you can connect to the agent via unsecured unsecure connection by unchecking the ‘Encryption (SSL)’, and the agents can then be used as expected. This is Known Issue which will be addressed in a future release.
↧
Wiki Page: "TChart control is not properly installed" when launching Silk Performer.
This issue has been known to occur when installing and accessing Silk Performer on a remote machine through an RDP session. RDP connection settings can affect the operation of certain Silk Performer components when enabled. Under Local Resources in the RDP options tab, if printers are enabled this triggers the installation of a virtual printer driver (this process happens in the background) which gets installed on the remote machine and this installation can lock access to specific parts of the registry required by Silk Performer. To resolve this error click on START | RUN | mstsc [enter]. Click on options and go to the local resources tab and disable printers. At this stage try connecting and starting Silk Performer. If you have installed Silk Performer over RDP with printer's enabled then you may need to uninstall/reinstall with the printers options disabled to fully resolve the issue.
↧
Wiki Page: "TChart control missing" when launching Silk Performer.
This issue usually arises due to the incorrect installation of Silk Performer. Unable to register teechart.ocx. This problem is due to the virtual printer driver of windows terminal services which misses a function to export. To resolve this, when connecting via remote desktop connection make sure to uncheck "printers". You can then navigate to (via commandline) "C:\Program Files\silk\Shared Files". Type "Regsvr32 -i teechart.ocx" The above should resolve the issue.
↧
Wiki Page: "Warning: hooking not properly configured. PerfHK_Name environment variable not available: PerfHk_Name81"
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 Workbench · Go to the environment variables dialog e.g.: START | SETTINGS | CONTROL PANEL | SYSTEM | ADVANCED | ENVIRONMENT VARIABLES · Ensure you have a SYSTEM variable called "PERFHK_NAME81" with the value being PerfHk.dll located in the SilkPerformer root folder e.g.: " C:\Program Files\Silk\SilkPerformer 2010\PerfHk.dll" Depending on the type of Operating System you are running the path could be C:\Program Files\Silk... · If this variable is missing add it with the value described · Exit the environment variables dialog
↧
↧
Wiki Page: "WebRemedyBackChannelUrl(WebEngine: 12 - The parameter provided is invalid., Please select the correct Remedy Application Type for script recording)" when testing Remedy 7.6.04 SP1
Silk Performer 2011 needs a new SilkEssential for testing this exact version of Remedy. Attached below is a Silk Performer project template for Remedy 7.6.04 SP1. To use this you should unzip and copy the attached file, "Remedy7.6.04 SP1.sep" to the Silk Performer 'Essentials' folder (default location, "C:\Program Files\Silk\SilkPerformer 2011\Essentials") and restart the workbench. You should then create a new project, select the new Remedy application type, "Remedy 7.6.04 SP1" and record a new script. Remedy7.6.04 SP1.zip
↧
Wiki Page: .Net Explorer 15 crashes while navigating certain classes.
Silk Performers .Net Explorer might crash whilst the user is navigating loaded classes which include a circular dependency in it's hierarchy. The problem has been fixed with Silk Performer 15.0 Hotfix3 and also natively in Silk Performer 16.0.
↧
Wiki Page: "XML: 19 - Parser Error!, Unexpected character in query string".
XmlSelectSingleNode(XML: 19-Parser Error!,Unexpected character in query string./SOAP-ENV:Envelope[1]/SOAP-ENV:Body[1]/ns:insertPlaceResponse[1]/- # The above error message will occur if you have executed a BDF script which was generated from exporting a .NET Explorer Project into Silk Performer. The actual root cause of the error is due to xml comments being incorrectly exported by the .Net Explorer as part of the actual XML string (e.g. the string "#comment" should not be generated when exporting the script to SilkPerformer). It is also worth noting that this error will only occur if previous to exporting the project from the .NET Explorer you have captured or verified an XML Comment string. The issue was fixed in Silk Performer 6.0. It's possible to work around the issue by manually removing any #comment entries from your BDF script file... for example, the following recorded line: mGetAddressResponse := XmlSelectSingleNode(hDoc, "/SOAP-ENV:Envelope[1]/SOAP-ENV:Body[1]/ns:getAddressResponse[1]/#comment[1]"); Should be modified to look like the following: mGetAddressResponse := XmlSelectSingleNode(hDoc, "/SOAP-ENV:Envelope[1]/SOAP-ENV:Body[1]/ns:getAddressResponse[1]/");
↧
Wiki Page: .NET Explorer Enhancements in SilkPerformer 7
TrueLog for Web Services .NET Explorer now generates TrueLogs that include HTTP traffic for all tested Web Service methods. TrueLogs include nodes for all Web Service calls containing request and response HTTP header and body information. Testing COM Components .NET Explorer now enables the testing of COM components by loading COM type information (library type or COM server library type) and generating runtime-callable wrappers that can be accessed just like standard .NET classes. Verifications on Variables .NET Explorer now allows you to execute verifications against variables. CSV Support for Multi-Column Parameters .NET Explorer introduces an enhanced data parameterization wizard (similar to SilkPerformer"s Parameter Wizard) that allows you to easily assign rows of data from CSV formatted files to multiple user-input data fields (e.g., login and password data). Negative Testing .NET Explorer now allows you to add methods that throw exceptions in your test cases. Exceptions thrown during replay can be treated as either errors or successes. For full details of .NET Explorer please see the User Guide that ships with SilkPerformer 7.0 START | PROGRAMS | SILKPERFORMER 7.X | DOCUMENTS | .NET TESTING - .NET EXPLORER USER GUIDE Please note : End of Support for COM and COM+ was announced in Silk Performer 2011.
↧
↧
Wiki Page: .Net Explorer verification fails with the error "RETURN(fFloat) value is not fFloat"
One possible reason for this is that you have entered a number with seven decimal places or more into the Input Value field. .Net Explorer will round this value to six decimal places for the input value display however the verification wizard does not round the value to six decimal places, instead it keeps the original value. For example, if you enter 1.23456789 as your input value, .Net Explorer will round this up to 1.2345678. Then in the verification wizard, if you enter 1.2345678 the verification will fail because the value is really 1.23456789. This will result in an error: Message(): { Method : echoFloat Test Case : TestCase Test Case Iteration : 1 Time : 02/02/2005 10:56:11 Severity : Error Message : RETURN(1.234568) value is not 1.234568 } This issue has been fixed in SilkPerformer 7.0
↧
Wiki Page: “Cannot find MSXML4 Parser - please install at least version 4” when attempting to reference xml functions.
This is a known issue with SilkPerformer 2010 R2 where the msxml*.dlls are not installed to the System32 or SysWOW64 folder. To resolve this issue please copy both the msxml4.dll and the msxml4r.dll from \Program Files\Silk\SilkPerformer 2010 R2\RSFiles to the following folder: For 32 bit machines……..\WINDOWS\system32 For 64 bit machines……..\Windows\SysWOW64
↧
Wiki Page: 'Show TrueLog' option is disabled within the 'Analyze Errors' section of Silk Performance Explorer.
'Show TrueLog' option is disabled within the 'Analyze Errors' section of Silk Performance Explorer. If the' Show TrueLog' option has been disabled (greyed out), it indicates that the TrueLog / TrueLog on Error file option was not enabled during test execution, meaning no TrueLog files were generated. To address this issue, the test will need to be re-run with one of the TrueLog options enabled (preferably TrueLog on Error)
↧
Forum Post: RE: SilkPerfomer 17.0 TrueLog file problem
Is this fixed in SilkPerformer v. 17.5?
↧
↧
Forum Post: RE: SilkPerfomer 17.0 TrueLog file problem
hi steven, that is scheduled for 18.0. the mix up in the truelog only occurs when "100 continue" is used in the protocol, which is really rare. cheers, udo
↧
Wiki Page: Can I set up silkperformer to run a script at intervals of 5 minutes 24x7x365 ?
The Workload Configuration dialog does not provide the flexibility required to schedule tests at specified intervals. However there are several workarounds you could implement: Windows 2000 Use the Program Scheduler START | PROGRAMS | ACCESSORIES | SYSTEM TOOLS | SCHEDULED TASKS Use the scheduler to execute a batch file that will run the SilkPerformer test. Please refer to How do I run a SilkPerformer loadtest from the command line or from a batch file? Windows NT Use the AT command line function to schedule the batch file to run. For more details on this go to the Command prompt and type AT ? Segue Solution Using SilkCentral Performance Manager you will be able to schedule tests to run at specified intervals. For more information on this consult your sales representative.
↧
Wiki Page: Can I simulate users doing file operations including creating, moving, opening, closing, reading from and writing to files?
You can simulate this using SilkPerformer"s fOpen, fWrite, fClose functions. It is also possible to use dll integration to make use of the How do I integrate third party dlls into my SilkPerformer script? Do you have any examples of integration of potentially useful functions from the Win32 API? as well as other API"s. It should be noted though that all simulated users will be using the same Windows login credentials.
↧