chicks
Regular Contributor
Joined 14 years ago
User Profile
User Widgets
Contributions
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....2.5KViews0likes5CommentsRe: 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.2.5KViews0likes6CommentsTC12 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() )Solved2.5KViews0likes8Commentsjava bridge questions
I've got two errors. The second of which came up when I was trying to debug the first. 1) ssl handshake error When I try to do a send request using a java api I am getting a ssl handshake error with line 998 indicated 992 api = JavaClasses.tests_excentus_rl_rise_integration_api.RiseAPI.newInstance; if ( api == null) { Log.Message ( "api matched null !" ); } else { Log.Message ( "api NOT null"); } 998 var responseText = api.sendRequest(ipAddress, port, processor, xmlStr, sslCertification); However this works when I try it from my laptop (TestComplete) but fails on my jenkins box. (TestExecute) Note that this also works using test execute for one flavor of processor but fails for other flavors.... 2) can't instantiate new java class I wanted to confirm that problem 1 above was happening on multiple TestExecute boxes. Although I had previously set up the java bridge on my laptop and then the jenkins box and believe I've duplicated those steps on the other TestExecute box, I seem to be missing at least one step. I'm getting "Object doesn't support this action" with this line indicated. 992 api = JavaClasses.tests_excentus_rl_rise_integration_api.RiseAPI.newInstance; I copied the jar files over and specified the java bridge in the test execute options. I added the jar file path to the system path variable as well, even though I have not done that there on the original TestExecute box.938Views0likes1Comment