![]() ![]() And we came to a conclusion that even our development environment is 64-Bit, we need to have the log4net assembly for 32-bit since crystal is referring to that internally. Afterwards the GAC was having both the assemblies registered.Īnd this resolved the issue. Therefore we installed the Crystal Runtime version 13 for 32-bit. Then we came across with the following article which gave us some kind of a hint of the issue we are facing:Īnd it occurred to us that even though we had the same assembly which the error is pointing installed in GAC, still the Crystal assemblies were expecting some other log4net assembly to be presented in GAC. But later we tried by un-installing the runtime and re-installing it again, assuming some corruption might had occur during the previous installation or afterwards. But it was sort of a puzzle to us since we already had it installed it. Then when we googled the issue we could be able to come across with similar incidents, where the majority of the people were able to resolve the issue by installing the Crystal Runtime. And in our application code we were using the same log4net and it was already presented in the bin folder. ![]() Because we could see that in GAC, the mentioned assembly (log4net) is being registered with the version 1.2.10.0 and with the correct ‘PublicKeyToken’ (692fbea5521e1304).Īnd we didn’t really worry about the ‘Processor Architecture’ column, since our development environment is 64-bit and all the Crystal Reports development pre-requisites were there in the development environment and Crystal Runtime was already installed (version 13 – 64-bit). The located assembly's manifest definition does not match the assembly reference.įile name: 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'Īt ()Īnd the confusion grew even further when we checked the GAC (Global Assembly Cache). PublicKeyToken=692fbea5521e1304' or one of its dependencies. ![]() > System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, > System.TypeInitializationException: The type initializer for '' threw an exception. : Exception has been thrown by the target of an invocation. ![]() This is the first of a series of error which lead to another and so forth. The issue was when a Crystal Report file is loaded through. We faced an issue sometime ago, which put us into a very tight situation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |