-
Notifications
You must be signed in to change notification settings - Fork 41
1.1 Issues Or Problems
Scot P. Floess edited this page May 28, 2014
·
2 revisions
This page highlights some issues/problems you may see when using Solenopsis.
If you see something like this in output:
info: [echo] [echo] Solenopsis release version [N/A] [echo] Solenopsis version [1.1] [echo] [echo] Ant version [Apache Ant(TM) version 1.9.2 compiled on September 12 2013] [echo] Java version [1.7] [echo] pull: [echo] Generating package.xml [delete] Deleting directory /tmp/sfloess/solenopsis/1.1/non-folder-pull [mkdir] Created dir: /tmp/sfloess/solenopsis/1.1/non-folder-pull [echo] [echo] [echo] Processing: [foo] [echo] [echo] URL: [https://test.salesforce.com] [echo] API: [30.0] [echo] [echo] Jar: [/home/sfloess/.ant/lib/ant-salesforce.jar] [echo] [echo] [delete] Deleting directory /home/sfloess/Development/personal/solenopsis/Solenopsis/ant/${solenopsis.env.foo.HOME} [mkdir] Created dir: /home/sfloess/Development/personal/solenopsis/Solenopsis/ant/${solenopsis.env.foo.HOME} [sf:retrieve] Note: use ant -verbose to get more information on the failure
Make sure you have defined "foo" (or whatever you are using for a dependent environment) within your ~/solenopsis.properties file as one of the values for the solenopsis.ENVIRONMENTS property. Above, the problem can be spotted in the [delete] output as "${solenopsis.env.foo.HOME}" - meaning foo wasn't defined.
If you receive this error:
Failed to login: Failed to parse detail: START_TAG seen ...... @1:434 due to: com.sforce.ws.ConnectionException: Incompatible type 'class com.sforce.soap.partner.fault.LoginFault' specified as xsi:type. It must be a subclass of 'class com.sforce.ws.ConnectionException'
It denotes a problem with your credentials (most likely your security token). Ensure your user name and password are correct. If they are, consider resetting your security token.