ETUtilityerror when attempting to run DV in Timeslips 2014

A client (Timeslips 2014 SR2) has a linking error in A/R as reported by running DV but I cannot get DV to run with the options checked for both validation and integrity.  It will run with just validation checked - but does not fix anything.  As soon as I try to run with 'integrity' box too checked I get box saying Timeslips has encountered an error - invalid filename or file does not exist.  Details reveal system error, ETUtility error.  Tech said to reinstall BDE, delete locks/login/temp files. delete pdoxusrs / paradox files which I did and still get the same error.  Have even tried on a stand alone workstation not on their network.  

Does anyone have any more suggestions?  

Many thanks 

Jane Giles

Parents
  • 0

    The ETUtil error is almost always due to lock files in the database.  Copy the database folder to a different location, delete the PDOXUSRS.LCK and PARADOX.LCK files from the installation folder, delete LOCKS.DB and LOGIN.DB from the database and make sure there are no subfolders contained in the database that shouldn't be there.  In other words, no databases inside the database, no backup files inside the database, etc.  

    You may also want to reinstall Borland per KB 13563.

    Make sure it's cleaned up.  I've seen more than one instance where an old installation of the program was intermixed into the database folder, or the database folder was the parent to the installation folder.  All bad practice and bound to cause issues.

    The knowledgebase is at http://support.na.sage.com and is also accessible from the portal at customers.sagenorthamerica.com (or partners.sagenorthamerica.com for partners, more specifically)

Reply
  • 0

    The ETUtil error is almost always due to lock files in the database.  Copy the database folder to a different location, delete the PDOXUSRS.LCK and PARADOX.LCK files from the installation folder, delete LOCKS.DB and LOGIN.DB from the database and make sure there are no subfolders contained in the database that shouldn't be there.  In other words, no databases inside the database, no backup files inside the database, etc.  

    You may also want to reinstall Borland per KB 13563.

    Make sure it's cleaned up.  I've seen more than one instance where an old installation of the program was intermixed into the database folder, or the database folder was the parent to the installation folder.  All bad practice and bound to cause issues.

    The knowledgebase is at http://support.na.sage.com and is also accessible from the portal at customers.sagenorthamerica.com (or partners.sagenorthamerica.com for partners, more specifically)

Children