There is another article that may be of interest to you:
“How to Backup a BO Universe and Maintain its CUID“

What inference i am making from this article is that it isnt safe to overwrite Universe in PROD repository with a copy of TEST for the fear of losing the report bindings in PROD even if Import wizard was used for migrating.(* in case CUID different in PROD & DEV)

To overcome this issue it best that both environments use the same CUID for a particular universe, which is only possible only if the original version in DEV was modified again and again and no save as copy was ever used in DEV, and only this copy is exported back to PROD

Thanks,
Dhiren

Case 1
User has acces to a report but when tried to open the report, gets the error.

User must also have acces to the universe on which the report was developed. Also, if the universe contains some other universes as the cores, user must be able to acces those cores too.

Case 2
User has acces to a universe and gets the error when tried to open the universe.

Solution is similar to the above. If the universe has linked cores, grant access to these cores for the user.

Case 3
User has a wid document and gets the error when tried to open this wid with locally installed web rich client.

Go to, Program Files / Business Objects / Universes folder and delete all the universes in this folder. Exit from everything about BO XI client, restart web rich client and try to open the wid again.

If the solutions above does not work,
- is there a working copy on other stages, for ex. you get the error in production environment and your uat copy is working fine.

be sure that production and uat universes are same by means of objecs, classes etc, then promote uat copy to production using import export wizard.

if this is not the case, check whether there is a local running copy and then export this to your server with designer.

- if the universe was migrated from an earlier version of BO, then (if possible) delete the universe and its cores and reimport it from the source BO system. In cases, where core universes are used by many derived universes, you may have to delete all universes and reimport them.

When you decide that the relation between the report and universe is lost forever, and you have to develop the report from the beginning;

- right click ob the report and select modify.
- report will be opened in Edit Report mode. Drag and drop a Querry Summary object from the templates tab to an appropriate part of the report. This, at least, gives you the name of the universe, objects used as the result objects and condition objects and their values.

As a last suggestion, if you are using an architecture of common core universes and derived universes from these cores for end users, keep the core universes in a seperate universe folder, and apply a rule like “never delete a core universe” on universe developers.

Also, look to Query Builder with regards to this report. See what Query Builder says about the report’s universe.

we have BO XI 3.1 and some of our users existing reports are giving this “universe not found” error.

1. when they create new personal reports-fine
2. existing public reports-fine
3. when I add myself to the same group as them and create/view webi reports -fine
4. Modified the existing report in user fav folder to see which univ it is pointing to but it hang the Webi.
5. Recieved the same report from user inbox to my inbox and ran the report. Its giving same ‘Universe not found error’
5.Tried to modify the report using my id but that also hung the webi.
6. changed my preferences so that I use “interactive” mode in webi rather than “advanced” then got the “universe not found” error.

I did try import/export of universe as well as save and export the report but both didnt helped here.

Any suggestions please
Thanks.

Great work Gazebo. Glad to hear you were able to get something that works for you. Sometimes this quickest solution is not always the most elegant. I am glad the article was able to help you see that you “unbound report” problem was not so bad. Please keep us posted on your progress with the clean-up.

Regarding a simple starter’s guide to the BO SDK, I am not sure if there is something out there already. All I find is the in-depth book on Amazon.com that might be a little too in-depth and might require significant prior .NET experience (not really a simple starter’s guide). Perhaps I should consider writing a simple BO SDK programmers start-up guide. I am still just graduating from an advanced novice and I would have loved to have such a guide to get me started mush more quickly.