I got this error in a strange situation yesterday. Here is what happened:
We were moving a group of new reports from Development repo to Test Repo. They were exported sucessfully into the repo and in to the ‘Testing’ group of users. The export took place about noon. Our testers had all been in BusinessObjects since early that morning. They then got the notification that the export was complete. They imported the new reports from the repository and then tried to open them. That is when they got the error. They emailed me about it and this morning I went in with their id’s and opened the reports with no problem. I called them and they tried again and they got in with no problem. There were no changes made in Supervisor as I am the only one that can do that.
My question is: Would the testers have to logout and log back in to BO before they could get to these reports? That is the only thing that I could think of, but it doesn’t seem as if that should be necessary. My thought was:
Testers logged into BO yesterday morning and at that time, BO
checked to see what documents they had access to in the repository, let’s say reports A, B and C.
Meantime, New reports are sent to the repository with their group
having access, let’s say reports X, Y and Z. * They import the reports X, Y and Z as BO can tell they have been
added to the repository, however, it is still under the impression that A, B and C are the only reports they have access to, thus the you are not authorized error.
That is the only thing that I could think of but I thought that the report access was a little more dynamic than that. Does anyone have any thoughts on this??
It sounds like you’ve figured it out 100%! Yes, the users have to log back in to gain access to new reports.
Cheers,
Luis
From: Carter, Maria [SMTP:mcarter@HRSERV2.IMS.ATT.COM]
Hi Everyone!!
I got this error in a strange situation yesterday. Here is what happened:
We were moving a group of new reports from Development repo to Test Repo. They were exported sucessfully into the repo and in to the ‘Testing’ group of users. The export took place about noon. Our testers had all been in BusinessObjects since early that morning. They then got the notification that the export was complete. They imported the new reports from the repository and then tried to open them. That is when they got the error. They emailed me about it and this morning I went in with their id’s and opened the reports with no problem. I called them and they tried again and
they got in with no problem. There were no changes made in Supervisor as I
am the only one that can do that.
My question is: Would the testers have to logout and log back in to BO before they could get to these reports? That is the only thing that I could
think of, but it doesn’t seem as if that should be necessary. My thought was:
Testers logged into BO yesterday morning and at that time, BO
checked to see what documents they had access to in the repository, let’s say reports A, B and C.
Meantime, New reports are sent to the repository with their group
having access, let’s say reports X, Y and Z. * They import the reports X, Y and Z as BO can tell they have been
added to the repository, however, it is still under the impression that A, B
and C are the only reports they have access to, thus the you are not authorized error.
That is the only thing that I could think of but I thought that the report access was a little more dynamic than that. Does anyone have any thoughts on this??
It sounds like you’ve figured it out 100%! Yes, the users have to log back in to gain access to new reports.
Cheers,
Luis
From: Carter, Maria [SMTP:mcarter@HRSERV2.IMS.ATT.COM]
Hi Everyone!!
I got this error in a strange situation yesterday. Here is what
happened:
We were moving a group of new reports from Development repo to Test
Repo.
They were exported sucessfully into the repo and in to the ‘Testing’
group
of users. The export took place about noon. Our testers had all been
in
BusinessObjects since early that morning. They then got the
notification
that the export was complete. They imported the new reports from the repository and then tried to open them. That is when they got the
error.
They emailed me about it and this morning I went in with their id’s and opened the reports with no problem. I called them and they tried again and
they got in with no problem. There were no changes made in Supervisor
as
I
am the only one that can do that.
My question is: Would the testers have to logout and log back in to BO before they could get to these reports? That is the only thing that I could
think of, but it doesn’t seem as if that should be necessary. My
thought
was:
Testers logged into BO yesterday morning and at that time, BO
checked to see what documents they had access to in the repository,
let’s
say reports A, B and C.
Meantime, New reports are sent to the repository with their
group
having access, let’s say reports X, Y and Z. * They import the reports X, Y and Z as BO can tell they have been
added to the repository, however, it is still under the impression that
A,
B
and C are the only reports they have access to, thus the you are not authorized error.
That is the only thing that I could think of but I thought that the
report
access was a little more dynamic than that. Does anyone have any
thoughts
on this??
In a message dated 98-10-01 11:32:28 EDT, you write:
Testers logged into BO yesterday morning and at that time, BO
checked to see what documents they had access to in the repository, let’s say reports A, B and C.
Meantime, New reports are sent to the repository with their group
having access, let’s say reports X, Y and Z. * They import the reports X, Y and Z as BO can tell they have been
added to the repository, however, it is still under the impression that A,
B
and C are the only reports they have access to, thus the you are not authorized error.
That is the only thing that I could think of but I thought that the report access was a little more dynamic than that. Does anyone have any thoughts on this??
Maria:
The report access really isn’t. In the OBJECTS.USE file is contained all of the information that pertains to a user’s permissions, and it is updated once they log on to the system. There is an option that I have never experimented with in Supervisor: Enable Real Time User Rights Update… you might try that and see if you can duplicate your problem. I have never worked with it myself, but it sounds good!
In a message dated 98-10-01 17:36:20 EDT, you write:
In the OBJECTS.USE file is contained all of
the information that pertains to a user’s permissions, and it is updated once
they log on to the system.
ARRRGH! Momentary brain derailment…
OBJECTS.USE is used in BusObj version 3.1. In the current versions (4.x) it is, of course, Objects.lsi. Or objects.ssi (I think) if you have it shared.
Maria,
Would like to know if you have “Enable Real-time User Rights Update” enabled under User properties in Supervisor…?? I haven’t yet figured out what this does, if anything, but perhaps this would resolve the users having to log out and back in again. As you said, it should work a bit more "dynamically’ than it has in your experience. Neal
