Max Titov IV @ TechSplice

Flex Builder 2 Crash

Don’t you hate it when you try to get back to the project that you just been working on and all of a sudden the main application doesn’t start? In this case I am talking about the Adobe Flex Builder 2 which crashed on me about ten minutes ago.

Similar event occurred a while back, I came home attempted to open Adobe Flex Builder and witnessed a crash before the program started.

The message: “Error: An error has occurred. See error log for more details.” flashed before my screen four times followed by a convenient reference to the log file: An error has occurred. See the log file ../../My Documents/Flex Builder 2/.metadata/.log.

Typically after examining the log file and discovering a long list of Java java.lang.NullPointerException error messages

!ENTRY org.eclipse.osgi 2007-07-20 10:55:52.296
!MESSAGE Bundle update@plugins/com.adobe.flexbuilder.debug.e32_2.0.155577/ [70] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2007-07-20 10:55:52.296
!MESSAGE Missing required bundle org.eclipse.debug.ui_[3.2.0,99.0.0).

I did the next best thing and Googled for more information. Sadly the search engine results did not come in handy and I fixed the problem by simply reinstalling the application.

Unfortunately as mentioned above a similar incident occured about fifteen minutes ago. This time around I didn’t feel like uninstalling the program and decided to fiddle with the application my self. Here are my findings:

Sollution:

1) Quick and dirty:

Go to the .metadata/.plugin directory and rename it to something different. This action will remove the metadata settings that eclipse stored but you will be able to run the application freely again. To get your data back simply perform an import operation for each project that you had in your Workspace.

2) More detail:

Go to the .metadata\.plugins\org.eclipse.core.runtime directory. Open the com.adobe.flexbuilder.standalone.prefs file and modify the line flexbuilder.afterFirstLaunch=true. The end result contents of the file should look like this:

#Sat Jan 10 00:12:04 PDT 2005
flexbuilder.afterFirstLaunch=false
eclipse.preferences.version=1

Save the file and try opening the application again. This should fix the problem and get you back on your feet. I hope this helps those of you who run in to this problem.

This entry was posted on Friday, July 20th, 2007 at 8:24 am and is filed under Flex. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.