We have the exact same problem. It occurs when users want to set their OoO, delegate the mailfile or update the persondocument 

I've opened a PMR with IBM. We use Oracle Enterprise Linux and IBM told me that they don't support this for IBM Notes 9. We tested on Red Hat Linux, but the problem remains.

I'll keep you informed when we find a solution

Any update on the PMR?

We are also getting the same error - but not for all users

"Update Roaming User State in Person Record" - currently only for one OU

"Update Client Information in Person Record" - for a couple of users in different OU's

All servers (Domino 9.0) and clients (Notes 9.0) are Windows (no Linux).

Except the registration server is still on Domino 8.5.3 - no users on this server are getting this error.

Let me know if there is anything you'd like me to check with your setups.

IBM is still working on the PMR and researching the problem, so for now we don't have a solution yet. As soon as we do, I'll post it here

I noticed we were getting errors on the Domino Server Console about users not having accessing to admin4.nsf (i.e. ATTEMPT TO ACCESS DATABASE admin4.nsf by USERNAME) .  Upon reviewing the ACL in admin4.nsf (which hasn't been changes for over 3 years), users had No Access.  After giving users Depositor access all requests are now being successfully processed.

You seem to have found the solution! Our default access was set to "Reader" and it has been like that for several years. I changed it to "Depositor", did some tests and now I don't get any errors. 

Reprocessing old requests with errors still gives the same error, but new requests seem to work fine.

Thanks! I'll inform IBM about this as well :-)

Depostior rights seems to fix a lot of our problems too but i also found that our admin4.nsf is still using version 8.5.3 template and there is no version 9 template.