916 views

Description

Due to a dictionary entry change related to support being added for attachments on MID Server Script Files, a multiple update database execution is performed when an attachment is deleted to null out references. Even though no actual change is made, this triggers the database listener MidScriptListener to incorrectly notify all MID Servers of a potential change.

Steps to Reproduce

 

  1. Initiate a grab log files from an existing MID Server record.

  2. Upon an input response with an attachment, remove the attachment.

    Note that an ecc_queue record is created per MID Server with the following:
    Topic: SystemCommand, Source: FileChange, Name: ecc_agent_script_file, Queue: output

Workaround

Update the following dictionary entry and set Reference cascade rule = None, not the default -- None --. This is also part of the official patch, and should not be reverted.

  1. Navigate to /sys_dictionary_list.do.

  2. Find the Dictionary Entry for Table = ecc_agent_script_file, Column name = script_attachment.

  3. Under Related Links, click Advanced View.

  4. Under Reference Specification - Additional Customization look for Reference cascade rule and select None from the drop-down, not the default -- None --.

    See the screenshot below:



  5. Clear the MID Server ECC queue if required, to avoid unprocessed messages to be sent.
     
    Manage ECC Queue content for a MID Server
    ECC queue

  6. Restart the MID Server node.

 

 


Related Problem: PRB1204637

Seen In

Kingston

Intended Fix Version

London

Fixed In

Jakarta Patch 7
Jakarta Patch 8
Kingston Patch 1
Kingston Patch 2

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-02-13 21:58:36
Published:2018-02-14