I am importing 16K-18K lines on a monthly sales entry. Last month the integration failed at record 16165. This month it is failing at 17751. It gives me an RDO error that IM has lost connection with the server. I can't figure out what is going on. Dynamics crashes. I restart Dynamics and IM, remove the lines from the header file that have already imported, and import the rest of the lines and it works fine. Any ideas?
*This post is locked for comments
I am encountering this same issue, but my integration has failed at line 950, then 958. I have tried on the Finance Director's PC, and also RDP'd directly to the SQL Server.
We could break up the files into batches of 900, but that's a band-aid. If anyone knows how to fix this I would greatly appreciate it!
I was wondering if you got any resolution with Microsoft on this matter. We are encountering a similar problem but with a smaller number of transactions.
I am going to try a few of things noted in the thread, but wondering if anyone has an update.
Who is the engineer you are working with on this?
I heard from Microsoft yesterday. They have been able to replicate the issue, but they are still troubleshooting. In the mean time, I may be learning eConnect. I will keep this open until I receive a final answer from them.
Any update on this?
IM is not designed to do that large number of records. I would recommend you split these up into smaller integrations. You can create a group integration which will allow you to run multiple integrations one after another.
Please have a look on the below link.
community.dynamics.com/.../im-troubleshooting-rpc-errors-when-running-integration-manager.aspx
Hope this helps!!!
Actually 16384 is very familiar to me. It is the max value of a small integer . Ran into this with Great Plains on integrating a bank reconciliation. Actually had to have Great Plains give me a .cnk file that we could bring in more than 16384 bank transactions. You have a choice, get Great Plains on the line and let them know and request a .cnk file to fix it, which is going to cost you a support call, and a whole lot of time while they verify exactly what field is causing the issue.
Use econnect or Smart Connect to bring in your transactions quicker and more efficiently. Or break up your file so that it runs less than 16384 transactions at a time.
Sue
I am doing this right on the SQL server, and no, there are no wireless connections on it.
With that many records, IM probably is actually losing connection due to intermittent network comm issues. Are you running over a wireless connection? Try hard wiring it. That's a lot of data to import using IM. You'd be better off using eConnect or Scribe.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (