000016500 - RSA Archer 4.x - Notification from a particular content record is failing to parse and skips intended delivery schedule.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016500
IssueRSA Archer 4.x - Notification from a particular content record is failing to parse and skips intended delivery schedule.
Notification delivery format is set to HTML.
Notification from the same RSA Archer application are being send out without an issues.
Archer.Notification log will show following parsing error:

<logRecord>
  <time>2014-05-15 22:49:36.031</time>
  <logLevel>Error</logLevel>
  <sessionToken>5407289CAEE837C9E0235004E0C5F334</sessionToken>
  <assemblyName>Archer.Engine</assemblyName>
  <message>Error processing notification - &apos;<Notification Name>&apos; is an unexpected token. Expecting white space. Line 84, position 16298.; Notification= &lt;content id=&quot;#######&quot;
.
.
.
<Notification Content Record Details in XML and HTML tags>
.
.
.
/&gt;&lt;/content&gt;</message>
  <stackTrace> 
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   at System.Xml.XmlTextReaderImpl.ParseAttributes()
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at Archer.Engine.Notification.Notification..ctor(DataCache dataCache, Int32 notificationId, NotificationTemplate notificationTemplate, String xml)
   at Archer.Engine.Notification.DataCache.GetNotifications(Recipient recipient, NotificationTemplate notificationTemplate)</stackTrace>
</logRecord>
CauseOne of the notification content fields (Cross Reference / Related Record) had a record with a pair Double Quotes in the text, hence throwing off the Notification XML syntax upon parsing.
ResolutionWorkaround: To fix this issue, please remove the pair of Double Quotes from the Cross Reference / Related Record and save the changes. And Try out the notification.
Legacy Article IDa65744

Attachments

    Outcomes