ACT! to SugarCRM - "Client found response content type of 'text/html', but expected 'text/xml'"

ATTENTION: This forum is no longer active. Please navigate to our new support site at https://support.starfishetl.com/
Viewing 5 posts (of 5 total)
grappaport
User - Author
Post count: 5
#1

Hello. I am using the ACT! to SugarCRM map and I am receiving an error when trying to run an Update on Accounts and Contacts. The error is: "System.InvalidOperationException: Client found response content type of 'text/html', but expected 'text/xml'. The request failed with an empty response. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at StarfishEngine.SugarCRM.sugarsoap.set_entry(String session, String module_name, name_value[] name_value_list) at StarfishEngine.StarfishService.PostStageSugar(rowdat& RowData, Stage st)." I have come across this error before and it had to do with me trying to update by matching the id field instead of another field. This is not the case this time. I cannot figure out what is causing the errors and there are a lot of them. I checked the sugar log and I do not see anything that would cause the issue. I also cleared the log and ran the update and nothing was added. I am stumped at this point. Any suggestions or ideas would be helpful.

Thank you in advanced.

Garrett R.

Comments (5)

Justin Kuehlthau's picture Justin Kuehlthau
Administrator
Post count: 24
#2

Aron may have a better solution, but when I run into these vague errors, I generally copy the Job, delete half the mappings and see if it works. Keep doing this until I find the problem field. Then go from there.

Is your map using the Sugar SOAP or REST API? If you are using SOAP, you could try using the new REST API.

Log in to post comments
grappaport's picture grappaport
User - Author
Post count: 5
#3

Thank you for your response Justin. They are still on version 6 so it is still using SOAP. I have tried removing and adding mappings and it still doesn't work. The weird thing is that I have only added two mappings to it since the last time I ran it and even with removing those it still throws the same errors.

Log in to post comments
grappaport's picture grappaport
User - Author
Post count: 5
#4

I am still running into these errors. I checked the sugar log again and there is nothing that is showing up. I also checked the starfish logs and the only information that it gives me is the error that I specified in my original post. Does anyone have any other ideas?

Log in to post comments
Aron Hoekstra's picture Aron Hoekstra
Administrator
Post count: 2
#5

I have seen this issue pop up when trying to assign a bad ID to the Assigned To User - by chance, are you assigning that field in this job? Could you temporarily remove that mapping and try again?

Log in to post comments
grappaport's picture grappaport
User - Author
Post count: 5
#6

Hello Aron,

I realized that I never responded. Sorry about that. I was assigning an assigned to user, but I was not matching it by that so I am not sure why that would have caused an issue now. I ended up getting around by filtering by status instead of running all of them at once. I don't know if it was timing out or what was causing it. I have had this issue in the past and I know that it typically has to do with the ID but could not figure out this time because I had only changed one field from the last time that I ran it. At this point though I am not running into this issue anymore. Thanks for the help!

Log in to post comments
Viewing 5 posts (of 5 total)

Forum Login

Login or sign up for our forums to connect to the user community.

Reply

You must log in to post.

Not a Member? Register.