HELP! My FlexBuilder won’t start! No worries, try this …
When you tried to open an AS file in FB did you suddenly get this message?
An error has occurred. See error log for more details.
Or maybe this message when you tried to open an MXML file:
Unable to create this part due to an internal error. Reason for the failure: The editor class could not be instantiated. This usually indicates that the editor’s class name was mistyped in plugin.xml.
No worries! try this:
go to:
[workspace directory]/.metadata/.plugins/com.adobe.flexbuilder.codemodel/searchCache
backup the directories in there that end with “.index”. zip them up and put them somewhere safe. then delete the directories. leave the file “catalog.xml”.
start flexbuilder. it should work.
The problem is that the lucene index was corrupted or lost, probably during a failed FlexBuilder shutdown. So when FB starts up and it tries to load the lucene index it fails horribly and you can’t use it anymore. Hmm … maybe the FB team can add a “try … catch” block and save us the horror? :)
Make sure your log file has an error that says something like this:
java.io.FileNotFoundException: [workspace]\.metadata\.plugins\com.adobe.flexbuilder.codemodel\searchCache\SWCReference.index\segments (The system cannot find the file specified)
The log file is located in:
[workspace]\.metadata\.log
Happy coding.
/r
July 5th, 2007 at 4:17 pm
So we’re aware of this issue, and I promise, it has many many try/catch blocks to hopefully make it not do this. But thanks for posting the how-to!
https://bugs.adobe.com/jira/browse/FB-7820
July 7th, 2007 at 3:56 pm
Another reason to not depend so much on a fragile platform like Eclipse. Too many of the newer tools ar basing themselves on this IBM product and are having many issues. Like memory, speed, crashes and it’s all based on the idea that building on a common platform and ubiquity. There are other IDE’s that are much more stable, in fact I think Jetbrain’s IDEA was better at Flex 1.5 than most other of the Flex tools out there. Unfortunately Adobe looked at the market place and saw that Eclipse had the market share and went with that. Push on Adobe to offer this plugin for other IDE’s like IDEA or Netbeans.
July 9th, 2007 at 9:25 am
I don’t think eclipse is to blame for this, and the product I complained about is still in beta, so there’s not much to complain about. In fact, it was not meant as a complaint at all - my snarky remark about TCBs was written in a moment of frustration.
Anyway, I’d rather avoid an IDE war, so let’s just leave it at “to each to his own.”
As a strategic choice I can see one reason to pick eclipse: price. IntelliJ is free for 30 days or 249 for the personal license. As a developer you’d have to add that cost above the Flex Builder license cost. That would be very expensive. Another reason is the availability of the adobe source.
August 2nd, 2007 at 11:18 am
[...] A workaround to use until Beta 2 comes out [...]
August 23rd, 2007 at 4:16 am
[...] The easiest solution i found is on: http://www.machine501.com/2007/07/05/flexbuilder-wont-start/ [...]
November 2nd, 2007 at 7:34 am
just downloaded and installed the 30 day trial, and a few days later I have this problem. FB crashes at launch. It seems like its loading, and I actually see my project blink up for a fraction of a second and then it all crashes and flex buidler is gone. I saw at Adobe that the case is closed - but so is my evaluation because the product will not run at all.
I looked and found: [workspace directory]/.metadata/.plugins/com.adobe.flexbuilder.codemodel/
… but there is no /searchCache folder in there. Any ideas how to make it run again?
Thanks!
JB
November 2nd, 2007 at 7:44 am
ok I just deleted everything under /.metadata and started from scratch and now FB starts.
November 16th, 2007 at 9:22 am
My problem was related to files that I had open in Flex Builder, it would start, then I could see it re-opening my files and it would crash with the same error. The log file had a bunch of useless junk in it.
Here’s how I fixed it:
Go to:
My Documents\Flex Builder 2\.metadata\.plugins\org.eclipse.core.resources\.projects\
In this folder you will see a folder for each of your projects, go into each one and delete (or rename) the “.indexes\properties.index” file - this file tells Flex Builder 2 which files you currently have open.