Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Can anyone give me a direction to trouble shoot this? GP 2013 on windows 2008.
There are dll in AddIns folder, but GP appears working despite this error shows up in event view.
Faulting application name: Dynamics.exe, version: 184.108.40.206, time stamp: 0x515dcd6d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0xb3c
Faulting application start time: 0x01cecf69b38c5f4a
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: f42766de-3b5c-11e3-899e-00155da40f36
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at System.Reflection.RuntimeAssembly._nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, Boolean, Boolean, Boolean)
at System.Reflection.RuntimeAssembly.nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, Boolean, Boolean, Boolean)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(System.Reflection.AssemblyName, System.Security.Policy.Evidence, System.Threading.StackCrawlMark ByRef, Boolean, Boolean)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(System.String, System.Security.Policy.Evidence, Byte, System.Configuration.Assemblies.AssemblyHashAlgorithm, Boolean, Boolean, System.Threading.StackCrawlMark ByRef)
does this error ocurre when the user log in in GP?
when you said all dll are in AddIns folder is because you have development with visual studio tools?
How much RAM on the workstation?
Prior to GP 2013 SP2, the add-ins needed to be registered in the Dynamics.exe.config file, in the addins section. As such, the addins in the Addins folder also needed to be moved to root folder where the runtime engine (Dynamics.exe) resides.
IF you install GP 2013 SP2, you will no longer need to move the assemblies out to the root folder and they should load just fine.
Mariano is correct you shouldn't have any files in the addins folder anymore. What is the name of the file?
Hi Mariano and Jonathan,
Can you point to any documentation or reference for what you are describing about needing to edit the Dynamics.exe.config prior to SP2, moving custom AddIn assemblies to the root folder, and not needing files in the AddIns folder anymore?
I just checked the RTM, SP2, and R2 versions of the VS Tools documentation, and they do not seem to match what either of you are describing.
1. The Dynamics.exe.config is only discussed in the R2 version for specifying supported client types--it is not mentioned at all in the RTM or SP2 versions.
2. All three versions indicate that default GP client AddIns should be copied to the AddIns folder. There is only a mention in the R2 version that the DLLs can be copied to the root directory (when using the Dynamics.exe.config option)
3. I don't see any documentation to explain Jonathan's statement that "you shouldn't have any files in the addins folder anymore", as all three versions of the VS Tools documentation specifically state to deploy add-ins to the AddIns folder for a default GP client configuration.
Can you both clarify?
I guess I don't know of any documentation it is just something that is known. We took those files out of the Add-ins folder because they were causing some performance issues. The Dynamics.exe.config file has always been used going back many versions.
Are you looking trying to develop a Add-in or just get this error resolved?
I have developed many add-ins for GP and I've always deployed the DLL to the AddIns folder without issue.
For the first time, while deploying to a client's terminal server (in the AddIns folder), I am seeing the System.IO.FileLoadException error referenced by the OP.
The DLLs work fine on two of my development servers, but throw the error on the client's server, causing GP to crash at startup. The only thing different that I can see if that the client is running a 32-bit terminal server. My DLLs are compiled x86, but I was going to test on an older 32-bit dev machine to see if I can reproduce the issue.
I am open to trying to move my DLLs to the root directory to see if that works, but this thread is the first that I've heard of that approach. If the AddIn is moved to the root directory, must the DLL be added to the Dynamics.exe.config file to be loaded?
Is the AddIns folder no longer recommended? If so, can you send a note to the documentation team to have them update the VS Tools documentation?
Review this link, I hope this can help you.
Thank you! I'm checking with the client to see if that solves their problem, but based on my tests, it looks like the culprit.
I tested downloading my DLLs in a zip file from OneDrive and copying them to my AddIns directory on my dev server, and that caused GP to crash with the same CLR System.IO.FileLoadException error.
When I check the DLL files, they are showing as blocked with the Unblock button.
I've run into problems due to the file blocking feature, but it seems so random that I always forget to check for it.
Thanks a million for pointing me to Patrick's blog post.
I am getting this error after installing GP2010 year end update for 2014 on a Windows 7 computer. We cannot find anything definitive about how to fix? We have repaired GP and we still get the message. Any help here would be great appreciated.....
Can you post the full error message you are seeing, either from the error dialog or Event Viewer? And perhaps a screen shot of the error dialog?
I'd like to confirm it contains "System.IO.FileLoadException" and "Microsoft.Dexterity.Bridge.AddinManager.LoadAddinsFromFolder", or if it has different details.
It was the exact same error message as the first message in this post. We fixed it by completely uninstalling and reinstalling GP.
Thanks for responding though!
Thanks, Mary. I was able to unblock the dlls and get past the error. Even 3 1/2 years after the solution was provided. :)
Business Applications communities