The exact error is as follows
Could not load file or assembly 'Microsoft.SqlServer.Replication, Version=22.214.171.124, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I've recently started working on this project again after a two month move to another project. It worked perfectly before, and I've double checked all the references.
This question is tagged with
~ Asked on 2008-09-03 10:55:53
I've found the solution. I've recently upgraded my machine to Windows 2008 Server 64-bit. The SqlServer.Replication namespace was written for 32-bit platforms. All I needed to do to get it running again was to set the Target Platform in the Project Build Properties to X86.
~ Answered on 2008-09-03 10:57:53
The answer by baldy below is correct, but you may also need to enable 32-bit applications in your AppPool.
Whilst setting up an application to run on my local machine (running Vista 64bit) I encountered this error:
Could not load file or assembly
ChilkatDotNet2or one of its dependencies. An attempt was made to load a program with an incorrect format.
Obviously, the application uses ChilKat components, but it would seem that the version we are using, is only the 32bit version.
To resolve this error, I set my app pool in IIS to allow 32bit applications. Open up IIS Manager, right click on the app pool, and select Advanced Settings (See below)
Then set "Enable 32-bit Applications" to True.
~ Answered on 2010-05-28 06:19:41
Change the value for Platform Target on your web project's property page to
~ Answered on 2010-10-26 13:09:20
Go to IIS -> Application Pool -> Advance Settings -> Enable 32-bit Applications
~ Answered on 2011-10-13 09:31:56
We recently had the issue when trying to run the code from Visual Studio. In that case you need to do
TOOLS > OPTIONS > Projects and Solutions > WEB PROJECTS and check the "Use the 64 bit version of IIS Express for web sites and projects".
~ Answered on 2015-11-05 20:15:28
For those who get this error in an ASP.NET MVC 3 project, within Visual Studio itself:
In an ASP.NET MVC 3 app I'm working on, I tried adding a reference to Microsoft.SqlServer.BatchParser to a project to resolve a problem where it was missing on a deployment server. (Our app uses SMO; the correct fix was to install SQL Server Native Client and a couple other things on the deployment server.)
Even after I removed the reference to BatchParser, I kept getting the "An attempt was made..." error, referencing the BatchParser DLL, on every ASP.NET MVC 3 page I opened, and that error was followed by dozens of page parsing errors.
If this happens to you, do a file search and see if the DLL is still in one of your project's \bin folders. Even if you do a rebuild, Visual Studio doesn't necessarily clear out everything in all your \bin folders. When I deleted the DLL from the bin and built again, the error went away.
~ Answered on 2011-06-21 13:33:05
I had this in an MVC5 app in Windows 10 against IIS Express. My solution was the following:
~ Answered on 2017-08-11 17:29:28
change it to 32-bit (true) it works
if you get this Length cannot be less than zero. Parameter name: length issue in iis server configuation do the simple thing change the connection string in web.config file like your sql server name and server name and restart iis then try to load the page it works
~ Answered on 2016-02-05 11:17:51
If Publishing in Visual Studio 2012 when erroring try unchecking the "Procompile during publishing" option in the Publish wizard.
~ Answered on 2013-10-24 22:23:57
Changing the Target Framework in project properties from .NET Framework 4.7.1 to 4.6.2 worked for me.
~ Answered on 2018-04-09 14:59:12
in windows form application I do this, Right-click on Project->Properties->Build->Check Prefer 32-bit checkbox. Thanks all
~ Answered on 2017-06-17 09:12:09
Delete the temp test directory located here C:\Users(User)\AppData\Local\Temp\VisualStudioTestExplorerExtensions\
Set all projects to x64 in Visual Studio
Set the default processor architecture to x64(Test/TestSettings/Default Processor Architecture).
Make sure to clean build the solution file.Hope this helps!
~ Answered on 2017-07-18 13:30:27