I deleted a document off of the repository. When I try to open it (stored on my hard drive), I receive the error message “You are not authorized to use this document”.
Can someone tell me why I’m receiving this error and how to correct it?
Thanks!!
Joanna
Listserv Archives (BOB member since 2002-06-25)
X-cc: FRAN.BOCAIN@chase.com
Funny someone else is having similar problems! Unfortunately I don’t know the real root of the problem, much less how to fix it. However, I do have some ideas. What starts the problem is a failed or incomplete save procedure on a report. You deleted the document from the repository, but BO is now looking at the hard drive version, so I think the repository issue is not relevant. I will assume your BOMain.key is in sync with the document on your hard drive, and that you’re properly connected. The only way I get rid of the problem is not only to exit BO, but to restart the operating system. Somehow, BO - or the OS - forgets to update the disk file table of content, or at least part of it. Or something like that.
Do you run an NT 4.0 machine? I do, and the BO release is 4.1.2, though it may make no difference. What leads me to believe it has to do with the FAT or the NTFS is that from the Explorer, I can sometimes display a file but if I try to copy, rename or move it, it says the file does not exist - even as it’s showing all the file properties! This is probably the same thing: The disk actually contains two identical TOC to locate its files, but somehow under a certain type of recovery procedure, the update is not made to both and then they’re out of sync. Rebooting has been the only way out. By the way, I have actually had a similar experience, not with BO, but a Word document. Word suddenly went silly and would not save my file. Explorer showed it but would not let me touch it. This could be a Microsoft bug, not BO’s. Incidently, your C:\TEMP folder should contain the last image of the BO document before you opened it. Under crash conditions, this temp file does not get deleted, and if you want it back, simply rename it to xxx.REP to reuse it, though it should not be necessary. The file names vary, but never have an extension. Typical names are: 00cc3, 014b58 or 007a3 - yes, those are file names. Check the size and date for clues. Regards,
Alexandre Courtney Barbier
Listserv Archives (BOB member since 2002-06-25)
Joanna, I have seen this problem occur when the document had been created with an Id other than YOURs, and you try to access it. You would need to have the General Supervisor open the document and do a “Save As…” and make sure the option “save for all users” checked.
-Sai
Joanna wrote----------
I deleted a document off of the repository. When I try to open it (stored on my hard drive), I receive the error message “You are not authorized to use this document”.
Can someone tell me why I’m receiving this error and how to correct it?
Listserv Archives (BOB member since 2002-06-25)
Funny someone else is having similar problems! Unfortunately I don’t know the real root of the problem, much less how to fix it.
I am pretty sure this is the way it is supposed to work. You must keep in mind the overall security picture. I don’t know technically what happens, but I do know you MUST save the report for all users PRIOR to deleting it from the repository (or else only a general supervisor can open it). This report was on the repository and therefore repository security applies. When you delete it from the repository then NOBODY has access to it any longer.
Thanks,
Greg Mills
s-greg.mills@usa.conoco.com
ETN/DUCOM 442-5597
(580) 767-5597
Listserv Archives (BOB member since 2002-06-25)
You must not be accessing your BOMAIN.KEY file.
Listserv Archives (BOB member since 2002-06-25)
My users have run across this problem before. Sometimes, when I make a change to a report and re-export it the users try to import it and they get this error message. I am logged in as Gen Sup and export the report to the top level subfolder. The users have to get out of BO and log back in to import it.
Julie
Listserv Archives (BOB member since 2002-06-25)
In a message dated 98-08-05 22:16:55 EDT, you write:
I deleted a document off of the repository. When I try to open it
(stored on my hard drive), I receive the error message “You are not authorized to use this document”.
Can someone tell me why I’m receiving this error and how to correct it?
Here’s my take on what is happening… perhaps someone from BusObj can confirm if I am correct.
When you export the document to the repository, it gets assigned a unique document ID. This is to keep track of the information in the repository database. That ID is (apparently) stored in the document (on your hard drive) as well. In other words, there is a little tag in the file that says, “I’ve been exported and therefore am now a secured document.”
When you open the document, BusObj detects that “tag” and says, “Hold on, I have to see if you are authorized to open this document.” A quick query against the repository information will let it know if the document is still valid, and b) if you still have permission to read it. (You would expect that if you owned the document this would not be a problem.)
Fast forward: document has been deleted from the repository.
When you try to open the document, BusObj sees the same “exported tag” and tries to validate the security. Since the document no longer exists in the repository, the check fails! Therefore, you are not authorized to use this document. Strange as it may seem (since you have created the document to begin with) you cannot open that document ever again. Nor can anyone else.
Except the General Supervisor. Nothing can ever be locked away from that user (fortunately).
The General Supervisor ignores the security check, and therefor can open any document. By opening with General Supervisor and using the “Save For All Users” option, you effectively remove the “tag” that says security should be checked on the document.
The bottom line is that you should do the “Save for all users” option before deleting the document from the repository. That way you don’t have to bother the General Supervisor.
By the way, this same issue is possible when exporting universes. Once the universe has been exported, you should not delete it from the repository or the General Supervisor will once again have to ride to the rescue!
Regards,
Dave Rathbun
Integra Solutions
www.islink.com See you in Orlando in… a few weeks!
Listserv Archives (BOB member since 2002-06-25)
This is to confirm that what David describes below is correct.
But if you’re asking yourself how this “security check” happens so quickly on your local hard drive, the answer is in the OBJECTS.LSI file. This file contains the list of documents and universes to which you have access and gets updated with every login.
When the document does not exist in the repository, it obviously is also absent in the OBJECTS file. Because the local copy still has the “security tag,” it cannot verify that you ever had access to it, so it prevents you from
opening it.
Simply put, this system works to prevent unauthorized access of files, regardless of whether you ever had access to the same.
Regards,
Luis Gonzalez
From: David Rathbun Integra Solutions [SMTP:DRathbun@AOL.COM]
Here’s my take on what is happening… perhaps someone from BusObj can confirm
if I am correct.
When you export the document to the repository, it gets assigned a unique document ID. This is to keep track of the information in the repository database. That ID is (apparently) stored in the document (on your hard drive)
as well. In other words, there is a little tag in the file that says, “I’ve
been exported and therefore am now a secured document.”
When you open the document, BusObj detects that “tag” and says, “Hold on, I
have to see if you are authorized to open this document.” A quick query against the repository information will let it know if the document is still
valid, and b) if you still have permission to read it. (You would expect that
if you owned the document this would not be a problem.)
Fast forward: document has been deleted from the repository.
When you try to open the document, BusObj sees the same “exported tag” and tries to validate the security. Since the document no longer exists in the repository, the check fails! Therefore, you are not authorized to use this document. Strange as it may seem (since you have created the document to begin
with) you cannot open that document ever again. Nor can anyone else.
Except the General Supervisor. Nothing can ever be locked away from that user
(fortunately).
The General Supervisor ignores the security check, and therefor can open any
document. By opening with General Supervisor and using the “Save For All Users” option, you effectively remove the “tag” that says security should be
checked on the document.
The bottom line is that you should do the “Save for all users” option before
deleting the document from the repository. That way you don’t have to bother
the General Supervisor.
By the way, this same issue is possible when exporting universes. Once the universe has been exported, you should not delete it from the repository or
the General Supervisor will once again have to ride to the rescue!
Listserv Archives (BOB member since 2002-06-25)
X-cc: Jeff.Rentsch@GECAPITAL.COM
For information, we recently had a problem running on NT / oracle where if you used reports off line and then logged in online (say a week later) suddenly you would lose the right to open some reports! only the GS account could then unlock them - this was being caused by a repository corruption.
I must have done something stupid, because suddenly I get this error message when I try to open some reports on my hard drive that I wrote several days ago:
“you are not authorized to use this document”
What did I mess up?
-Jeff
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’ Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
–
BODEV
Listserv Archives (BOB member since 2002-06-25)
What did you do to resolve it?
Jodie
Listserv Archives (BOB member since 2002-06-25)
This Report should be saved for all user check baton in the saving Dialogue box
This problem because somebody open the report for modifications and save it but not for all users
Mrehem
For information, we recently had a problem running on NT / oracle where if you used reports off line and then logged in online (say a week later) suddenly you would lose the right to open some reports! only the GS account could then unlock them - this was being caused by a repository corruption.
- Rob.
Listserv Archives (BOB member since 2002-06-25)
The last I knew (before leaving the contract) it was being looked at by BO. since the corruption was also causing problems with V5 Rob.
In message <3B633D1F4A4BD3118FAF00508B08F336012BD665@wdwexccp05.noceast. dws.disney.com>, Schott, Jodie Jodie.Schott@DISNEY.COM writes
What did you do to resolve it?
Jodie
For information, we recently had a problem running on NT / oracle where if you used reports off line and then logged in online (say a week later) suddenly you would lose the right to open some reports! only the GS account could then unlock them - this was being caused by a repository corruption.
- Rob.
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’ Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
–
BODEV
Listserv Archives (BOB member since 2002-06-25)