AlexeyKolosov
StaffJoined 15 years ago
User Profile
Staff
User Widgets
Contributions
Warning: Windows updates break interaction with .xls files from TestComplete
Please be aware that recent Windows updates break the JET driver which TestComplete uses to interact with Excel files saved in the old format (.xls). The issue may have different symptoms, but typically it’s an error message saying “Unexpected error from external database driver (1)”. Less popular error messages are "Reserved error (-5016)", "There is no message for this error (-5016)" or "General Warning Unable to open registry key 'Temporary (volatile) Jet DSN for process". It may appear when trying to edit the Data-Driven Loop operation in keyword tests, or during test playback - any attempt to interact with an .xls file from TestComplete may trigger this error. Note that this is not a TestComplete issue: it’s Microsoft Windows updates breaking a Microsoft driver. However, TestComplete is using this driver to work with Excel files and therefore you may see unexpected errors in TestComplete. Microsoft is aware of this problem and they are planning to fix it: >>> Apart from this, Microsoft is working on a resolution and will provide an update in an upcoming release of the security patch. This is expected to be available in another 2-3 weeks or earlier. <<< https://blogs.msdn.microsoft.com/dataaccesstechnologies/2017/10/18/unexpected-error-from-external-database-driver-1-microsoft-jet-database-engine-after-applying-october-security-updates/ In the meantime, an easy workaround (and the recommended solution from Microsoft) is to use the newer ACE driver instead of the JET driver which is obsolete. For that, you need to save the Excel file in the new format (.xlsx), which will make TestComplete use the newer ACE driver in the Data-Driven Loop keyword test operation or force TestComplete use the newer driver explicitly via setting the UseACEDriver parameter of the DDT.ExcelDriver method to true in scripts, like this: DDT.ExcelDriver("c:\My File.xls", "Sheet1", true) Please see the following KB article for more information on possible workarounds: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Unexpected-Driver-Error-2017&sp=TestCompleteSolved3.3KViews6likes3CommentsRe: Warning: Windows updates break interaction with .xls files from TestComplete
Thanks for the note, Robert! Indeed, the bitness of the driver is important and must coincide with bitness of the TestComplete process. In fact, the "same bitness" rule applies not only to Excel, but also to all DB connections in TestComplete: starting from 12.40, you must pay close attention to bitness of data providers as 32-bit providers can only work with the 32-bit version of TestComplete and 64-bit providers can only work with the 64-bit version of TestComplete.3.2KViews1like1CommentRe: Is Digest Authorization supported for REST Requests in Ready API?
Unfortunately, Digest is not currently supported by Ready! API. However, you are welcome to create a feature request here: https://community.smartbear.com/t5/Ready-API-Feature-Requests/idb-p/ReadyAPIFeatureRequests If the request will get popular among our customers, devs will consider implementing the feature.1.7KViews1like0CommentsRe: Error loadig local WSDL
Looks like I've managed to reproduce a similar issue on my side. Please use our Contact Support form at https://support.smartbear.com/message/?prod=ReadyAPI to submit a case so I can escalate the case to our devs and ask them investigate the issue.901Views0likes0CommentsRe: TestComplete 9.20 - Need for Installation of DevExpress?
Hi Manuel, The fact that TestComplete records interactions with a control named TextBoxMaskBox is caused by DevExpress controls' internal implementation - this internal control is created for every control with masked input, as far as I know. However, I'm not sure I understand what problem you currently face. A recorded test should be played back successfully regardless of the way the controls are implemented. If the test cannot be played back successfully, please zip your entire project suite folder along with the log of the failed test execution and send me the archive. Make sure that messages in your log correspond to the latest version of your tests. You can do this via replying in the support case you created (M0111343) to make sure your message gets the appropriate priority.830Views0likes0CommentsRe: Process Tree is not refreshing automatically in TestComplete 9
Hi Ben, That patch fixes a problem of TestComplete 9.0, while the latest version of the tool is 9.20 that has this issue fixed. So, you can just upgrade your instance of the tool. If you cannot do this for some reason, please contact our support team directly and explain why you need the patch and cannot upgrade to version 9.20.1.5KViews0likes0CommentsRe: Expand all in keyword test
Hello Chuck, You can use the Expand All and Collapse All buttons. Follow the steps below to make them visible: 1. Right-click on any available toolbar space and select Customize... 2. Switch to the Commands tab in the invoked Customize dialog. 3. Select Edit on the 'Categories:' list. 4. Drag Expand All and Collapse All from the 'Commands:' list to the Project Explorer toolbar. Also, you can use the Ctrl-Alt-A and Ctrl-Alt-C shortcuts correspondingly.1.5KViews1like0CommentsRe: random JScript runtime error
Hello David, Could you provide us with the detailed information on your environment? Do the errors occur with the latest version of TestComplete 9 in a system with all the latest updates? Note: JScript exceptions are generated by the script engine, so you need to handle them in your code.1.1KViews0likes0Comments