Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

severe error "Failed to match against any enum values"

I'm using the Honeybee interface to run EnergyPlus simulation for a simple model.

I got the following severe error:

Program Version,EnergyPlus, Version 8.9.0-eba93e8e1b, YMD=2018.08.12 11:34,
* Severe * <root>[Output:Variable][Output:Variable 76][reporting_frequency] - "Simple" - Failed to match against any enum values.

I checked the IDF file, and the format of the two output variables as highlighted below seems OK:

Output:Variable,*,Surface Outside Face Incident Ground Diffuse Solar Radiation Rate per Area,hourly;

Output:Diagnostics,DisplayExtraWarnings;

Output:SQLite, Simple;

Output:Variable,My_PV_generator_system:DISTRIBUTIONSYSTEM,Electric Load Center Produced Electric Energy, Simple;

Once these two output variables on diagnostics and SQLite as highlighted above are removed in the Honeybee workflow, the simulation runs correctly.

However, without removing these two output variables: 1. the same Honeybee workflow works fine in another computer with the same software installation, and 2. the same IDF file also works fine independently through the EPLaunch.exe.

May I ask if you can kindly advise what could have caused the severe error in this case?

severe error "Failed to match against any enum values"

I'm using the Honeybee interface to run EnergyPlus simulation for a simple model.

I got the following severe error:

Program Version,EnergyPlus, Version 8.9.0-eba93e8e1b, YMD=2018.08.12 11:34,
* Severe * <root>[Output:Variable][Output:Variable 76][reporting_frequency] - "Simple" - Failed to match against any enum values.

I checked the IDF file, and the format of the two output variables as highlighted below seems OK:

Output:Variable,*,Surface Outside Face Incident Ground Diffuse Solar Radiation Rate per Area,hourly;

Output:Diagnostics,DisplayExtraWarnings;

Output:SQLite, Simple;

Output:Variable,My_PV_generator_system:DISTRIBUTIONSYSTEM,Electric Load Center Produced Electric Energy, Simple;

Once these two output variables on diagnostics and SQLite as highlighted above are removed in the Honeybee workflow, the simulation runs correctly.

However, without removing these two output variables: 1. the same Honeybee workflow works fine in another computer with the same software installation, and 2. the same IDF file also works fine independently through the EPLaunch.exe.

Another strange issue is that, as shown above, the EnergyPlus version is indicated as 8.9.0. However, I'm using EnergPlus 8.8.0 only currently....

May I ask if you can kindly advise what could have caused the severe error in this case? case?

severe error "Failed to match against any enum values"

I'm using the Honeybee interface to run EnergyPlus simulation for a simple model.

I got the following severe error:

Program Version,EnergyPlus, Version 8.9.0-eba93e8e1b, YMD=2018.08.12 11:34,
* Severe * <root>[Output:Variable][Output:Variable 76][reporting_frequency] - "Simple" - Failed to match against any enum values.

I checked the IDF file, and the format of the two output variables as highlighted below seems OK:

Output:Variable,*,Surface Outside Face Incident Ground Diffuse Solar Radiation Rate per Area,hourly;

Output:Diagnostics,DisplayExtraWarnings;

Output:SQLite, Simple;

Output:Variable,My_PV_generator_system:DISTRIBUTIONSYSTEM,Electric Load Center Produced Electric Energy, Simple;

Once these two output variables on diagnostics and SQLite as highlighted above are removed in the Honeybee workflow, the simulation runs correctly.

However, without removing these two output variables: 1. the same Honeybee workflow works fine in another computer with the same software installation, and 2. the same IDF file also works fine independently through the EPLaunch.exe.

Another strange issue is that, as shown above, the EnergyPlus version is indicated as 8.9.0. However, I'm using EnergPlus 8.8.0 only currently....

May I ask if you can kindly advise what could have caused the severe error in this case?