We have AS2000 SP4 and have enabled writeback on our accounts cube for
budgeting and forecasting reasons. The cube is partitioned by year. The users
who are entitled to writeback have their own Db role with custom cell
security (they can writeback to 3 measures only, no other restrictions). The
accountant’s writeback via spreadsheets and Proclarity.

Our problem arises intermittently. Every now and then one or more users
cannot writeback for security reasons (-2147168234), even though the security
has not been touched and they have permissions.

This can be usually cured in one of four ways –
Remove and re-add the user/s in question.
Add a new user.
Remove and reapply the role to the cube.
Fully reprocess the cube.

None of the above solution works every time, and there are no tell tail
signs as to which one will work at any given time.

My questions are what’s happening? Why? And how do I fix it?

Any help is much appreciated.

We are experimenting with writeback as well.

Havent' had that kind of trouble yet (but we are still testing) but could
you put the measure allowance into the front end ? so this checks what you
may update in order
to skip custom cell security.


"HWUK" <HWUK (AT) discussions (DOT) microsoft.com> wrote

Hi,

any news on this yet?

I have the same issue with writeback:
- SQL A.S. 2000 SP4
- Proclarity Professional v6

Sometimes users can't use modelling in proclarity. We solve this in Analysis
Services by "Manage roles" -> For the role of the user that has issue, cell
security, custom security for read/write and then change the description.
When applying, the user can model again.

But I get tired of doing this! Any good workaround is welcome...

BR,
Bert

"michael v" schreef: