Forum Discussion

andrewa's avatar
andrewa
Contributor
8 years ago

"OleObject" does not exist, TestComplete 12.2

So we recently moved from TestComplete version 9 to 12.2. We have a number of tests that read and write data from Excel spreadsheets. I started to have problems with the JScript we use to access the ...
  • tristaanogre's avatar
    tristaanogre
    8 years ago

    Not sure... the variable assignment is assigning to a property, not necessarily calling a method that returns.  So... it could be that you do need some sort of delay.

     

    What I would do is add

     

    Sys.WaitProcess('Excel', 10000)

    I did a quick smoke test of this and, yes, there IS a bit of a delay before the application is running.  Give this a try and see if this helps.

andrewa's avatar
andrewa
Contributor

Looks like it's the 32-bit version. Microsoft Excel 2016 MSO (16.0.4456.1003).

 

It all seems so odd to me. Would JScript proceed if the app hadn't loaded into memory yet?

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago

Not sure... the variable assignment is assigning to a property, not necessarily calling a method that returns.  So... it could be that you do need some sort of delay.

 

What I would do is add

 

Sys.WaitProcess('Excel', 10000)

I did a quick smoke test of this and, yes, there IS a bit of a delay before the application is running.  Give this a try and see if this helps.

  • andrewa's avatar
    andrewa
    Contributor
    8 years ago

    That piece of code seemed to clear up most of the errors I had when trying to open up an Excel file.  The intermittent OleObject errors have come back. I'm guessing something with how my machine is configured might be causing this issue.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    Again, it might be that the Excel.Application is still open... 

     

    Try, before your variable assignment, the following

     

    if (Sys.WaitProcess('Excel', 10000).Exists) {
    Sys.Process('Excel').Terminate();
}

     That's just a guess.. but see if that helps.

  • Jeevan's avatar
    Jeevan
    New Contributor
    8 years ago

    Recently faced the Sys.OleObject("Excel.Application") issue, the call is randomly returning object contains nothing and test fails. Below approach is a workaround.

     

    if(Sys.WaitProcess("Excel", 10000).Exists){
      Sys.Process("Excel").Window("XLMAIN").Activate();
      Delay(1000);
      //activate any of your application here to loose focus from Excel
      Sys.Process("MyApp").Window("WNDClassName").Activate();
      Delay(1000);
      var XL = Sys.OleObject("Excel.Application");
    }

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    8 years ago

    Hi,

     

    > Below approach is a workaround.

    Hm-m-m... It is my expectation that this code should not work as expected with the latest versions of Windows and TestComplete.

    The

    var XL = Sys.OleObject("Excel.Application");

    line of code should create another instance of Excel instead of the (expected?) reference to the existing instance of Excel.

    Have you checked in Task Manager whether or not another instance of Excel is created?

    If another instance of Excel is created but you need to get a COM reference to the already running one, the above line of code must be replaced with this: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Get-COM-reference-for-a-running-Excel-instance&sp=testcomplete