IM - Troubleshooting RPC errors when running Integration Manager

Lately, I have seen a number of forum discussions where users have reported receiving a number of RPC (Remote Procedure Call) errors when running Integration Manager and thought I would offer a number of troubleshooting tips for this issue. But first, here are some of the common error messages you may see:

"The destination could not be initialized due to the folowing problem:  The RPC server is unavailable."


"DOC 1 ERROR: The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) - The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))"

To begin troubleshooting this issue try the following options:

1. Close all running instances of Microsoft Dynamics GP and open Windows Task Manager. Under the Processes tab, verify that there is not more than one instance of the Dynamics.exe process running.

Windows Task Manager
If you find an additional Dynamics.exe process running, select it and click the End Process button. At this point, restart Microsoft Dynamics GP and try running your Integration. This solution is also outlined in KB article 943948.

2. If you are on Terminal Server or Citrix, make sure you don't have more than one active session at a time. Since you probably will not have access to Terminal Server Administration or Citrix Console, you will need to address this with your Systems Administrator. In any case, if you find more than one active session, decide with your administrator the best procedure to close down the unwated session.

You will  typically experience this error message because you have not been following the correct procedures to close down your Terminal Server or Citrix session.

3. If on Terminal Server or Citrix, you may receive this error if running Integration Manager as a published application. You will receive RPC errors if you attempt to integrate a document to Microsoft Dynamics GP when both Integration Manager and Microsoft Dynamics GP are ran as published applications.

In this case, you will want to log on to the Terminal Server console or Citrix console and execute your integration. Since this may not be acceptable to your System Administrator, as an alternative you can setup a dedicated Microsoft Dynamics GP and Integration Manager client.

4. Repair or reinstall Integration Manager and make sure to be using the latest service pack. Yes, when all else fails, some times this is the only recourse left. To download the latest Integration Manager service packs, use the following links:

Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 2010
(PartnerSource/CustomerSource access required)

Service Packs and Hotfixes for Integration Manager for Microsoft Dynamics GP 10.0
(PartnerSource/CustomerSource access required)

Until next post!

Mariano Gomez, MVP
Maximum Global Business, LLC


Chip Reed said…
I am having the same issue after updating to GP2013r2. The file is the same and the integration is the same. On the Item integration it always fails at 630 records irreguardless of the dataset.
Unknown said…
Mario, we are encountering the same error message - similar at least - have looked at all the notes above and we are not running on Citrix / Terminal server - our system has been running for a number of years and we just recently updated to GP2013 r2 and this is when the error message started.

If possible, I have a OneNote file that outlines in pretty good detail what we have. I would like to send to you.
Mariano Gomez said…
Please send the OneNote file to me at mgomezb _AT_ bellsouth _DOT_ net
Cindy Kammermeier said…
I'm having this same issue with GP2013R2. It always fails at about the same number of records. I can't figure out why. Did anyone find a reason that the integrations are suddenly having an issue with R2 of GP 2013? Thanks for any update!
Mariano Gomez said…
@Bill and @Cindy,

This issue can also be due to bad data in the data source. Look for delimiters that may produce additional columns if using text files.

Mariano Gomez
Cindy Kammermeier said…
So, when I'm doing my integration of inventory items it is failing at 572 items. I fix my source file by getting rid of the ones that are importing just fine and then start again, and I get to 572 items again and it fails. So, I have a 19,000 item spreadsheet that is taking me forever to get imported into GP. It seems weird that it works for 572 and then I get the error: "The following problem was encountered during destination uninitialization: -Exception from HRESULT: 0x0020001.
Mariano Gomez said…

Please open a support case with Microsoft. They will be in a better position to ascertain whether this is a bug in the software or a problem with data.

Mariano Gomez said…
@Bill and @Cindy,
I believe I found the cause of the issue you are experiencing with GP 2013 R2. As it turned out, the new GP 2013 R2 ribbons seam to cause IM to go whacky. Under User Preferences, switch the Window Command Display option to Menu Bar. You can then log out of GP and log back in, which should switch the UI.

Try running your integration once more and this should take care of the problem.

Mariano Gomez
Anonymous said…
Thank you Mariano, we will be testing this out this afternoon. My login was changed when we installed and it works fine. The person having issues was still using the ribbons. I am a power user and we thought maybe it was something to do with the security, but no changes to that helped either.
Cindy Kammermeier said…
I just put in a support request with Microsoft and they said this is a known issue with GP 2013 R2, which no known date to resolve. They told me the only workaround was to break the integrations into smaller files or to try to use the eConnect Adapter as this wouldn't happen with eConnect. Just thought you'd want to know!
Cindy Kammermeier said…
I started a new integration after I reverted my ribbons to the "old" ui and I'm getting much, much further along. I like your workaround substantially better than support's :). Just wanted to let everyone know that Mario's solution appears to be working and is easy to fix vs. creating a new integration! Thank you!
Angela Furney said…
Thanks to all for posting the workaround with GP 2013 R2, we were pulling our hair out. I attempted to look if there was an issue submitted on the Connect web site and wasn't able to find it to vote on for a hopefully faster resolution timeline. Do you know if there was anything posted to Microsoft Connect about this?
Unknown said…
This is still a problem in GP 2015 R2.
ummmhello said…
We're running into this on R2 as well. Any ideas?
Unknown said…
Mario - client is getting the HRESULT:0x80010105 error when integrating on GP2015. Any updates to a resolution on this issue?
Mariano Gomez said…

Have you tried any of the suggestions above?
jiani latrece said…

Thanks for so much help. i am in Dynamics 16. My coworker is able to integrate files just fine but I cannot, do you think your solution could work for me before I present the idea to her?

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

#MSDYNGP: Named Printers and Redirected Printers in RDP environments

Integration Manager 10 INI settings