Same build does not necessarily mean that the object doesn't have dynamic properties. Especially when working with web applications and certain .NET structures, the properties of an object may change which will make situations like you encountered occur. Check out the following video for some tips as to how to handle this.
http://smartbear.com/support/screencasts/testcomplete/reliable-tests-for-dynamic-objects/Another possibility may be that the object itself is not incorrectly identified but may be a timeout issue. You're requesting actions against a component whose parent component does not exist for some reason. It could be that the timing of your automation may be attempting to perform that action before all the components have resolved. You can try putting a "Delay" call to test this theory. You can also mitigate this somewhat by using the WaitAliasChild method as well as increasing the Auto-wait timeout in your project.
