Hello All
We have a “Power” user group in 6.1.B and for this group we have enabled for InfoView witrhin Supervisor to “Send documents to users in own groups” and “Send documents to users in other groups”. When this user tires to send a report, he is able to pick / select users to whom he wants to distribute the report, however, when he finally clicks OK, he gets the following error:
A system error occurred. (Error: INF 00130) (10405)
I had the same problem. We wound up having to enable ‘View All Users’ in the BusinessObjects Miscellaneous permissions. I then had to allow people to send only to users in their own group for our own personal reasons.
We basically toggled permissions till we stumbled on that but there are other settings that may impact this as well.
Cindy
Thanks for the post. I tried what you suggested and it still does not work. If I make it work, I will definitely post the results. The peculiar thing is that it works for user’s who are general supervisors.
I just sent you a pdf via email that lists the permissions for our group that can successfully send documents to one another. You can use the report if you implement the stuff in the Bob Downloads area…at least I thought it was in there but I can’t seem to find it right now.
With 6.1.b I got this error message (Error: INF 00130) and chased it down to a problem with a timeout during authentication process. For me this problem was manifest in the Oracle 9.2.0.2 middleware. Tech Support said that 9.2.0.2 was not on the PAR and the problem would be rectified with an upgrade to 9.2.0.4. Once I made this upgrade to the server middleware we had almost eliminated all of these problems. Your symtoms seem to be consistent with this problem after all sending docs to users requires users security information access.
Here’s another work around that I came upon just by chance. If you log into the administration tool on the server you may want to change the WILOGIN SERVER refresh cycle from 10 minutes (600secs) to 1 minute (60 secs). This worked pretty well until I got the middleware upgraded.
Another action that I took that help mitigate the problem until we got more information on the server was to go to the task manager on the server and kill the WILOGINSERVER.EXE process. This process automatically restarts after being terminated and the problem went away for a while. It continued to return until I upgrade the middleware.
My suggestion would be to try reseting the login information refresh cycle first. If this seems to correct the problem you could be dealing with the exact same problem. Upgrade the middleware and your problem should go away.