It's not doing this locally on dev machine, only on production server with
any save to an existing 'Account' document.

I would do a backup/restore to my local machine to test, but it takes over
24 hours.

From: ravendb@googlegroups.com [mailto:ravendb@googlegroups.com] On Behalf
Of Oren Eini (Ayende Rahien)
Sent: 09 June 2012 11:27
To: ravendb@googlegroups.com
Subject: Re: [RavenDB] OperationVetoedException - when updating an existing
document

Any way to repro?

I have updated to build 960 again and I'm running from the debug console,
still getting the same problem.

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 09 June 2012 00:55
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: RE: [RavenDB] OperationVetoedException - when updating an existing
document

I can reproduce this from the Silverlight management studio too, load up the
document, modify and save it.get the same error.

I have downgraded the server to build 951 just to check if it fixes it, but
it doesn't which is strange.

I'm not 100% sure it was build 951 I was using previously to be quite
honest, but it was around the 24th May i downloaded the latest build I was
using.

This is affecting a large proportion of my site currently when saving any
document related to a user account.

Paul

From: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
[mailto:ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');> ] On Behalf
Of Paul Hinett
Sent: 08 June 2012 23:41
To: ravendb@googlegroups.com
<javascript:_e(%7b%7d,%20'cvml',%20'ravendb@googlegroups.com');>
Subject: [RavenDB] OperationVetoedException - when updating an existing
document

Hi,

Just upgraded to build 960 stable from 951, both client, server and bundles.

On a simple procedure of loading an existing document by id, updating 1
property (a DateTimeOffset property) I am getting an exception from the
UniqueConstraint bundle.

I can't seem to reproduce this locally on my dev machine but only on my
production server.

var account = _documentSession.Load<Account>(command.AccountId);

account.LastNotificationReadDate = DateTimeOffset.Now;

Raven.Database.Exceptions.OperationVetoedException: PUT vetoed by
Raven.Bundles.UniqueConstraints.UniqueConstraintsPutTrigger because: Ensure
unique constraint violated for fields: ArtistName, EMail

Has anything changed that could cause this, it was working fine before the
upgrade to latest stable.

Paul