function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
dev_jhdev_jh 

Issues with Eclipse

Hi all,

 

We are using Eclipse to deploy changes made on a Sandbox and we are getting a few odd errors. This has made us deploy in batches (and also, having to re-do changes manually in Production, for those changes that just can´t be migrated!).

 

The most annoying thing is that, whenever we want to add objects to an existing Force.com project in Eclipse (like, for example, the Opportunity Standard Object) we get an error message and it doesn´t work. The message states: "Factory Exception occurred when marshalling package manifest into DOM document, please make sure package manifest is well-form and present in proper location. Reason: Invalid byte 2 of 4-byte UTF-8 sequence".

 

The only option we have is to delete the project and recreate but this is incredibly frustrating. Any thoughts?

 

Thanks,

 

J

Best Answer chosen by Admin (Salesforce Developers) 
JonPJonP

What version of Eclipse are you using?  What version of the Force.com IDE?  Do you have any other third party plugins installed in Eclipse?

 

I would recommend trying this in a clean install of Eclipse 3.3.2 with the Force.com IDE 15.0.2, using a fresh Force.com workspace and Force.com project, and see if that resolves the issue.  Once you know whether it works in a controlled environment, you can go back and figure out what's different about your current (old) Eclipse install.

All Answers

JonPJonP

What version of Eclipse are you using?  What version of the Force.com IDE?  Do you have any other third party plugins installed in Eclipse?

 

I would recommend trying this in a clean install of Eclipse 3.3.2 with the Force.com IDE 15.0.2, using a fresh Force.com workspace and Force.com project, and see if that resolves the issue.  Once you know whether it works in a controlled environment, you can go back and figure out what's different about your current (old) Eclipse install.

This was selected as the best answer
dev_jhdev_jh

 Thanks John... Actually the problem is gone now and since we tried a few of your suggestions it is quite probable one of them did the trick! All the best,

 

Javier