The attribute you are trying to update already has this value.
I do not know why RT insists on treating this as an exception,
but since it does so,
so should the client.
You can probably safely catch and throw away this exception in your code.