Forum Discussion

nounge's avatar
nounge
Occasional Contributor
9 years ago

TestComplete12: Excel sheet not found error when executing as batch

On TestComplete 9, I was using the Windows Task Scheduler to run a suite of (scripted) tests by command line execution every day. I also use Excel to parameterize input for the tests. This had been w...
  • tristaanogre's avatar
    tristaanogre
    9 years ago

    I'm still thinking it's a permissions thing in some way...  Running it at the "Run" prompt in windows is running it using your user account.  Running it as a task in task scheduler or as a batch, potentially, may be using a different user account or privilege level or, if it's running as you, it MIGHT not be running with the most elevated privileges you have (admin).

     

    Try in your task setting the security options to have it run as an administrator. I know it seems strange, but give it a shot and see if that works.

nounge's avatar
nounge
Occasional Contributor

I understand that you would believe the paths to be the issue due to the error message. I considered it as well. However, the paths are not declared relatively in the command. This is verified by the fact that the command works perfectly through a normal Command Prompt.

 

I am not using the Start in option. For the sake of simplifying the solution, we can neglect Task Scheduler. The command does not work when inserted into a batch call.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
9 years ago

Hrm... what about permissions elevation? Is it possible that when running as a batch/task that the persmissions aren't sufficient to get to the Excel sheet?

Could you post the code that is accessing your excel sheet or a screenshot showing the configuration if you have it in a Project variable or Keyword Test Variable?

  • nounge's avatar
    nounge
    Occasional Contributor
    9 years ago

    I don't believe it to be a permissions issue: TestComplete 9 was able to access it this way. I will take a closer look at this, but I don't believe it is the cause.

     

    Attaching the code for the GetParameters function

    • nounge's avatar
      nounge
      Occasional Contributor
      9 years ago

      FYI: code is VBScript

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        9 years ago

        OK... the code looks fine at first blush.

        Two pieces of information that will be helpful:

        1) The exact line of code generating the error

        2) The exact text of the error message

         

        I'm GUESSING it's on 

        Set oWorkbook = oExcel.Workbooks.Open(...)

        But your OP mentions Sheet not found, not file not found... which seems to point to the next line

        Set oWorksheet = oWorkbook.Worksheets.item("Data")

        Can you confirm what's happening?