how to solve log4net error

Question

0.00/5 (No votes)

See more:

, +

I had facing an could not load file error after using crystal report.
error as below:

Server Error in '/' Application.

Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

I check with property page, log4net version is 2.0.5, is updated by nuget.

after browsed on internet, i add this to my web.config

<dependentAssembly>
    <assemblyIdentity name="log4net" publicKeyToken="1b44e1d426115821" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.0.5.0"
                         newVersion="2.0.5.0"/>
</dependentAssembly>

but it still not work.
Please help.

Posted 4-Jan-16 21:54pm

Member 12115140

Add a Solution

Comments

Sinisa Hajnal 5-Jan-16 4:29am

Did you deploy everything? Are you trying it on the same server (even local) as it was before using CR?

Member 12115140 5-Jan-16 4:53am

yes. And it is ok on local

ZurdoDev 5-Jan-16 7:41am

It's missing the dll.

Member 12115140 5-Jan-16 10:28am

So, can give me a way to solve this?

ZurdoDev 5-Jan-16 10:36am

Put the dll in the bin folder.

Member 12115140 5-Jan-16 10:40am

an error appear after add the dll:
The type initializer for 'CrystalDecisions.Shared.SharedUtils' threw an exception.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)