When refreshing a report as a ‘normal’ user I get a DA0004 error: A connection required to refresh this document is unavailable
When I log in as a General Supervisor I don’t get this error
This happens on all machines but only for some reports…
I do have a workaround but this means that I have to go into the query panel and run the query from there (for all queries, for all reports having this problem → Frustrating )
Anybody any ideas where this error comes from? Any way to avaid this without using General Supervisor or the work around mentioned above?
Do you mean to say when you edit the query and run the query from the Query Panel it works and doesn’t work only when you press the Refresh button from within the report
Looks like the universe that was used to create those reports has been moved to a different repository or domain.
Just check to see if you are picking the data from the right universe for those reports. You can go to View Data and try changing the universe to the correct one.
I am still not sure how come it is running when you go to the query pannel and run it…
We have this same issue, and have found the same workaround (manually running each data provider through data manager), but I think Cindy is on the right track asking about multiple repositories / domains. We have multiple repositories (model office and production), and must be very careful when moving reports from one to the other. After moving the updated universe to production first (if needed), we then open each document in production, open each data provider and click “save and close,” before finally saving the document and publishing to corporate documents. The “save and close” is the only we have found to guarantee that the connection information is updated properly.
There is one other possibility regarding that error message. When executing the report via ZABO running on UNIX, it was necessary to set the database connection to synchronous instead of asynchronous. This didn’t happen when we had ZABO on Windows, but that change was necessary when we moved to UNIX.
We are running BO FC 5.1.5 (not ZABO) on a windows platform with an Oracle repository.
We do have multiple doc and universe domains since recently, but the ‘normal’ users only have access to the production domain. the General Supervisor (needless to say) has access to both.
Why doesn’t this error occur for the General Supervisor? Why doesn’t this error occur for all reports built on the universes in question?
Along the lines suggested by Dwayne:
What happens if you open one of the problem BO documents in Production (with a BO user ID which has been granted access to the Test AND the Production domains), and make sure that each data provider is pointing to the universe in the Production universe domain (and NOT to the universe in the Test universe domain). Then save this BO document and re-publish it to Corporate Documents. Does this help or do the other “regular” users still encounter problems with this modifed BO document?
Welcome ozbob (are you ozbob 'cause you like the show oz ;-))
Let’s take this one step at a time. We’ll start with one possibility. A Gen Sup has everything granted. All permissions are green/enabled. One of those is the Reporter permission ‘Do Not Regenerate SQL’. This setting would prevent the Gen Sup’s queries from trying to regen and masks the DA0004 error.
Do your regular users have this setting at disabled or hidden? Disabling that would tell the queries to try and regenerate the SQL and that process would help the report realize that it can’t find the universe/connection combination it needs. Before you say no, look at permissions everywhere. If your user is in more than one group and the buttons are multiple settings and they are disabled or hidden anywhere, that setting wins.
It should occur for any that haven’t been physically pointed to the production copy of the universe. This can be done in a variety of ways…save and close the queries…use the … button.
Just had a similar problem on Oracle this morning. (DA0004 problem)
In the good old “have you tried rebooting?” style, I rebuilt the ODBC connection and the query ran fine after that. I used to be an Oracle fan, but SQL Server is so much better for working with BusObj.
With respect to the DA0005 problem, check with your DBA to see if any changes have been made within the database structure since you built the universe. Also check if there is any maintenance work being done. But if the table exists, one extreme option may be to dump the table data to a text file, drop the table, recreate it and re-populate with SQL Loader.
We also got the same error. The report was refreshing properly in the BO Full Client. We got this in ZABO 5.1.4. The error dialog box title consisted the connection name which the universe – > report was utilizing.And there was no “Details” button.
We tried to change the query by removing some objects. When the Number of Charecters (non space) in the query was :
1249 --> DA0004 ERROR (with title as connection name, and no “Details” button)
1208 --> NO ERROR
Our Solution:
We edited the SQL generated. The original SQL which BO generates doesnot utilize “alias” names for Tables. This increases the number of charecters in the SQL query.
i) Go to Edit Data Provider --> SQL. Edit the query - Use alias name for table name in query.
Ex:Original SQL:
SELECT Table1.Name,Table2.Age
FROM Table1,Table2
WHERE Table1.Key = Table2.Key
Modified SQL:
SELECT a.Name,b.Age
FROM Table1 a,Table2 a
WHERE a.Key = b.Key
ii)In the SQL viewer itself, Check the check box “Do not generate SQL before running”.
iii) Go to View Data --> Click on Query --> Definition --> Uncheck “Editable” checkbox. This prevents further modification in Query Panel.
The user login who has made all the above changes will only be able to make any further modification. For all other users the Edit Data Provider will be disabled.
Sort of…in a way that is. If you have a report that has moved between domains or repositories, it may be having trouble finding the universe/connection combination it needs to run the report. The DA0004 may not happen if your setting is enabled…essentially meaning 'Don’t try to regenerate the sql. That is why I asked earlier in the thread…
This is starting to make sense. We did migrate all of our universes from a regional repository to a central one. Before we did this, all of the users did the following:
Open report
File > Save as > Click on Save for all users > Save
Close Business Objects
Open Business Objects > Select “Production” from Security Domain
Open report
Data > View Data > Select query from Data Providers >
Select Definition tab > Click on “…” to select universe >
Click on appropriate universe
Run and save report
However, we did not experience the connection error until we began to reference Oracle views.
I am also getting this error. When I try to access teh universe on user’s machine to create areport, it shows this error “DA0004” : connection required to refresh this dosument is unavailable. i am just trying to access the universe its not even opening the universe in BO to begin with reporting.
I have checked the entry of teh database in tnsnames.ora
DO i need to do anything for Oracle based universe. We have all SQL Server based universe, they work fine, only thsi one is giving problem, does the connection needs to be physically created on the user’s machine.
Regarding Universe conections as in Business Objects Designer: No.
Yes regarding DB middleware, if you are using Business Objects Full Client (aka 2 tier).
No regarding DB middleware, if you are using ZABO (aka 3 tier), but the DB middleware will have to be created and configured on the WebI/ZABO server (aka Business Objects server).
)
(BOB member since 2003-05-12)
(BOB member since 2002-11-08)
(BOB member since 2002-06-20)
(BOB member since 2002-06-11)
(BOB member since 2002-09-19)
(BOB member since 2003-05-12)
(are you ozbob 'cause you like the show oz ;-))
(BOB member since 2002-06-20)