Unspecified Error

It depends upon what you are doing during those tests.



The only time I've personally experienced that error is if I've tried opening more than 64 connections through the Microsoft Jet database engine (more than 64 DDT.CSVDriver's for example).



Check through your code and make sure that you're properly closing database connections and other such things.  Without knowing more detail about how you're executing your tests, that's the best place I can suggest to start.

Hi, we are experiencing "Unspecified Error" messages too & then Test Complete dies, we dont lose any files or anything like that, but it's interesting that you say you have experienced similar when your using DDT... we are using DDT to access Excel workbooks and although we do close the connection perhaps there is something going wrong? and they are not actually being closed...





Is there a way of checking if there is a connection already opened before trying to open a new one?

or a way of ensuring that they are closed??



kindest regards

K



P.S> should say we are using 7.51 and prior to that have had no issues

Hi,





To help us investigate the problems, please follow the steps below:





1. Download a free trial version of AQtime 6, which is our profiling tool, from our web site. You can request it on the following page of our web site:

http://www.automatedqa.com/downloads/aqtime/





2. Install the tool.





3. Start AQtime with the -NotOpenApp command-line argument. For example, you can use the following command line:

"c:\Program Files\Automated QA\AQtime 6\Bin\AQtime.exe" -NotOpenApp





4. Select the 'File | New Project From Module...' main menu item.





5. In the Open File dialog, select the TestComplete.exe file and click Open.





6. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.





7. Select the "Options | Options..." main menu command - the Options dialog will appear.





8. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.





9. Click the Run toolbar button (the green arrow) or press F5 to start profiling.





10. AQtime will start TestComplete and trace all the exceptions that will occur in the application until it is closed.





11. Reproduce the problem in TestComplete.





12. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.





13. Save the panel's contents to an HTML file and send me the file via our Contact Support form.





Thanks in advance.

Hi Robert / Alex,



I'll try installing AQTime and send the report to you soon. In the meanwhile, please take a look at the pjs file present in the attached zip file and let me know if you find anything wrong with it. It has a lot of visualizer information that I did not delete it on purpose as I wanted to keep the file intact.



Please note that this is a copy of the file that I create and when the tests are done, the file is gone! Even the log files vanish! It's like leaving no evidence after a crime :D



I made use of the OnLogMessage event and re-directed the log messages and remarks to a text file to have see what's being logged and all I see in the file is Exception - Unspecified error.



I really need this thing to work ... please help.



Regards,

GJ

Hi,



The PJS file you've posted here is not enough. Follow the instructions from our previous post.

Hi,



These two dialogs (images attached) appeared on the same machine on which I get the Unspecified Error issue.



I clicked 'Yes' on both of them and TestComplete.exe got terminated.



Does the message got to do anything with the issue I am facing?



- GJ

Hi,





I cannot say for sure whether this issue and the initial one are related. As for the latest issue, most probably, it is caused by the fact that TestComplete's process was abnormally terminated previously. Let me know if TestComplete does not work properly after you choose "Yes" for such dialogs.





BTW, the latest issue can also be caused by a malfunctioning hard disk on the problematic PC. So, if you suppose that this situation can take place, check whether the issue can be reproduced on another PC and check the hard disk.