Hi Scott,
The case is that when you run ABS interactively (i.e. from your desktop), the tested application and TestComplete start in your user session as well (as a processes spawned by ABS). The tested application can draw its UI and TestComplete can access and interact with it.
When the ABS macro is executed as CI task, it is started by ABS service running (by default) under the system account. System account does not have either its own desktop or access to your one so that OS can draw application's UI. That is why TestComplete cannot find the tested objects.
I would recommend you to search ABS (
http://community.smartbear.com/forum/?mode=singleForum&forum=0331ec96-8718-4144-be56-82bc5f49888d) or this section of the forum as there were a few discussions on exactly the same question.
The possible solutions are either to start ABS service on behalf of dedicated user or use the RunInteractive utility provided with the ABS. Note, that regardless of the approach you select, it will be required to have an unlocked system with the logged-in user to start TestComplete and tested application on.
