Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DA0011 (Cannot find universe)

Status
Not open for further replies.

blom0344

Technical User
Mar 20, 2002
3,441
NL
Part of our BO user population is experiencing the DA0011 error message with version 6.5.1 full-clients.
The error will only appear in a session the first time a certain universe is accessed through running a document.
Refreshing second time always results in correct refreshing of the dataprovider.
The universes are where they should be, but documents are opened from another network location than the default setting within BO.
Is this a known bug? (sorry, at work I can only access tek-tips, no BO site)

Ties Blom

 
Brian,

I know BOB. However internet policy prohibits sites that have 'forum'in the URL. Luckily 'tips' seem to be allowed, otherwise I wouldn't been here anymore :)
I have searched BOB at home, could not yet find a clue, other than the obvious (and checked) reasons for DA0011..



Ties Blom

 
I've had a similar problem before and it was down to a combination of either that users File locations being incorrect in reporter or the users reporter pointing to the wrong location for the universe. Refreshing the reports a few times seemed to solve the later problem so i'm guessing you might be experiencing something similar.

I accessed the reg editor on my pc and went to

HKEY_CURRENT_USER\Software\Business Objects\Suite 6.0\default\BusinessObjects\psc007 User Prefs\Directories

I changed the location here and it seemed to solve the problem.

Not sure if this will help but it's worth a look.

Andy
 
Sorry for re-opening such an old thread, but we finally found a solution to this problem.
We have logged a case with BO support about this peculiar error , but were told that placing universes and documents on a networkshare would induce this problem. However, with 299 users not having an problems, we found this a bit doubtful.
Next, we deleted and re-created the user's profile and examined the registry without succes.
Ultimately we simply deleted the universes from the share and the problem resolved itself.
Lesson learned: Try simple approached first... :)

Ties Blom

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top