Business Objects R3 Adapter v1.74 causing jobs to abort
I've already filed a case with tech support, but I was wondering if anyone has experienced this problem with the Business Objects R3 Adapter version 1.63-1.74 where the Tidal job gets launched and then almost instantaneously gets aborted. And if there are subsequent Tidal jobs dependent on that aborted job, then those jobs will never get run (stuck on Waiting on Dependencies...) until the job status gets manually set from Aborted to Completed Normally*
The pattern is random, and the BO reports are being generated, it's just the Tidal job status returns Aborted when the external id cannot be found. Any suggestions?