topic Strange 05010107 Failed to write property deltas error while updating document in Alfresco Archive

Strange 05010107 Failed to write property deltas error while updating document

pradeepsimha — Sun, 01 Jun 2014 06:36:17 GMT

Hi Team,I am trying to update the already existing document properties using below coderoperties.put("tirettyUrl", apiListDoc.getPretyUrl());properties.put("ti:apiAuthHeaders", apiListDoc.getApiHeaders());String docText = apiListDoc.getPretyUrl();byte[] content = docText.getBytes();InputStream s

Re: Strange 05010107 Failed to write property deltas error while updating document

jpotts — Fri, 13 Oct 2017 18:44:58 GMT

I know this is an old post, but no one has responded and I just came across the same problem, so I thought I'd post what fixed it for us.

In our case, we were using the CMIS connector in Chronoscan to create documents in Alfresco and set custom aspects and properties on those aspects.

For some reason, all of our aspects were working fine except one. If a document had that aspect, any change to the document properties would fail with a "Failed to write property deltas" error. This error would occur both in the Share user interface and via the Chemistry OpenCMIS Workbench.

The fix was to shut down the server, clear out the solr4/model directory, and restart.

That's the second time this week clearing out the Solr model directory has fixed a problem for one of my clients (two different clients, two very different problems, same solution).

This is Alfresco Enterprise 5.1.3.

Re: Strange 05010107 Failed to write property deltas error while updating document

jpotts — Tue, 17 Oct 2017 19:17:36 GMT

Just another update...it turns out in one of these cases that the customer was using a third-party scanning software package that leverages CMIS to write to the repository. The configuration was specifying the properties to write metadata to and the configuration was not using the same case as is specified in the content model XML. So, for example, the config was using scomeProp when it should have been using sc:someProp. This caused a transient property to be created called "scomeProp" when the scanner ran, and that was enough to cause the error. The restart cleared the problem. The solution was to correct the scanner config.