
I have followed the steps in the DL documentation and configured the command line execution of dataloader. I have checked the below already:
1. Generate key file
2. Encrypt password (tried both the password only and password+security token)
3. Verify whether decryption of encrypted pwd matches the original string
4. Build SDL
5. Build process-conf.xml
6. Run the process.bat
I end up with same error again. Below is the error message dump from command line. I have eyeballed on this message detail for a day now. Need a pair of fresh eyes may be. Please, if someone could point me what's missing here.
2014-02-10 14:47:28,281 INFO [main] controller.Controller initLog (Controller.java:389) - Using built-in logging configuration, no log-conf.xml in C:\Program Files (x86)\salesforce.com\Data Loader\bin\log-conf.xml
2014-02-10 14:47:28,281 INFO [main] controller.Controller initLog (Controller.java:391) - The log has been initialized
2014-02-10 14:47:28,281 INFO [main] process.ProcessConfig getBeanFactory (ProcessConfig.java:103) - Loading process configuration from config file: C:\SF\conf\process-conf.xml
2014-02-10 14:47:28,359 INFO [main] xml.XmlBeanDefinitionReader loadBeanDefinitions (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from file [C:\SF\conf\process-conf.xml]
2014-02-10 14:47:28,406 INFO [csvAccountExtract] controller.Controller initConfig (Controller.java:327) - config dir created at C:\SF\conf
2014-02-10 14:47:28,811 ERROR [csvAccountExtract] config.Config decryptProperty (Config.java:692) - Error loading parameter: sfdc.password of type: java.lang.String
javax.crypto.BadPaddingException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.DESCipher.engineDoFinal(DashoA13*..)
at javax.crypto.Cipher.doFinal(DashoA13*..)
at com.salesforce.dataloader.security.EncryptionUtil.decryptString(EncryptionUtil.java:210)
at com.salesforce.dataloader.config.Config.decryptProperty(Config.java:686)
at com.salesforce.dataloader.config.Config.postLoad(Config.java:638)
at com.salesforce.dataloader.config.Config.load(Config.java:617)
at com.salesforce.dataloader.config.Config.load(Config.java:593)
at com.salesforce.dataloader.controller.Controller.initConfig(Controller.java:354)
at com.salesforce.dataloader.controller.Controller.<init>(Controller.java:110)
at com.salesforce.dataloader.controller.Controller.getInstance(Controller.java:212)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:110)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:100)
at com.salesforce.dataloader.process.ProcessRunner.main(ProcessRunner.java:253)
2014-02-10 14:47:28,827 FATAL [csvAccountExtract] process.ProcessRunner topLevelError (ProcessRunner.java:238) - Unable to run process csvAccountExtract
java.lang.RuntimeException: com.salesforce.dataloader.exception.ControllerInitializationException: Error loading config file: C:\SF\conf\config.properties. Please make sure that it exists and is readable
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:112)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:100)
at com.salesforce.dataloader.process.ProcessRunner.main(ProcessRunner.java:253)
Caused by: com.salesforce.dataloader.exception.ControllerInitializationException: Error loading config file: C:\SF\conf\config.properties. Please make sure that it exists and is readable
at com.salesforce.dataloader.controller.Controller.initConfig(Controller.java:360)
at com.salesforce.dataloader.controller.Controller.<init>(Controller.java:110)
at com.salesforce.dataloader.controller.Controller.getInstance(Controller.java:212)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:110)
... 2 more
Caused by: com.salesforce.dataloader.exception.ParameterLoadException: Error loading parameter: sfdc.password of type: java.lang.String
at com.salesforce.dataloader.config.Config.decryptProperty(Config.java:693)
at com.salesforce.dataloader.config.Config.postLoad(Config.java:638)
at com.salesforce.dataloader.config.Config.load(Config.java:617)
at com.salesforce.dataloader.config.Config.load(Config.java:593)
at com.salesforce.dataloader.controller.Controller.initConfig(Controller.java:354)
... 5 more
Caused by: javax.crypto.BadPaddingException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
at com.sun.crypto.provider.DESCipher.engineDoFinal(DashoA13*..)
at javax.crypto.Cipher.doFinal(DashoA13*..)
at com.salesforce.dataloader.security.EncryptionUtil.decryptString(EncryptionUtil.java:210)
at com.salesforce.dataloader.config.Config.decryptProperty(Config.java:686)
... 9 more
답변 9개

Thanks again, Abhishek. Repeated all the steps in another fresh folder and accidentally fixed the issue. :-) Upon investigating, I noticed there was a config.properties file, that was earlier generated by the data loader UI tool, was left in the same folder where process-conf.xml resided. This caused a conflict between parameters and the login process failed. (my understanding)
So, I removed the config.properties file and executed the process, and the load went through.
Looking at this behavior, seems the data loader only expects the process-conf.xml. After the load completion it generates an empty config.properties and processName_lastRun.properties files. Is my understanding correct?
The load I executed was an export. Are there other pointers I should consider before running the loads for other operations such as insert, upsert and delete?