A User is trying to open a Desktop Intelligence Report and is getting the following error.
I am sorry to have to ask this question again but I can not find anything about this in BOB for release XIR2.
I am very new to BO and when I see log in as General Supervisor it appears to be something that was in a earlier version of BO?
I have full admin rights to my login and I can not open this file.
I have also looked on Business Objects web site and it appears that you must have created a backup before you have this issue.
Thanks in advance for any help you can shed on this.
Guy
Moved from the “Semantic Layer” forum (which is for Designer (or BusinessViews) questions) to the “Building Reports” ==> Desktop Intelligence (XI r2) sub-forum.
I am sorry for not putting this in the correct forum.
The document(s) will not open to allow a save as. Is there another way?
I have tried to login with the Offline checked to see if that would work but it doesn’t.
I know this is a stupid question but when you say “save as” you are talking about opening the file then clicking file/save as correct?
Because I can not get the file to open it seems like this is not a option.
I tried the following test this morning (XIr2 w/sp1).
-I created 2 reports on my local machine with Desktop Intelligence.
-I saved the first report with “Save for all users” checked. I saved the second report without checking the “Save for all users” box.
-I exported both reports to a public folder, logged on to BOE (Infoview) and deleted both reports.
-The 2 local .rep files still exist on my local machine, but I get the “you are not authorized (FRM008)” error when I attempt to open either report using Desktop Intelligence.
So the behavior Im seeing is that the original report author can no longer open his original local copy of the report after it has been exported and then deleted from the repository. Yay…
Yep I remember that this behaviour has been already described in an other post. BO keeps in mind somewhere ( ) security on this report. I mean you have no rights to use it.
Did you try a work around using VB to change the owner of the report / rights to open it for all users …
-I created a report, save for all in a temp directory and then saved with same name in user docs and exported.
-Deleted file from repository and cannot open the original file that was exported.
-I can open the first copy I saved off before export however.
I did a binary compare of the 2 copies and can see that the act of exporting modifies the local file. there are several sections of information stored in the exported copy that do not exist in the one I saved off before export.
So for now, my workflow will be save a local copy, save again in different location and then export.
When a report is published, BO sets a security bit. It knows the magic id of the repository. This is done so that a user from a different repository cannot open the report. When it is unpublished, it is meant to be not usable by ANYONE.
But in BO Classic a General Supervisor has access to everything, so he could open the local copy of the report and do a save for all users. That would remove the security bit so other users could open the local copy. Is there no equivalent process in XI? :x
I see that Classic Business Objects also modifies the local .rep file when exporting. The difference is (as the previous poster points out) I can still login as supervisor and open the report, even after it has been deleted from the repository.
That is the behavior I would prefer to see in XI when dealing with Desktop Intelligence reports. I think it is more then a minor annoyance that there is a way to lock yourself out of a report, forever.
Here is my new Desktop Intelligence idiom:
Save twice,
Export once,
Or Ill be a Deski Dunce .
No. BO doesn’t feel that this is a problem. There is a workaround. Build an object that has the same name. Note it’s location in the CMS. Put your report on that location and then try to open it. It might work.
I did something similar with a universe and it worked fine.
Thanks a lot for your reply Steve! I have been using that workaround but it surely doesn’t look good when the same user complaints about yet another report not working… I have couple of users who reported atleast 4 or 5 such documents
Mostly, this happens with some reports migrated from 6.x to XIR2. If it was happening to all the converted reports, then I could have taken care of it at the time of conversion. Unluckily, it happens with only few of the converted reports and I’m yet to figure out why.
This could also happen to new Deski reports created in XIR2 if you forget to Save it for All Users and do not press the Save button again
I also had hundreds of FC reports that I converted and have had this problem with may be 12 reports so far. There are other people on this forum who got this error message which can’t be a mere incident. I think there is a glitch in the software which causes this issue.
In XIR2 you can recover these reports using the following workflow.
Launch Deski and create a simple report based on the same universe and connection as the report that you are trying to recover.
Save for all users and export to the repository (preferably into the same folder as you want the recovered report to reside in)
Launch the CMC > browse via ‘Folders’ > ‘Objects’ and click the report you just uploaded to the repository.
Make a note of the file name- should be something like:
“frs://input/a_…encrypted text…etc.rep”
On whatever machine the filestore is located, browse to this location.
Once you have found the report, copy its encrypted name.
Rename the document you are trying to recover with the above name and paste it into the above location in the filestore (replacing the report that is already there.)
6… The report is now unlocked and back in the repository.
(BOB member since 2006-10-23)
(BOB member since 2003-09-25)
(BOB member since 2004-06-02)
(BOB member since 2004-06-02)
(BOB member since 2004-05-20)