Receiving this ERROR: Sensor is expecting JSON format (sys_script_include.778011130a0a0b2500c4595ad1d1d768.script; line 28)

[B Wetzstein]

We are running Discovery on our Dev environment, about 1700 devices. On WMI: Installed Software we get this error on 268 CIs

Sensor is expecting JSON format in the output field after probe post processor script.  Please check that your MID server is up to date. (sys_script_include.778011130a0a0b2500c4595ad1d1d768.script; line 28)

in the script:

<?xml version="1.0" encoding="UTF-8"?><results error="JSON.parse (script_include:JSON; line 42)" probe_time="11227" result_code="0"><result>

[tim_broberg]

So, the post processor script is in the probe. This is a script that runs on the mid server to pare away any useless fluff from the results and report the relevant bits in a more compact json format.

The alternative, which post processing is disabled, is that the raw output of the command run in the probe gets dumped into the output field of the payload.

You probably want to look at the ecc_queue input associated with this discovery log message and squint at the <output> field of the payload.

Does it look like json? Is there an <error> tag in the result?

You may be able to compare it to the ecc_queue input from other similar probes to get a feel for what they should look like.
    - Tim.

[B Wetzstein]

We ended up having to open a HI ticket. There was a known problem.. 

• Windows terminal width can handle 9999 characters.
• When we receive payload more than that, the data is pushed to a new line.
• This breaks the JSON and causes issues.

We had to install a xml fix to our instance, which has now fixed this issue.. 🙂

Thank you,

Brian

[tim_broberg]

Thanks for the update, Brian.

I'm sure somebody else will step in the same puddle some day and appreciate the solution.

[venkat ajay]

can you explain me how did you resolve that issue we are facing same issue?

Thanks,

Ajay