cancel
Showing results for 
Search instead for 
Did you mean: 

TC12 attempt to work with closed (excel) driver after updating to Office 365

SOLVED
Highlighted
Regular Contributor

TC12 attempt to work with closed (excel) driver after updating to Office 365

 

This has been working for over 5 years, but started failing after I updated to office 365.

Following the update,  I can no longer run testcomplete from my laptop in this particular project.

It does not seem to makle any difference if I am opening DriverG with DDT.ExcelDriver(aInputFile, aInputSheet, false)

with DDT.ExcelDriver(aInputFile, aInputSheet, true) or omitting the parameter completely.

When I try to do aqConvertVarToStr or DriverG.EOF() I get an error "attempt to work with closed driver".

I can succesfully use DriverG.Name and it prints driver is Excel0

 

var DriverG = DDT.ExcelDriver(aInputFile, aInputSheet);

Log.Message(" driver is " + DriverG.Name);
omit = aqConvert.VarToStr(DriverG.Value(omitHeader));
Log.Message ( "omit is " + omit);

var row = 0;
var tempValue;
while (! DriverG.EOF() )

1 ACCEPTED SOLUTION

Accepted Solutions
Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

so although test complete claims to be a 64 bit application,  when I added the driver for 32 bit testcomplete after removing the 64 bit driver, it works as it has been.

8 REPLIES 8
Community Hero

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

What version of TC 12 are you running?  What "bitness" of Excel is installed?

 

Note that there are some requirements wrapped around bitness for using Excel versions.  See https://support.smartbear.com/testcomplete/docs/testing-with/data-driven/excel-storages.html#require...  I'm assuming that, when you upgraded to 365, something changed in those areas.  See if any of this helps.


Robert Martin
[Community Expert Group]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Extensions available
Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

Thanks Robert.  I have office 365 version of excel  and test compete 12.10.590.7 

Curiously,  I can use the ddt  driver with another project from my laptop and it works fine.  This leads me to suspect there is some setting on the project that is screwing up the ddt driver but have not been able to find it.

Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

so I tried creating both a new project as well as a new  project suite,  this did NOT work for my spreadsheet but did for my co-worker's spreadsheet.  I noticed that his spreadsheet is  using the extension  .xls  where mine is stored as .xlsx   unfortunately,  I am still getting the error after I copied my spreadsheet to xls format....

Community Hero

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

Again... verify the bitness.  Are you using the 64-bit Office 365 or the 32-bit?  

 

IIRC, in order to use the Excel DDT, you need to have a 32-bit Excel ACE driver installed, even if you're using 64-bit TestComplete.


Robert Martin
[Community Expert Group]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Extensions available
Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

64 bit Office / Excel  and 64 bit test complete .  Am double checking the link now......

Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

so although test complete claims to be a 64 bit application,  when I added the driver for 32 bit testcomplete after removing the 64 bit driver, it works as it has been.

Regular Contributor

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

Does NOT work as it has been.  But I can read .xls files without getting the error.

Community Hero

Re: TC12 attempt to work with closed (excel) driver after updating to Office 365

TC 12.10 is not 64-bit, it's only 32-bit.

Also, Microsoft had done some strange patching a while back which, for the JET engine, required some necessary downloads.  If you set ACE to true, you shouldn't need it but you do need to make sure that you have a 32-bit driver for excel installed.


Robert Martin
[Community Expert Group]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Extensions available
New Here?
Join us and watch the welcome video:
Top Kudoed Authors
Join the September Hub-bub to show off, learn and win