I have a Business-Objects report that runs OK. I have exported this report as Corporate Documents. When I run this report from Web-Itelligence, It fails with the next messaage:
BusinessObjects server process raised an automation exception. (BOMGR0060) IDispatch error #109 Error en la conexión o en la orden SQL: (DA0005): [[IBM][CLI Driver] CLI0165E Error en la fila. SQLSTATE=01S01-99999] No se han actualizado correctamente los siguientes proveedores de datos: Freight FOB ARCELOR. (DMA0007):
I have checked The data supplier in B.O. and the results that it provide are correct. This result is a complex compute.
I have read all issues related to this one. I have really found some people that the same problem, but no solutions for that. For exemple the next isuue have the same problem.
Hi all…
Thanks by take in account me trouble.
I have read again the topics related in and none solve me problems.
I have contact with our support tecnical team and following their advice we have removed the universe and the repoprt from repository, and we have exported it again as corporate documents.
The result was the same error.
Other new clue: I have sent the report to Broadcast-Agent and it runs OK.
Hopefully this sheds some light on the automation exception error BOMGR0060 and DMA0007 issue. Apologies at the start for rambling, but here goes.
We started having problems with one user who received the infamous Automation Exception error with BOMGR0060 and DMA0007. We checked everything we could think of that might be the source of the problem: DNS, universe, connectivity, and bomain.key. We also verified our ETL process to confirm no changes were made for updating our user mapping tables in oracle as we utilize the bouser variable. What was unusual was that there were some users who could run the report and others that could not run the same report. Other users in different work centers started to experience the same issue.
After trying several options from various posts on BOB we tried removing the user from the Supervisor group for the universe the report is based upon. We then added the user back to the group et voilà! The user could run the report once they logged into BusObj or Webi.
This was our short term fix and hopefully this prevents others from reinstalling ZABO, removing universes to download from the repository, and general hair pulling.