Please describe the problem in detail. What do you mean by "batch run"? If you mean that the application is launched from a batch file, please send us the file at email@example.com. Also, please zip the entire TestComplete project suite folder along with the failed test execution log and send us the archive at firstname.lastname@example.org so we can investigate the problem here.
What i meant by batch execution was, TestComlete enables me at the project level to run mutiple scripts in a sequence (i.e. the batch i referred to). Now what happens particularly for me is when I run them in sequence back to back (approx i am having some 50 scripts), the initial scripts gets executed perfectly with no issues, but after 30% of execution is completed i get this problem when test complete warns the user with messages like "Object does not exists" or "object not identified" or "Improper command".
I suspect this has to do something with the way the TestComplete hooks works with Java. Is it possible for us to modify some where in configuration to overcome this or it may be that we are making wrong interpretation. At this point of time i cannot attach the project suite due to some reasons.
What is most likely happening is that the scripts you are executing are actually executing too fast for the AUT. Those three errors you mentioned are the types of errors you will usually get when the scripts try to access an object that has not become available to the scripting engine yet due to delay in the AUT.
The obvious short-term solution is to add calls to "BuiltIn.Delay" in various areas of your scripts to apply the necessary delay times. However, this does not account for the variability in application delay. What I would recommend is for you to read up in the TC help on methods like WaitWindow, WaitChild, WaitProcess, WaitWinFormsObject, etc, that put a more dynamic factor to your scripts.
Automated Testing Evangelists
Definition expert - noun - Unknown drip under pressure