Azure DevOps Integration Test Execute version that is launched.
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Azure DevOps Integration Test Execute version that is launched.
When integrating with Azure DevOps using the TestComplete Test Adapter, you select the 'Preferred test runner' of either 'TestExecute' or 'TestComplete'.
Where would we specify whether the 32bit or 64bit version should be run?
Thanks
Brad Knutson
Solved! Go to Solution.
- Labels:
-
Integrations
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@bknutson you mentioned "Oracle query functionality and getting errors" - how are you performing the query (SQL query?), are you using ODBC?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Try to create Support ticket via the https://support.smartbear.com/testcomplete/message/ form. Hopefully, they will help you...
As a quick workaround you may try to rename <TestExecute>\x64\bin\TestExecute.exe to something else. There is a chance that test adapter will resort to 32-bit TE flavor if it (test adapter) is smart enough...
/Alex [Community Champion]
____
[Community Champions] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Champions]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Champion] signature is assigned on quarterly basis and is used with permission by SmartBear Software.
https://community.smartbear.com/t5/Community-Champions/About-the-Community-Champions-Program/gpm-p/252662
================================
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was wondering if I could rename one of those executables to try and 'trick it out' but, have not attempted that yet. I believe I have a 64bit ODBC query and setup that might work. I will just push all the setup down to the agents and hope I don't run into a conflict. If that doesn't work I will manipulate the agents more as Kitt suggested.
Thanks everyone for the assistance.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have a 64 bit operating system, you can run 32 bit applications. If you have a 32 bit application accessing a 32 bit database, then you need the correct ODBC driver. i.e. 32 bit.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks rraghvani. I think I was running into a 'mix' of database bit versions. They have been converting things but, I don't think everything has been switched over yet. However, I am able to get things working now with some 64bit ODBC so, hopefully I can just continue down that path.

- « Previous
-
- 1
- 2
- Next »
- « Previous
-
- 1
- 2
- Next »