How to fix errors caused by inconsistent schema

Anonymous · ‎02-13-2020

I am kind of new to Azure Stream Analytics and all related services like power bi, but recently I've been trying to work on an IoT project. I had a number of sensors already pre-configured in addition, my IoT Hub setup as well. So what I'm trying to do is ingest sensor data via my IoT hub and push it to power bi for live streaming and visualization. However, whenever I start my ASA job, with two sensors connected (DHT11 & Water Sensor all via an ESP8266) that are sending data to the IoT hub in JSON format. The job fails after a while and gives this error

properties": {
        "Message Time": "2020-02-14 07:09:13Z",
        "Error": null,
        "Message": "First Occurred: 02/14/2020 07:09:13 | Resource Name: outputpowerbi | Message: Received a batch with inconsistent schemas. Please ensure that the schemas of output events are consistent and then restart the job. See 'https://aka.ms/asa-powerbi-schema-update' for more details on how to safely change the table's schema.",
        "Type": "DiagnosticMessage",
        "Correlation ID": "9317b7ab-dce3-4ea5-bc2f-6440fb53d0f0"
    },

I used Azure IoT explorer to extract/view the telemetry data being sent and here is how they both look like

Temperature & Humidity Sensor

{
  "body": {
    "deviceId": "temperatureSensor",
    "Temperature": 17.2,
    "Humidity": 164.8
  },
  "enqueuedTime": "2020-02-14T07:10:43.076Z",
  "properties": {},
  "systemProperties": {
    "iothub-connection-device-id": "temperatureSensor",
    "iothub-connection-auth-method": "{\"scope\":\"device\",\"type\":\"sas\",\"issuer\":\"iothub\",\"acceptingIpFilterRule\":null}",
    "iothub-connection-auth-generation-id": "637166446115566557",
    "iothub-enqueuedtime": 1581664243080,
    "iothub-message-source": "Telemetry",
    "x-opt-sequence-number": 26124,
    "x-opt-offset": "11293464",
    "x-opt-enqueued-time": 1581664243076
  }
}

Water Sensor

{
  "body": {
    "deviceId": "waterSensor",
    "Status": 0   
  },
  "enqueuedTime": "2020-02-14T04:39:13.205Z",
  "properties": {},
  "systemProperties": {
    "iothub-connection-device-id": "waterSensor",
    "iothub-connection-auth-method": "{\"scope\":\"device\",\"type\":\"sas\",\"issuer\":\"iothub\",\"acceptingIpFilterRule\":null}",
    "iothub-connection-auth-generation-id": "637166446422348866",
    "iothub-enqueuedtime": 1581655153204,
    "iothub-message-source": "Telemetry",
    "x-opt-sequence-number": 25163,
    "x-opt-offset": "10877712",
    "x-opt-enqueued-time": 1581655153205
  }
}

The line "Status:" 0 is just to show that there is no water/leakage detected. The overall idea is being able to connect multiple sensors via IoT hub and being able to see all sensor data being visualized on power bi without any conflict or issues.

Can anyone help Cause I tried the reading what is on the link provided in the error but to no avail.

Thanks in advance.

simoncfc01 · ‎11-19-2021

im having a similar issue with a multisensor and after a couple of minutes or an hour or straight away the job fails giving this error

Send Events: Failed to send data to Power BI due to incompatible sc...

ive recreatd the streaming job and the sensor is still inoutting data into Azure but even during the few times this stays up i get no significant data whatsoever. and this has been posted a year ago and no PowerBi gurus have responded to the original request and mine