Failed to load Antlr3.Runtime.dll file or assembly.

Question

We used TeamCity for our .Net Framework 4 build server and ASP.NET MVC2 and NHibernate Our build server recently shut down due to the release of Amazon EC2. We are installing a new build server.

However, although nothing has changed in our code base, Teamcity gives the following error.

ResGen error RG0000: Could not load referenced assembly "C:\TeamCity\buildAgent\work\1e7706dcd512f467\xxx\Lib\Antlr3.Runtime.dll". Caught a FileLoadException saying "Could not load file or assembly 'C:\TeamCity\buildAgent\work\1e7706dcd512f467\xxx\Lib\Antlr3.Runtime.dll' or one of its dependencies. Provider DLL failed to initialize correctly. (Exception from HRESULT: 0x8009001D)". 

This DLL file exists along with other necessary DLL files. Any solution?

Answer 1

Sometimes, within a specific assembly within a certain assembly agent, the situation starts to go wrong. I struggled with this problem before, but in my case, MSBuild owned a lock in one of the DLLs, so TeamCity could not rewrite it.

So basically:

• Try to force clean
• Try to delete the working folder of the assembly "C:\TeamCity\buildAgent\work\1e7706dcd512f467" , so the next time you build TeamCity will force all files to be captured.

Answer 2

I found a link to error code 0x8009001D on the Microsoft support site here .

This problem occurs if you change the value of the MountedDevices registry to change the destination letter of the boot disk or the drive letter of the system drive.

Workaround for error code 0x8009001d

To resolve this issue, you must delete the entire contents of the MountedDevices registry key. This key is located in the following registry key: HKEY_LOCAL_MACHINE \ SYSTEM \ MountedDevices For more information, click the following article number to view the article in the Microsoft Knowledge Base: 223188 How to change the system / boot drive letter in Windows 2000 You cannot change the MountedDevices registry key in Windows XP because C: \ Windows, there are many hard-coded paths. These hard-coded paths may not load. This behavior then triggers the error code associated with WPA.

I have never come across this myself, but hopefully this helps.

Answer 3

This helped me (and I feel very comfortable with him because I did not need to change any obscure settings or delete files that I really don't know)

• comment out the line <package id="Antlr" version="3.4.1.9004" targetFramework="net45"/> from the packages.config file.
• recompile and run → no problem.
• include the line <package id="Antlr" version="3.4.1.9004" targetFramework="net45"/> .

What are all people!

Answer 4

I had the same problem today. In the IIS-> preset application pool settings, I changed the "Enable 32-bit applications" settings to true

Answer 5

This also happens when the assemblies listed in the packages.config file are not synchronized with the assemblies specified in the project. If so, then simply remove the package from package.config that the project is not referring to, then rebuild the project or solution.

Answer 6

Packs of guys ... packages. No matter what problem you have with the DLL, for example with some DLLs, it sometimes helps to update them. Cause. You probably just ran some Windows updates or (Windows did it yourself), and this makes your new patches incompatible with the old DLLs in your project. Step 1 Go to Tools> Nuget Package Manager> Manage Nuget Package for Solution> Updates> Update All (usually the best option :-)). And wait ... if you get this error: Nuget.exe Install - Microsoft.CSharp already has a dependency on System.Dynamic.Runtime , then it updates your first NUGET package manager (Step 2): Tools> Extensions and Updates> Updates> Visual Studio Gallery> Click Refresh next to NuGet> Restart VS. Repeat Step 1. Good luck! (VS Studio 2013)

Answer 7

in visual studio ---> tools ---->

in the console console manager

PM> install-package antlr and press enter