Symantec Management Platform (Notification Server)

 View Only
  • 1.  Failed to process NSE - There is an unclosed literal string

    Posted Dec 20, 2013 11:20 AM

    We're currently battling an issue with our NSE's not processing.  I'm looking at the log viewer and there are several entries saying:

         "Failed to process NSE

         Exception Details: System.Xml.XmlException: There is an unclosed literal string.  Line 323, position 29."

    I can't seem to find any documentation for this error.  What can I do to stop these?



  • 2.  RE: Failed to process NSE - There is an unclosed literal string
    Best Answer

    Posted Dec 20, 2013 01:10 PM

    By default, bad events are now discarded but you can keep them for examination:

    "EventFailureBackupFolder

     If you don’t see this setting in the registry, it means it’s not effective or not used. However, you can define it manually by adding an EventFailureBackupFolder string value under the key HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Notification Server. As soon as you add it, the setting will be active. If any of the NSEs fail to process (with retries), the file will be put into that folder. The appropriate subfolder will also be created, depending on the type of exception."

    "Event Queues in ITMS 7.1 SP2"

    http://www.symantec.com/docs/DOC5480

     



  • 3.  RE: Failed to process NSE - There is an unclosed literal string

    Trusted Advisor
    Posted Dec 30, 2013 03:57 PM

    Andy,

    The documentation feels incomplete on that.  I found this murky explanation:

    Question:
    Please describe how to use the feature Event Failure Backup folder.  I see the setting in coresettings.config which seems to reference a registry setting.  Do I create a registry string value with the value of where I want the backup folder to be?  Exactly how is this implemented.
    Answer:
    Yes, the code query for core setting, which tells that this setting is in registry. If there is something (non-empty string), than it goes like this:
    1.1  if the value is “rooted path”, i.e. with driver letter – it is being used “as is” (+ the subfolder for exception, which map we have in “BadNSEFolders.config“)
    1.2  if the path is relative, then we create such folder under the “EventQueue” folder
    1.3  The code write the NSE itself into this place, along with extra file with same name and “.log” extension, if it was an exception which lead to event backup – the log file body will be an exception message itself.

    So, my string value would be something like "C:\badNSE"?

     



  • 4.  RE: Failed to process NSE - There is an unclosed literal string

    Trusted Advisor
    Posted Dec 31, 2013 12:47 PM

    I just confirmed this for myself.  In my example, though, you need to actually create C:\badNSE as it won't be created automatically.



  • 5.  RE: Failed to process NSE - There is an unclosed literal string

    Posted Jan 07, 2014 11:02 PM

    Can you please share the Release of SMP installed.
    This issue should be resolved after upgrading to Latest release i.e. 7.1 SP2 Mp1 Rollup V7
    If still you have issues please let me know