Post

DestinationType is a duplicate attribute name while editing Nintex Workflow
We encountered an issue where some Nintex Workflow actions weren’t editable anymore. The error was saying “Sorry, something went wrong” while opening for example the “Create item” action and the ULS was saying “DestinationType is a duplicate attribute name”. The following full message was fount in the ULS logs System.Xml.XmlException: ‘DestinationType’ is a duplicate attribute […]

We encountered an issue where some Nintex Workflow actions weren’t editable anymore. The error was saying “Sorry, something went wrong” while opening for example the “Create item” action and the ULS was saying “DestinationType is a duplicate attribute name”.

The following full message was fount in the ULS logs

System.Xml.XmlException: ‘DestinationType’ is a duplicate attribute name. Line 1, position 163.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.AttributeDuplCheck()
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r)
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at Nintex.Workflow.Activities.Adapters.WssActions.WssActionsFile.GetCoercionsXmlStringForJavaScript()
at Nintex.Workflow.ApplicationPages.Activities.ContextDataLookup.BuildClientScript()
at Nintex.Workflow.ApplicationPages.Activities.ContextDataLookup.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

We tried the following things to resolve this issue (with no effect):

  1. IISReset
  2. Restarting the SharePoint Timer Service
  3. Clearing the cache folder
  4. Restart the SharePoint Timer Service

We were only able to edit the action again after restarting all SharePoint servers in the farm.

 

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Archive