Take the 2-minute tour ×
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

Whenever I open a Salesforce project in Force.com IDE, I get this error message: enter image description here

It prevents me from saving any chances to Salesforce. Here is one such error message:

Description Resource    Path    Location    Type
Save error: Unable to perform save on all files: com.salesforce.ide.api.metadata.types.Metadata$JaxbAccessorF_fullName cannot be cast to com.sun.xml.internal.bind.v2.runtime.reflect.Accessor  HandleProductPriceChange.trigger    /Warehouse/src/triggers line 1  Force.com save problem

I am working on Ubuntu 12.10 64bit, Force.com IDE version 26.0

share|improve this question
    
What version of Java are you using? –  Phil Hawthorn Jan 13 '13 at 10:58
    
java version "1.7.0_09" OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) –  Martin Betz Jan 13 '13 at 11:05
    
I would also try replacing the Open JdK with the Sun JDK, I think I had problems with Eclipse on Ubuntu when it auto upgraded Java from to Open JDK from Sun JDK. –  techtrekker Jan 13 '13 at 21:24

4 Answers 4

up vote 5 down vote accepted

You're out of the supported platform matrix with your development stack, see:

http://wiki.developerforce.com/page/Force.com_IDE_Release_Notes#Supported_Platforms

for details of supported platform.

share|improve this answer
    
Okay, going back to such an old version is out of debate, so I should switch to Eclipse + plugin? –  Martin Betz Jan 13 '13 at 11:21
    
Yeah I think I got Eclipse + IDE to work okay on Ubuntu. Prolly also try running the Force iDE via Wine? –  techtrekker Jan 13 '13 at 21:22

This is typically caused by using an unsupported version of the JRE. Specifically, version 7 of the JRE causes this issue so you will need to downgrade to version 6.

  1. Check your JRE version: This can be found under the help menu -> "about eclipse platform" (or "about force.com ide") -> installation details -> configuration details. You should see the properties java.runtime.name and java.runtime.version.
  2. Change the JRE version in your eclipse.ini file: Instructions for finding the location of your ini file for eclipse are here. You need to set the -vm argument like they have in the example.
  3. Restart eclipse and check that you are using the correct JRE: Open the configuration details from step 1 and search for the -vm argument to make sure eclipse is looking for java in the place you put in your ini file.

Note: I can confirm that version 6 of the OpenJDK JRE (openjdk-7-jre) works without any issues on 64-bit ubuntu.

share|improve this answer
    
Well, downgrading is not very handy as I use Java for more apps than only this. I guess it would be best to run Force.com IDE in a virtualbox. –  Martin Betz Jan 14 '13 at 13:00
    
@MartinBetz You do not need to downgrade. That's why I recommended putting the JRE version in your ini file so that you don't need to change $JAVA_HOME or any PATH variable. All your other programs can continue to use openjdk-7 or whatever you have. –  Greg Grinberg Jan 14 '13 at 15:25

I'm not saying your question is 100% duplicate but have a look at Unable to refresh src from server using force.com IDE, similar error message.

I used to get this one sometime on Windows 7 64-bit. Mostly when I create a new project (for example I need to reference a newly created sandbox & start working in it), sometimes when project is old but I want to make a new Apex class.

While Phil might have a good idea about it being unsupported (some incompatibility fun with 32/64 bit versions of plugins?) please try if answers from the other question change anything for you.

I simply restart the IDE or "switch workspace". Sometimes restart with "run as administrator". I believe it flushes some cache/obtains access to files that were previously non-writeable... I don't know really. "Cargo cult" ;)

share|improve this answer

I get this issue all the time. I am the same as @eyescream I just restart the IDE and the problem is solved.

I have been able to isolate this issue but never done anything about it. The way to reproduce the problem is to create a new apex class or trigger in the IDE.

It will save the class or trigger to the server but make a change and it will not save. This only seems to be a problem if "Build Automatically" is checked in the IDE. a Manual save does not cause a problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.