boundary="----_=_NextPart_001_01BF61BD.C2A55D96"
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.
Listserv Archives (BOB member since 2002-06-25)
David,
We had that same thing happen with one of our reports. The developer that created the report could not open it. So how did we solve it? This may sound strange, but I had him send me the report. I opened it, then saved it as a different name, sent it back to him, and he was able to open it. We never did figure out what caused it; probably a misallignment of the planets.
Michael Welter
Sr. Technical Analyst
AirTouch
I created three reports in version 5.0 that access data from the same universe. They have all been moved to the repository. Two of them run fine, however, one of them cannot be accessed. An error message that states “You are not authorized to use this document (FRM0008)” appears when I attempt to open the report. I checked the properties on all three reports and they are the same. By the way, I did access this report on the first attempt this morning, but subsequent attempts resulted in the above mentioned error message. I even logged into Business Objects as another user and still could not access the report.
Listserv Archives (BOB member since 2002-06-25)
In a message dated Tue, 18 Jan 2000 10:53:30 AM Eastern Standard Time, “Caddell, David P.” CaddellD@PRISMPLUS.COM writes:
I created three reports in version 5.0 that access data from the same universe. They have all been moved to the repository. Two of them run fine, however, one of them cannot be accessed. An error message that states “You are not authorized to use this document (FRM0008)” appears when I attempt to open the report. I checked the properties on all three reports and they are the same. By the way, I did access this report on the first attempt this morning, but subsequent attempts resulted in the above mentioned error message. I even logged into Business Objects as another user and still could not access the report.
Any suggestions would be appreciated.
Thanks you,
D.P. Caddell
The only thing that I can think of is that someone - in between the time you were able to access the report and the time you got this message - deleted the document from the repository. This topic comes up a lot, but is probably worth repeating again.
When you send a document to the repository, it gets a flag set in the .REP file that says, “I am a secure document.” From that point on, when a user opens that document a query is sent to the repository to see if the user has access to that document.
Now, if that document is ever deleted from the repository, that query will fail. But rather than provide a message like “Unable to determine security settings for this document” Busobj just assumes that you don’t have access to it, and provides what it thinks is an appropriate message. There are two ways to fix this:
-
Re-export the document to the repository. Which can be a neat trick if you can’t open it, or…
-
Have a General Supervisor open the document and do a “Save for all users” operation.
The Save for all… removes the “security bit” that got set when the document was first sent to the repository. At that point, anyone can open the document.
So, check to see if the document is still in the repository. If it is, make sure that you actually have access to it (make sure that permissions have not been revoked). If permissions have been revoked, then things are working they way they are supposed to. 
If it is no longer in the repository, then the solution I outlined above should work.
Regards,
Dave Rathbun
Integra Solutions
www.islink.com
Listserv Archives (BOB member since 2002-06-25)
I am testing version 5.1 and if I try to open a report which was retrieved using version 4.1 I get the message:
You are not authorized to use this report
If I try doing the same thing using General/Supervisor than there is no problem. I know there must be some type of security blocking any other type users from doing this but I can’t find it.
Any help is appreciated.
joe
Listserv Archives (BOB member since 2002-06-25)
To get around the problem you could, as general supervisor, do a Save As and check Save for All Users. This will make it available for other users. Michele
Listserv Archives (BOB member since 2002-06-25)
Thanks Michele, I don’t have a problem when I try to download the report from the repository. The problem only comes when a 4.1 version of a report was saved onto an individual PC and the user tries to open that report using 5.1. The only way you do not get a problem is if you retrieve the report again from the 5.1 respository.
joe
Listserv Archives (BOB member since 2002-06-25)