Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Also are you using any apostrophe's in zone names? May be related to this issue
If you upgrade to OpenStudio 1.10.0 or later it will trap this error and you will see the rest of the report except for the Zone Conditions section. Or if you rename your thermal zones then you can re-run and the error should go away.
| | 2 | No.2 Revision |
Also are you using any apostrophe's in zone names? May be related to this issue
If you upgrade to OpenStudio 1.10.0 or later it will trap this error and you will see the rest of the report except for the Zone Conditions section. Or if you rename your thermal zones then you can re-run and the error should go away.
The issue is caused by sql query's with some non- alphanumeric characters. Here is a similar post but with design day name instead of thermal zone name.
| | 3 | No.3 Revision |
Also are you using any apostrophe's in zone names? May be related to this issue.
If you upgrade to OpenStudio 1.10.0 or later it will trap this error and you will see the rest of the report except for the Zone Conditions section. Or if you rename your thermal zones then you can re-run and the error should go away.
The issue is caused by sql query's with some non- alphanumeric characters. Here is a similar post but with design day name instead of thermal zone name.
| | 4 | No.4 Revision |
Also are Are you using any apostrophe's in zone names? May be related to this issue.
If you upgrade to OpenStudio 1.10.0 or later it will trap this error and you will see the rest of the report except for the Zone Conditions section. Or if you rename your thermal zones then you can re-run and the error should go away.
The issue is caused by sql query's with some non- alphanumeric characters. Here is a similar post but with design day name instead of thermal zone name.
