RDK and repository items (OpenInsight Specific)
At 09 MAR 1998 05:28:45PM Tyler Crosbie Vernon Systems wrote:
Right I'm still battling with the RDK. When I've generated, deployed and applied the upgrade to my existing clients runtime site, and then create a new user with USER rights, I get this message 'REP119 user USER does not have rights to perform operation 1 against entity COLLECT*OIWINEXE**win_name' when I try to log into my system. Now this is not right, a user should be able to start up a window. Access rights are $public, the entity is publishable and shareable. One thing I have noticed is that when I look at this particular repository item, (and about 104 others out of 27000+), in Arev3, the repository entry is not compiled down to machine code, (or whatever you choose to call it), it is infact very readable, however their are only 104 items like this, the other 27000 ALL have compiled code in their repository items, so I'm guessing this is the problem. However if I checkout or copy this entity to another location, delete the existing one and then either check it back in or copy it back in, the item is stil
l has the same problem, so my question is how can I get this repository item created correctly, (with the compiled code), without having to recreate the entire window, oh yeah one other thing I did try copying the window to another name, deleting the old window totally, logging out of the system logging back in and copying the temp window to the old window name, and although when the temp window was created it had the correct repository item format, as soon as I copied it back to the old window name, which no longer existed in the repository, it was exactly the same. What is going on here?
At 12 MAR 1998 11:26AM Aaron Kaplan wrote:
So, you've gone into ARev, create a pointer into the SYSREPOS file and looked at the data. Instead of seing the record as encrypted, you're seeing it in 'clear text'. Correct?
If so, Don't know how this happened, but from ARev, copy the records to a temp file. Then, from OI, copy the recs from the temp to SYSREPOS. They should encrypt themselves.
I'll bet what's happening is that REPOS_BFS is decrypting the non-encrypted records, so it's reporting that the user has no rights to the file.
