By Steve Endow
This is a quick note about an obscure error that I received when trying to use Integration Manager 2013 to run an eConnect integration.
![]()
eConnect error - Could not load type System.Runtime.Diagnostics.ITraceSourceStringProvider
The error isn't particularly meaningful, so there's no way to troubleshoot it directly. Fortunately the error is unique enough that a Google will provide several results, such as this thread:
https://stackoverflow.com/questions/24291769/could-not-load-type-system-runtime-diagnostics-itracesourcestringprovider
The recommended solution is to install / reinstall .NET 4.5.2. But I verified that I already had 4.5.2 on my server, so that seemed odd.
Then I re-read the original question--note that the user having the issue reports that they just upgraded their server from Windows 2008 to 2012?
Coincidentally, I also upgraded my server from 2008 R2 to 2012 R2 last week. It would seem that the Windows upgrade process breaks something about the .NET 4.5 installation.
So I downloaded the .NET 4.5.2 web installer and reinstalled it.
![]()
After .NET 4.5.2 was reinstalled, the error went away. Small victories!
![]()
![]()
This is a quick note about an obscure error that I received when trying to use Integration Manager 2013 to run an eConnect integration.
eConnect error - Could not load type System.Runtime.Diagnostics.ITraceSourceStringProvider
The error isn't particularly meaningful, so there's no way to troubleshoot it directly. Fortunately the error is unique enough that a Google will provide several results, such as this thread:
https://stackoverflow.com/questions/24291769/could-not-load-type-system-runtime-diagnostics-itracesourcestringprovider
The recommended solution is to install / reinstall .NET 4.5.2. But I verified that I already had 4.5.2 on my server, so that seemed odd.
Then I re-read the original question--note that the user having the issue reports that they just upgraded their server from Windows 2008 to 2012?
Coincidentally, I also upgraded my server from 2008 R2 to 2012 R2 last week. It would seem that the Windows upgrade process breaks something about the .NET 4.5 installation.
So I downloaded the .NET 4.5.2 web installer and reinstalled it.
After .NET 4.5.2 was reinstalled, the error went away. Small victories!
Steve Endow is a Microsoft MVP for Dynamics GP and a Dynamics GP Certified IT Professional in Los Angeles. He is the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.
