You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.
Course Of The Month
6 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Running a 32 bit DLL product in Windows 2008 64 bit
Posted on 2009-03-30
I have built a (strongly named) .Net library that uses a 3rd party tool, pdf2image. This 3rd party tool is supplied as a old type (pre-com) windows dll (something I almost understand). Please see the sample .Net declaration and call in the Code section. This all works fine on a Windows 2003 32 bit machine.
When I tried to move this library to a Window 2008 64 bit server, the call to 3rd party tool fails, almost certainly because it is a 32 bit dll (the .Net code itself runs fine until it gets to this call). I've heard of a 32 bit compatability mode on 64 bit machines, but all of the discussions focus on running 32 bit programs (EXEs) rather than accessing legacy libraries (DLLs).
Is there any way to make this 3rd party tool dll work on a 64 bit machine?
When I tried to move this library to a Window 2008 64 bit server, the call to 3rd party tool fails, almost certainly because it is a 32 bit dll (the .Net code itself runs fine until it gets to this call). I've heard of a 32 bit compatability mode on 64 bit machines, but all of the discussions focus on running 32 bit programs (EXEs) rather than accessing legacy libraries (DLLs).
Is there any way to make this 3rd party tool dll work on a 64 bit machine?
[DllImport(@"C:\bin\pdf2image.dll", CharSet = CharSet.Auto)]
static extern uint PDFToImageConverter(
[MarshalAs(UnmanagedType.LPStr)] string FileName,
[MarshalAs(UnmanagedType.LPStr)] string OutputName,
IntPtr UserPassword, IntPtr OwnPassword,
int xresolution, int yresolution, int bitcount,
int compression, int quality, int grayscale,
int multipage, int firstPage, int lastPage);
result = PDFToImageConverter(FileIn, _FileOut, UserPassword, OwnPassword, 300, 300, 1,
COMPRESSION_LZW, 70, FALSE, TRUE, -1, -1);
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
4 Comments
There is an easy fix.... just recompile your application to target the "x86" CPU rather than the default of "AnyCPU". That will force your application to run in the 32-bit mode on a 64-bit (which in turn, allows the 32-bit 3rd-party DLL to load).
From the menu, select Project, then Properties. Select the Build vertical tab, and change the "Platform Target" to x86
From the menu, select Project, then Properties. Select the Build vertical tab, and change the "Platform Target" to x86
Thanks for the great response! I'm probably almost there. One thing that I should have mentioned is that my .Net library (ResultReports.dll) that uses the 3rd party library (pdf2image.dll), is in turn used by an ASP.Net application.
I can recompile my library, ResultReports, to target x86 and then publish it to the GAC on all of our 32 bit web servers and it works fine. When I publish the recomplied library to our new Windows Server 2008 64 bit web server, the ASP.Net web application throws this error:
Could not load file or assembly 'ResultReports, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c92e9103e25
Note: the published web application was simply copied to the new 64 bit server ahd has worked OK except for this problem. It's built in Visual Studio 2005 and targets the Framework v2.0
Apparently, ASP.Net web applications on a 64 bit machine don't like assemblies in the GAC that target x86. Is there a was around this? If not, I may just run IIS in a virtual x86 server hosted by the 64 bit server.
Thanks again.
I can recompile my library, ResultReports, to target x86 and then publish it to the GAC on all of our 32 bit web servers and it works fine. When I publish the recomplied library to our new Windows Server 2008 64 bit web server, the ASP.Net web application throws this error:
Could not load file or assembly 'ResultReports, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c92e9103e25
Note: the published web application was simply copied to the new 64 bit server ahd has worked OK except for this problem. It's built in Visual Studio 2005 and targets the Framework v2.0
Apparently, ASP.Net web applications on a 64 bit machine don't like assemblies in the GAC that target x86. Is there a was around this? If not, I may just run IIS in a virtual x86 server hosted by the 64 bit server.
Thanks again.
That's correct... in no circumstances can you configure a 64-bit applicaiton to run with a 32-bit DLL... it's just not gonna happen
So, again, the solution is fairly easy... you just configure IIS to run the the "32-bit emulation mode". Windows 2008 allows you configure the 32-bit emulation separately for each "application pool". Note: For the previous version (ie. Windows Server 2003) the conversion to the the 32-bit emulation mode was an "all or nothing" proposition... not so with Windows Server 2008. That means you won't have to convert all of you web applications to 32-bit... you can just convert this one.
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
So, again, the solution is fairly easy... you just configure IIS to run the the "32-bit emulation mode". Windows 2008 allows you configure the 32-bit emulation separately for each "application pool". Note: For the previous version (ie. Windows Server 2003) the conversion to the the 32-bit emulation mode was an "all or nothing" proposition... not so with Windows Server 2008. That means you won't have to convert all of you web applications to 32-bit... you can just convert this one.
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Configuring Remote Assistance for use with SCCM
This article helps those who get the 0xc004d307 error when trying to rearm (reset the license) Office 2013 in a Virtual Desktop Infrastructure (VDI) and/or those trying to prep the master image for Microsoft Key Management (KMS) activation. (i.e.- C…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
- Microsoft Legacy OS
- Windows 10
- Windows 8
- Windows OS
- Windows 7
- Windows Vista, Windows XP, Windows 2000
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7.
Start the SARDU utility:
Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
Suggested Courses
Course of the Month6 days, 15 hours left to enroll
Earn Certification
Managing Projects with Microsoft Project 2013 (Exam 74-343)
$49.00$44.10
724 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.