Unable to open DDT driver suddenly

Hi Simon,



According to our database, you have contacted us via e-mail. Please do not make duplicate requests as they complicate processing messages for us. Let us continue working via e-mail.

Probably you don't close the driver (DDT.CloseDriver) and somewhere you reach the maximum of the opened drivers...

Hi Gennadiy,



This is exactly the problem.  Is there any where I can delete those files?  After restarting the computer, I assume those resource should be released but apperently it is not.  I cannot use DDT.CloseDriver() function neither because the script has been closed already.  How can we solve this problem?



Thanks,

SC

Hi David,



There are few reasons I need to post it here even I have already send you guys email.



1. Replying in email is extremely slow and not helpful.  So far I am getting two emails responded from tech support, first email ask me to upgrade to 8.60 which is a waste of time. Second email asked if I have close the driver but there is no way to close the drivers since the script already exit and we have install new TestComplete and restart 100 of times.  He mention we can upload the project folder for you guys to take a look and didn't even leave a link.



2. Instead of waiting for respond from ONE tech support, I was hoping more people can see this problem here and can share their expereince.  I search on this site for the whole day yesterday and couldn't find any one has this problem before.



3. All our test scripts are basically data driven by CSV and Excel, with this error, we cannot run ANY test script at all.  We are just sitting here looking at this problem whole day yesterday so we need to find solution in every possible ways we can.



Thanks,

SC

I have checked out older version of my project folder from SVN and still get the same problem now.  I even try to open a new project and try to open the DDT drive, still got the same error.  It makes me think the stuff that saved in TestComplete is not in the project folder.  Something has been save in the TestComplete or Windows that causing this problem?

Hi,



I just thought of something.  Even if we close the driver properly every time at the end of the test script, what if the script failed in the middle?  Then the driver will be hanging around and there is no way to close them after the script already exit.  So this problem will still occurs from time to time.



Thanks,

SC

Hi Simon,



Even if the test execution fails, the file used by the DDT driver should be released. Please upload your project by the link we provided via e-mail.

I am uploading my porject folder.  I am sure there is something in the memory that is holding something in TestComplete.

I tried the follow and it seems to solve the problem temporary.

1. Open a new Project Suite

2. Open a new Project under the Project Suite

3. Create a new script and put the follow codes inside the script

function main() {

var Global;



Global = DDT.CSVDriver("../DataSet/test.csv");



DDT.CloseDriver(Global.Name);

}

4. Create a NEW csv file and put it in the DataSet folder in the new project folder you just created. Make sure you create a new csv file and name it different from the csv file you used before.

This is what I put in my test.csv

Username,Password,Environment

IBM1TSU01,IBM1TSU01,User Defined

5. Then run the script. If any luck, you should be able to run the script and exit out successfully.

6. Then now open up your old project folder, it seems to work now.

Does your CSV file corresponds to the values in schema.ini?

Someone had changed this file for me and my tests didn't work.

It took a while before I found this out...

Simon,



What scripting language are you using?  The reason I ask is that, with either DelphiScript or the JScript derivatives (JScript, C++Script, C#Script), you can use a try/catch/finally logic in your routines utilizing your DDT drivers.  This was a best practice I implemented in a previous life in that the finally block of each routine that created a DDT driver had corresponding code to close it.  There's not a nice clean way to get a listing of ALL the DDT driver objects currently open in a test project so you need to make sure that you close the drivers in code.  The finally block is the best way I've found to do so because it guarentees that, even if there is an error, the DDT driver will close.



Now, beyond that, I needed to write other code to detect if the DDT driver had actually been created because if you try calling DDT.CloseDriver on a driver that doesn't exist, you get an error.  so, I created this:

function CloseDriver(DriverName)

{

    if (IsSupported(DDT.DriverByName(DriverName), "ADOCommandObject"))

    {

        if (DDT.DriverByName(DriverName).ADOCommandObject != EmptyVariant)

        {

        DDT.CloseDriver(DriverName);

        }

    }   

}