Timeline for Unexpected element. Parser was expecting element but found ':HEAD'
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2015 at 20:16 | comment | added | Keith C | AFAIK it uses the normal bulk API endpoints. I think this is the source code github.com/forcedotcom/dataloader if you want to check further. | |
| Jul 4, 2015 at 19:56 | comment | added | Avijit | @KeithC: I have checked your 2nd option but I have not found any issue in my Org instance. I will check with our network team soon. How ever I want to know if there is any way to trace the endpoint(s) to which data loader is taking? | |
| Jul 4, 2015 at 16:34 | history | edited | Samuel De Rycke | CC BY-SA 3.0 |
added 18 characters in body; edited tags
|
| Jul 4, 2015 at 16:23 | comment | added | Keith C | I'd start by explaining what you see to them and ask them what they suggest to figure the problem out. Also ask them if the firewall has some kind of error log. Be open minded - the network is the first thing to consider based on the evidence, but it may just be a coincidence that changing network apparently solved the problem. You might also see if your problem corresponds in date/time to any documented problem in trust.salesforce.com/trust/instances. | |
| Jul 4, 2015 at 16:16 | comment | added | Avijit | @KeithC: What do you suggest? How should I work with our network team to resolve this issue? | |
| Jul 4, 2015 at 13:42 | comment | added | Keith C | Sounds like the data loader program is receiving some HTML (that has a head element) instead of a SOAP message (that has an envelope element). As the same operation works through a different network then yes your office network is the first place I would look. | |
| Jul 4, 2015 at 12:33 | answer | added | Prabhat Ranjan | timeline score: -1 | |
| Jul 4, 2015 at 10:27 | review | First posts | |||
| Jul 4, 2015 at 16:34 | |||||
| Jul 4, 2015 at 10:23 | history | asked | Avijit | CC BY-SA 3.0 |