We have an integration solution set up between a custom system and a CRM system. When we are syncing from the custom system to the CRM system, we sometimes get timeout-errors. Especially when we have a bulk-load going to the CRM system.
The error is this one:The adapter failed to transmit the message going to send port "..." with URL "...". It will be retransmitted after the retry interval specified for this Send Port. Details: "The operation has timed out".
We've been searching for a solution for this problem for a while already, but we can't seem to find it... Anyone can help us?
A side-effect of these timeouts (well, we hope it is due to that) is that sometimes contact or accounts are created more than once in the CRM-system... Anyone else experienced that already?
I didn't have a chance to work with CRM adapter, but don't you have there some time-out configuration parameter?
I'm afraid it's not as simple as that... There ain't much possibilities of configuration for that adapter.It must be possible to configure it somewhere, but we can't find it...
You can look into DLL of that adapter (I hope it's not obfuscated) and try understand if there's some configuration or some value for TimeOut.
Is on CRM side such configurable value? Maybe need a check - from default to increase to bigger value :)
Did you try to transfer smaller amount of Data?
It seems to be impossible to open the contents of the DLL (with Reflector)... so I'm afraid I can't find where to configure that timeout.
I know nothing about CRM... So I don't know it it's configurable there. I asked some people, but they said they don't think it should be set on CRM-side, but on BizTalk-side.
When we transfer small amounts of data, it's no problem at all... But sometimes we need to process a whole backload and then it's a big amount of data.
Did someone use the adapter already?
Check this link out http://microsoftcrm3.blogspot.com/
Look for header "Maximize Attachment size in MS CRM "
I'm sorry for the late answer... But that solution didn't seem to do the trick :-(
I've been playing with that timeout, but it doesn't matter when I make it bigger. When I set it to something really small, I get simular timeout errors, but not the one's I'm having.
It seems to be a client timeout of BizTalk...Adjusting the execution timeout in the machine.config on the BizTalk-machine doesn't help either.
Did you get a solution to this, i'm interested as we have recently experianced this, i have set retry count to 0 to avoid dups,i.e let the message fail which then is picked up by our resubmission process,