function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
grigri9grigri9 

At my wits end with a force.com IDE bug

This is a brand new windows 7 install and so far I have been completely unable to get the force.com IDE working on this machine.

 

I am getting the following error when trying to create a force.com project:

 

com.salesforce.ide.api.metadata.types.Metadata$JaxbAccessorF_fullName cannot be  cast to com.sun.xml.bind.v2.runtime.reflect.Accessor

 

Specifically, I am able to create the project in eclipse and fetch the component metadata but when I click finish I get this error. This occurs on DE and sandbox orgs alike.

 

I've tried everything I could possibly think of to get rid of it but nothing seems to solve it. This error persists across all versions of eclipse that I've tried it on (galileo, helios, helios 64-bit, stand alone force.com IDE). I've even gone back to a system restore point and completely re-installed the JDK and eclipse from scratch and this error still occurs.

 

ANY information that anyone has about the root cause of this error or what might be causing it would be greatly appreciated.

 

 

Best Answer chosen by Admin (Salesforce Developers) 
colemabcolemab

right click on the IDE icon and choose "run as .." then select administrator.

 

I had mutiple copies of the IDE open (one for data loader on JDK 1.7, and one for the force.com project) when I got the error.  Closing the JDK 1.7 project and restarting the force.com project eliminated the error for me.

 

I am on win XP with JDK 1.7.0, JRE6 and JRE7 installed.

All Answers

Martin.LehmannMartin.Lehmann

I got the same error where my installation setup was

* Windows 7

* JRE 7 32 & 64 bit

* Winter '11 Force.com IDE 64 bit

 

The workaround was to run the force.com IDE in Administrator mode which "solved" the problem.

 
grigri9grigri9

I'll have to try that. I was able to fix this by switching to an older version of the JRE. My working configuration is:

 

*Windows 7

*JRE 6 update 26 (32 & 64 bit)

*Winter '11 Force.com IDE

*Eclipse Helios SR1 32 bit

 
JRINGJRING

I can confirm the above.

My specs:

 

Windows 7

java version "1.6.0_26"

Java(TM) SE Runtime Environment (build 1.6.0_26-b03)

Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing)

Winter 11 Force.com IDE

 

Thanks for that find!
ASteffensASteffens

And so how does one run the Force.com IDE in admin mode?

"The workaround was to run the force.com IDE in Administrator mode which "solved" the problem."
colemabcolemab

right click on the IDE icon and choose "run as .." then select administrator.

 

I had mutiple copies of the IDE open (one for data loader on JDK 1.7, and one for the force.com project) when I got the error.  Closing the JDK 1.7 project and restarting the force.com project eliminated the error for me.

 

I am on win XP with JDK 1.7.0, JRE6 and JRE7 installed.

This was selected as the best answer
LeeTsiamisLeeTsiamis

Great find, I can also confirm that this spec is working without running as an admin.

Thanks for the contribution everyone.
SmitaGSmitaG

That totally worked for me too! great live the questions and answers :) Thanks!