Could not load file or assembly objectpooling.dll error on production server

Question

1.00/5 (1 vote)

See more:

Hi All,

We create one WCF application and used technique of Object Pooling for object creation. Everything works fine on code & then on testing machines. But when we deploy that application to production server, we get error like

System.IO.FileNotFoundException: Could not load file or assembly 'ObjectPooling.dll' or one of its dependencies. The specified module could not be found.
File name: 'ObjectPooling.dll'

ObjectPooling.dll is present in the build also same build tested on various places. We can't track down the issue on production server.

Can anyone have an idea how to overcome this issue OR what are the possible ways to tackle this?

What I have tried:

We copy dll into several places including C:\Windows\System32 , C:\Windows\Microsoft.NET\Framework\v2.0.50727 , C:\Windows\Microsoft.NET\Framework\v4.0.30319 and more.

But not able to resolve.

Posted 12-Mar-18 4:22am

Umesh AP

Updated 19-Mar-18 2:07am

v2

Add a Solution

Comments

Nagaraj Muthuchamy 12-Mar-18 11:56am

Could it be that DLL version is not matching in PROD?

Richard Deeming 13-Mar-18 12:41pm

Could be a 64-bit / 32-bit issue?

Umesh AP 19-Mar-18 8:05am

Thanks Nagaraj & Richard for your replies.
Yes, its the issue with 32-bit/64-bit DLL compatibility. My issue is resolved by referencing proper DLL.
Still I am confused that on some systems it works properly and on production server its not worked.

1 solution

Add a Solution

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)

Umesh AP · Accepted Answer · 2018-03-19T02:08:00

Solution 1

My issue is resolved by referencing proper DLL (issue with 32-bit/64-bit DLL mismatch).

Posted 19-Mar-18 2:08am

Umesh AP