NOTICE: Our Community is moving. Get more information. Updated information on a New Login Process
To resolve the issue, delete any .jou and .o files in your working directory which are related to your testscript.
For example, if your testscript is named foo.t, then the default name for the results file would be foo.res. Check to see if you have a foo.jou or a compilation file (foo.to or foo.ino); if so, delete these.
If there is a file called foo.jou in the same directory as the testscript you are trying to run, SilkTest will be unable to open the results file and SilkTest will refuse to execute the testscript. The .jou file is a temporary journaling file. If SilkTest unexpectedly terminates without being able to clean up files open at the time, then the .jou can be left around.
Also check for testscript compilation (.to or .ino) files. If a compilation file for some reason gets into an invalid state, this can also prevent SilkTest from writing a new .to of the same name and the execution will again be blocked.