ContributionsMost RecentMost LikesSolutionsRe: Unable to open DDT driver suddenlyHi Chris, I think we are reading the same code example when we first starting to write DDT drivers. I do not have this problem at all until we start to have a large team start coding hundreds of test cases with DDT drivers. After a few months, we start getting this error. So yes, I suggest you start closing the drivers now to avoid my problem. Thanks, SimonRe: Unable to open DDT driver suddenlyHi 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? Re: Unable to open DDT driver suddenlyHi 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, SCRe: Unable to open DDT driver suddenlyHi 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, SCRe: Unable to open DDT driver suddenlyHi Patrick, Thanks for pointing that out. But our csv file does not have any linkage to schema.ini. Thanks, SimonRe: Unable to open DDT driver suddenlyHi 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, SCRe: Unable to open DDT driver suddenlyI 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. Re: Unable to open DDT driver suddenlyHi, 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, SCRe: Unable to open DDT driver suddenlyI 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?Re: Unable to open DDT driver suddenlyHi 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