{"id":29,"date":"2007-06-28T09:04:25","date_gmt":"2007-06-28T14:04:25","guid":{"rendered":"http:\/\/www.lonhosford.com\/lonblog\/2007\/06\/28\/flex-builder-an-internal-build-error-has-occurred-please-check-the-error-log\/"},"modified":"2014-03-16T12:55:33","modified_gmt":"2014-03-16T17:55:33","slug":"flex-builder-an-internal-build-error-has-occurred-please-check-the-error-log","status":"publish","type":"post","link":"https:\/\/www.lonhosford.com\/lonblog\/2007\/06\/28\/flex-builder-an-internal-build-error-has-occurred-please-check-the-error-log\/","title":{"rendered":"Flex Builder 2.01 an Internal Build Error has Occurred Please Check the Error Log"},"content":{"rendered":"<p>I am using Flex Builder 2.01.<\/p>\n<p>I was attempting to follow the <a href=\"http:\/\/blogs.adobe.com\/flexdoc\/pdfs\/modular.pdf\" target=\"_blank\">updated ModuleLoader documentation<\/a>  at Adobe blogs.<\/p>\n<p style=\"margin-left: 20px\">The directions included:To edit the list of runnable application files:<br \/>\n1. Right-click the project file and select properties.<br \/>\n2. Select the Flex Applications option.<br \/>\nThe list of Flex applications appears in the dialog box. This list includes all MXML files<br \/>\nthat were added as applications, regardless of their root tags.<br \/>\nYou can add and remove modules from this dialog box by using the Add and Remove<br \/>\nbuttons.<\/p>\n<p>Well that dialog screen does not reflect your choices later, but also created in the problems tab the message<\/p>\n<p><strong>&#8220;An internal build error has occurred. Please check the Error Log.&#8221; <\/strong><\/p>\n<p>This is a catch all error when Flex Builder coughs up blood. Now I can see if you are messing with files outside of an integrated product you should be prepared to see the product cough. But I noticed in searching for this error message on the web, many folks have hit it in various ways while working inside of Flex Builder.<\/p>\n<p>In my case I wanted to have a source folder called modules. The error was that I also needed to create manually  a bin folder named modules. When you follow the directions above to set the modules as runnable, this does not occur automatically.<\/p>\n<p>Well no matter what the reason for the error message you can find out more in a file in your workspace. This file is in the folder .metadata and is named .log. Once you open it you will see dumps of Flex corpuscles, a trace of its errors, and you can perhaps dig out the problem.<\/p>\n<p>In my case it was simply<\/p>\n<p>java.io.FileNotFoundException: C:\\Documents and Settings\\Lon\\My Documents\\Flex Builder 2\\ModuleLoader\\bin\\modules\\BarChartModule-debug.swf (The system cannot find the path specified)<\/p>\n<p>Flex had been building these in the bin folder and only after I forced it to run them. Once I got the bin\/modules folder created, it started doing this on its own.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I am using Flex Builder 2.01. I was attempting to follow the updated ModuleLoader documentation at Adobe blogs. The directions included:To edit the list of runnable application files: 1. Right-click the project file and select properties. 2. Select the Flex Applications option. The list of Flex applications appears in the dialog box. This list includes [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[9],"class_list":["post-29","post","type-post","status-publish","format-standard","hentry","category-general","tag-flex"],"_links":{"self":[{"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/posts\/29","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":4,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/posts\/29\/revisions"}],"predecessor-version":[{"id":3320,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/posts\/29\/revisions\/3320"}],"wp:attachment":[{"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/media?parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/categories?post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lonhosford.com\/lonblog\/wp-json\/wp\/v2\/tags?post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}