Unable to open DDT driver suddenly

Hi Robert,



Thanks for the respond and the piece of code.  I will give it a try and see if it will catch somoe drivers that was previously opened.  What I do not understand is how come something still hold up the system after restarting the windows mutiple times.  By the way, we use Jscript to do all our test scripts.



On the other hand, can you explain a little bit more on "finally" block you mentioned?  May be some examples?  We want to make sure this bug will not happen again.  It doesn't seems like the tech support people will be able to help find the root cause by looking at the project folder I uploaded.



Thanks,

SC

Hi Patrick,



Thanks for pointing that out.  But our csv file does not have any linkage to schema.ini.



Thanks,

Simon

Simon, 



If during the course of running your tests you're opening more than 64 DDT connections to CSV files, even if they are all the same CSV file, you'll end up not being able to open them up until you close TestComplete and re-open.  This is why you need to make sure that, as soon as you are done with a DDT connection, you close it.  And actually, depending upon how you're doing so, you may be creating the connections outside of the scope of the TestComplete application environment and so those connections may still be open in Windows...



As for the finally block, see http://msdn.microsoft.com/en-US/library/k4hea629(v=VS.80).aspx

Hi Robert,



Thanks for the explaination.  It will take some time for us to change all the codes to close the drivers.  In the mean time, if we get this problem again, what is the best way to reset this "64 counters" thing? 



Thanks,

SC

It's not a matter of a "reset"...shut down TestComplete and start it up again and run your test and, if you haven't closed all your drivers, you'll run into the problem again.  It's simply a matter of making sure that you "clean up" after yourself when creating the connections.

Hi Robert,



I understand we will need to make sure all drivers are closed from now on.  But once a while we still run into problem that the script error out before the close driver function gets to execute.  All it takes is to get it happen once, the project will be locked up again.  I will have to use the method I mention above to get this clear out.  So obviously there is something stage inside TC and I was just hoping may be you would know an alternative way to get this clear out.  If there isn't anything you are aware of, I guess will have to wait for SmartBear tell me a way to fix my project so it won't be lock up as easy.



Thanks,

SC

Hi Robert,



I have try to use the codes you provide above to create a event handler.  I am getting error when trying to run the first IsSupported statement.  Can you shade some lights on this?  Here is my codes.

function GeneralEvents_OnStopTest(Sender)

GeneralEvents_OnStopTest(Sender)

{

if (IsSupported(DDT.DriverByName(Global.Name), "ADOCommandObject"))

{

if (DDT.DriverByName(Global.Name).ADOCommandObject != EmptyVariant)

{

DDT.CloseDriver(Global.Name);

}

}

if (IsSupported(DDT.DriverByName(Local.Name), "ADOCommandObject"))

{

if (DDT.DriverByName(Local.Name).ADOCommandObject != EmptyVariant)

{

DDT.CloseDriver(Local.Name);

}

}

}

The error is:

An exception occurred in the "DDT_Close" unit at line 3:

Microsoft JScript runtime error

'Global' is undefined



Global DDT has already been closed in this case, but your if statement should check whether global exists right?

Most likely the identifier "Global" is not in scope for the routine.  Where is Global declared or defined?  You need to make sure that it is available to the unit where your code is declared (using a //USEUNIT call perhaps).

Hi All-

I've read this thread with interest as I've created a simple DD script but haven't included the CloseDriver line because the DD example/tutorial that came with TC did not have it. Am I to understand that if I run my script more than 64 times without closing the driver I'll get the same error that Simon is experiencing? Even if it's over the course of several months with many re-bootings in between?



Chris

Chris,



It is 64 simultaneous connections in scope of the application.  In my experience, rebooting the box, even shutting down TestComplete and restarting it will "clear" those connections.  However, it is still good practice to incorporate those CloseDriver methods in your code.





Please note that both articles on DDT mention this.  (see http://smartbear.com/support/viewarticle/13855/)

The Jet Engine has a limitation of 64 connections per process. So, after your test finishes with a CVS file, it is recommended that you close the connection by calling theDDT.CloseDriver method.