PerfomanceTest Error - Could not open PerformanceTest preferences file

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • hippman
    Junior Member
    • Mar 2017
    • 4

    #1

    PerfomanceTest Error - Could not open PerformanceTest preferences file

    I have automated version 8 to run and output the results to a CSV file.

    With v9 there is an error message when using the /ac commandline option.

    PerformanceTest64.exe /ac C:\folder\results.csv

    Anyone else come across this?

    ---------------------------
    PerfomanceTest Error
    ---------------------------
    Could not open PerformanceTest preferences file

    ---------------------------
    OK
    ---------------------------

  • hippman
    Junior Member
    • Mar 2017
    • 4

    #2
    Here are the steps to reproduce the issue.

    Install PerformanceTest9

    Use "Install to USB" feature then move to another machine for testing

    Run the command "PerformanceTest64.exe /ac C:\folder\results.csv"

    Comment

    • David (PassMark)
      Administrator
      • Jan 2003
      • 11092

      #3
      The install to USB function was designed to install the software to a portable USB drive (not a hard drive).

      Does it work if you install it to a USB drive?

      Comment

      • hippman
        Junior Member
        • Mar 2017
        • 4

        #4
        Hi David,

        Yes this problem is reproducible on a USB key as well.

        I even tested this via the command line with Performance Test installed locally and it fails as well.

        I suspect this is actually an issue with running Performance Test with the command line "/ac" switch and should be reproducible.

        Comment

        • Richard (PassMark)
          Administrator
          • May 2010
          • 967

          #5
          The bug prompting the error "Could not open PerformanceTest preferences file" (triggered when no initialization file is specified) has been fixed as of PerformanceTest V9 Build 1009. Can you try again with the current release and let us know if this solves your issue?

          Comment

          • hippman
            Junior Member
            • Mar 2017
            • 4

            #6
            Thanks Richard! I just installed build 1010 and that resolved the issue!

            Comment

            Working...