Classic ASP invokes dll - works in 32 bit OS but fails in 64 bit OS with IIS 7.5 - asp-classic

I am working on a Classic ASP application. It used dlls to upload and download files to web server.
FunctionUpload.dll is registered using the regsvr32.exe command. It works fine in Windows 2003 server , 32 bit OS with IIS 6.
Now the server is upgraded to Windows 2008 64 bit OS with IIS 7.5. I registered the dll using regsvr32.exe command in 64 bit OS. ( regsvr32.exe in C:\Windows\SysWOW64 folder using Admin login)
When the ASP code tried to create an object of that dll it fails.
Set download = Server.CreateObject("FunctionUpload.File")
Please let me know what steps need to be done to access the dll from ASP code on a server with windows 2008 64 bit OS with IIS 7.5?
How to check if the dll is registered properly on a 64 bit OS?
Should I make any changes in the IIS 7.5 settings to invoke that dll?
Thanks
Ashok

you have to enable 32-bit applications in your iis under your application pool

Related

Cannot get ADO connection working on a classic ASP website running in IIS Express on Windows 7 64 bit

I have a legacy classic ASP website that I need to do some maintenance work on. My development machine is running Windows 7 64 bit, Visual Studio 2012 and IIS Express 8.0.
The ASP app is backed by a Microsoft Access database.
The website runs fine until it tries to establish a connection to the database, where it fails with the following:
0x800a0e7a - ADODB.Connection: Provider cannot be found. It may not be
properly installed.
If the ASP process is running as 64-bit and it is trying to use the Jet database engine then that won't work because there is no 64-bit version of Jet. If that is the case then you can either
install the 64-bit version of the Access Database Engine (ACE), available here, and tweak the connection parameters as required, or
get the ASP process to run as 32-bit
I had the same problem you mention in a follow up comment.
I tried to install the 64 bit version, but I could not because I have
Office 2010 32 bit installed.
You can force the 64 bit version of the Access Database Engine (ACE) from here to install with the 'passive' switch:
AccessDatabaseEngine_x64.exe /passive

Why is IIS 6 / Windows 2003, forcing a Website to use .NET 2.0?

I have a Windows 2003 Server 64bit running IIS 6.0.
When I set the server up, I noticed that the 'ASP.NET' tab has been removed from the 'Web Sites' property in IIS Manager.
Now every website runs on .NET 2.0 and I need to change them to run on .NET 4.0.
I have ASP.NET 4 (32bit) enabled in the 'Web Service Extension' (the only other options ASP.NET versions 2 in both 32 and 64 bit modes).
I can confirm that in C:\Windows\Microsoft.net folder, there is both 'WOW' and 32bit .Net installation.
This is a production server with many websites and I'm afraid to run some IISReg scripts to put back the 'ASP.NET' tab.
When I try to the .Net 4 targeted website, I get an error:
Unrecognized configuration section system.web.extensions
The version information shows .Net 2.0
So what can I do?
Thanks!
As I indicated in my 'Comments' above, I had to run IIS in 32bit mode in a 64 bit system to target a certain web application. The background information for that can be see here:
http://dillieodigital.wordpress.com/2010/10/07/windows-server-2003-64bit-iis-6-32bit-asp-net-4-framework-and-targeting/
That resulted in running all websites in 32 bit mode with .NET 2.0. To get the new web application to run in .NET 4, I followed instructions, per:
http://mlichtenberg.wordpress.com/tag/iis6-asp-net/
Problem solved!
FYI.
Thanks.

Skipping Strong Name Assembly for Windows 7 IIS 7.5 still give an error "Couldn't be Verified"

Environment Windows 7 IIS7.5 64 bit
I have an ASP.NET website traget framework 4.0 and I have a dll whose source code isn't with me and it's already a delayed signed assembly. Now I have added that assembly for skipping strong name verification using Sn -Vr *, Token. It got complied in VS2010 and If I press F5 it runs sucessfully. But I would need to add as a website under IIS to be used by other application as its a webservice. So when I am adding it as a website under IIS and running it shows the same error "Strong name signatuer could not be verified." but it's working from VS2010 instead but not from IIS why?
I tried doing the same with a Windows 7 32 bit IIS 7.5 and is working, so it is some thing to do with 64 bit OS? Please help.

Could not load file or assembly while running in IIS 7.0 on a 64 bit OS

I am trying to host a web application in a Windows 2008R2 server on IIS7.0 which is 64 bit. I had been running my application on IIS 5.1 XP machine which is 32 bit.
I have my DLLs built with the 'x86' option and also I have enabled "Enable 32 bit applications" to True and also set the managed pipeline to Classic in the application pool of my webservice.
Now I get the following message:
Could not load file or assembly 'Microsoft.Web.Services2,
Version=2.0.1.0, Culture=neutral, PublicKeyToken=[some value]' or one of its dependencies. The system cannot find the file
specified.
Can someone tell me why this happens ?
Just install Microsoft Web Services 2.0 : http://www.microsoft.com/downloads/details.aspx?familyid=1ba1f631-c3e7-420a-bc1e-ef18bab66122&displaylang=en
Can you set your DLLs to build with the AnyCPU option and report what happens?

InstallShield 2010 - 1603 Fatal Error [Windows Installer] (Windows 7 Only)

I created an MSI InstalScript Project where i deploy a web based (ASP.NET) precompiled project copying the files during installation in the \inetpub\wwwroot\projectnamefolder, creating an AppPool and the virtual dir of course in the IIS. The setup works great in windows
XP Pro (SP3 i used). But soon as i try in Windows 7 (tried Ultimate and Home Premium) i get
a -1603 Fatal Error during installation...Windows Installer Help (MSI.chm) or MSDN for more info....
Dying to fix this...
[Edit] I think error occurs when trying to create the Application in the IIS.
[FIXED] Enable 32 Bit Apllications needs to be true when creating Application Pools through InstallShield in a 64 bit OS!
No permission. See this MS support article
So you have write access to the directory but does the account have permissions to modify the IIS settings?

Resources