# Stream xml get attribute failed

**URL:** <https://forums.jcsda.org/t/stream-xml-get-attribute-failed/342>\
**Category:** JEDI\
**Created:** [July 6, 2022, 1:10pm UTC](https://forums.jcsda.org/t/stream-xml-get-attribute-failed/342 "2022-07-06T13:10:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![byoung-joo](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.jcsda.org/byoung-joo/32/126_2.png) [@byoung-joo](https://forums.jcsda.org/u/byoung-joo)\
**Post date:** [July 7, 2022, 4:51pm UTC](https://forums.jcsda.org/t/stream-xml-get-attribute-failed/342/4 "2022-07-07T16:51:16Z")

</div>

I’m glad that it fixed your issue.

I don’t know what cause the HDF related error. But we have recently encountered the same error message `HDF5-DIAG: Error detected in HDF5 (1.12.0) MPI-process 0:` when the observation file was unintentionally removed. So, can you please double check if the path for the observation file ( under `obs space`.`obsdatain`.`obsfilein` key) is correct in your yaml file ? This might not be a reason for the error because the error message also said `Exception: Reason: An exception occurred inside ioda while opening a variable. `

The other thing is… JEDI-MPAS 1.0.0 requires IODA Version 2 format for the observation files. So I wonder which version of [obs2ioda.x](https://forums.jcsda.org/t/observation-data-for-simulating-observations/232) is used to generate your obs files: `obs2ioda-v1` or `obs2ioda-v2`. Also please check if there is an executable `bin/ioda-upgrade.x` under your build directory. This executable converts the IODA V1 format into V2 format.

---

_[View the full topic](https://forums.jcsda.org/t/stream-xml-get-attribute-failed/342)._