Autodesk Green Building Studio - Web-Based Service
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Failed Run DOE 2.2 Error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I am getting the following error
Issue: An error has occurred related to the DOE-2 simulation. It is below and may be of assistance in determining the issue with your building model. If it is unclear what the issue is, please submit the issue at the link below and include the gbXML file used for this run. <br/> *16482* Y = -3563.6142339895<br/>*ERROR***********************
How do I find the elements this is refering to? I thought hte numbers would be the Revit ID but does not appear to be the case. Checked the file thourghly and found no errors that I know of. Any Ideas?
Re: Failed Run DOE 2.2 Error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
You can open up your input gbxml file and look for the relevant unique text or number. Ex, you can look for '4380' in the gbxml file. There is a free tool called xmlnotepad. It works great with gbxml file for trouble shooting issue like this.
Re: Failed Run DOE 2.2 Error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I tried that in notepad, built a DB in Excel and Access. Just tried the xml notepad. None of them found any of the values listed in the error statement. I suspect these are being misread by the DOE application, but I do not know why.
How does one get support for GBS from ADESK beside asking questions on the discussion boards?
Re: Failed Run DOE 2.2 Error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
You can send email to support.gbs@autodesk.com with your input model file. We can further investigate this issue.

