Hi Angus,

Perhaps this thread from StackOverflow can help you to solve the error.

http://stackoverflow.com/questions/19131915/umbraco-content-syncing-issue-error-refreshing-a-node-in-the-distributed-list

Hope this heps,

/Dennis

Hi Angus

If the solution Dennis mentions above does not work for you would you then mind sharing your code so the c# wizards can have a look and figure out if there is something that needs to be changed in order to get rid of the error perhaps?

/Jan

Thanks for the prompt reply.

Newly created documents are being *successfully* published to BOTH the master and slave so this doesn't appear to be an authentication issue.

Calling the following method successfully creates and publishes the content but it generates the log file error:

public bool AddWhatsNew(string nodeName, int parentId, string headline, string summary, string urlpickerMode, string targetURL, int targetNodeId, string publicationDate)

{

try

{

// get the content service

var contentService = ApplicationContext.Current.Services.ContentService;

// create 'What's New' doc

IContent newdoc = contentService.CreateContent(nodeName, parentId, "whatsnew");

// set values : headline, summary, target, publicationdate

newdoc.SetValue("headline", headline);

newdoc.SetValue("summary", summary);

// set 'target' property, a urlpicker

Property p = newdoc.Properties["target"];

// create new urlpicker state

UrlPickerState pState = new UrlPickerState();

// set values : assume urlpicker mode 'URL' or 'Content'

pState.Title = nodeName;

if (urlpickerMode.Equals("URL")) {

pState.Mode = UrlPickerMode.URL;

pState.Url = targetURL;

} else {

pState.Mode = UrlPickerMode.Content;

pState.Url = targetURL;

pState.NodeId = targetNodeId;

}

// set the 'target' parameter value to the serialisation of the urlpicker state

p.Value = pState.Serialize(UrlPickerDataFormat.Xml);

//newdoc.SetValue("publicationdate", publicationDate);    // doesn't work in 6.2.1! 

string[] dateEelements = publicationDate.Split('-');

int year = Int32.Parse(dateEelements[0]);

int month = Int32.Parse(dateEelements[1]);

int day = Int32.Parse(dateEelements[2]);

newdoc.SetValue("publicationdate", new DateTime(year, month, day));

// save and publish the document

contentService.SaveAndPublishWithStatus(newdoc);

return true;

}

catch (Exception cdex)

{

LogHelper.Info(this.GetType(), "\nAddWhatsNew : " + cdex.Message + " : " + cdex.StackTrace);

return false;

}

}

 

Exmaple Call:

AddWhatsNew("Planning Service - Development Plan Consultations", 4009, "Planning Service - Development Plan Consultations", "Update to Review of Supplementary Guidance for Wind Energy Development...", "URL", "http://intranet/planningservice/devplanconsultations.asp", -1, "2014-12-03");

Angus - did you resolve this? I have the same issue in 6.2.1 and wondering if this is related:

http://our.umbraco.org/forum/getting-started/installing-umbraco/55867-Setting-up-distributedcall-for-Umbraco-load-balancing-with-Umbraco-7?p=1#comment193598

Hi Simon,

Errors still appearing in the log file! Other than the mild irritation caused by the presence of the errors, as our setup is in development and functionality is not compromised - the newly created documents being published to both the local and the distributed server, i.e., both caches are being successfully updated - I'm basically ignoring the errors for now.

/Angus

is working on a reply...