Running a Try-Script starts a loadtest instead.

Running a Try-Script starts a loadtest instead.

This was a known issue and can occur when you have a workload named ORIGINAL. Silk Performer uses this name internally for Try-Script tests and having a workload with this name will cause a load test to execute instead when a Try-Script is chosen. As a workaround simply rename your workload to something else. This issue was fixed in SilkPerformer 7.0.

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.