I am having issues running the chart control on our 64 bit machine. I get the following error...
Could not load file or assembly 'AspnetChart' or one of its dependencies. An attempt was made to load a program with an incorrect format.
The machine I am running this on is a Windows Server 2003 Enterprise x64 Edition SP2 Intel(R) Xeon(R) CPU E5405 # 2.00 GHz w/ 4.00 GB RAM
The chart control works fine on our 32 bit Windows XP Professional SP3 and Windows Server 2003 Standard Edition SP2 machines, but not when deployed to the 64 bit machine.
I tried to change the Platform target to x86, but that didn't seem to help. I also tried signing the dll and putting it in the GAC, but that didn't help.
Any thoughts, suggestions?
It sounds to me like you have a 32 bit DLL. In IIS 7 it's possible to run 32-bit and 64-bit processes simultaneously. But in IIS 6 you can only do one or the other. For running 32-bit applications on IIS 6 (64-bit windows) check out this Microsoft article.
Related
My installer works fine with Windows 7 32Bit but if run on a Windows8 64 Computer I get an out of memory error during the installation process.
The Windows 7 and the Windows 8 output are created fine with Inno Setup 5.5.5
Sorry forgot to cancel this.
I discovered my brand new Windows 8.1 computer with 32GB of ram was locked to 4GB of useable ram. I was getting out of memory errors. I have reconfigured the computer and now all is well.
How can I run an Application Pool in 64bit mode on Windows Server 2008 R2 x64 with IIS7 Installed ?
You do not tell it to run in 64 bit mode, you only tell it if you want to run it in 32 bit mode. By default it should run in 64 bit.
I have a 64 bit CHILKAT CRYPT assembly (for .NET 4.0). when I run my application in IIS 6.0 in Windows Server 2003 (64 bit) I got an error that the assembly is not found. on the other hand, in my local machine I have a 32 bit assembly and Windows7 32 bit and it works fine.
What should I do to to overcome this error and what are the causes?
The main problem I found is that the web application is built for platform x86 and deployed to x64 machine on which the machine does not allow 32 bit programs to run.
in this case the error that indicates that the assembly is not found is not correct. its simply not compatible with x64 machine.
I found that the following steps solved the problem:
Add the 64 bit assembly to web application project (visual studio 2010)
Select x64 for target platform from the configuration manager in visual studio
Build the solution and deploy it
This steps really fixed my problem.
I am about to upgrade my pc, and operating system at the same time. I was wondering what version of Windows 7 to get pre-installed, given that I want to do some ASP.NET development using Visual Studio.
Specifically :
Will all versions of Windows 7 run an IIS server & be suitable for ASP.NET development ?
Are all good for running SQL Server etc ?
Will Windows 7 have any probs running old versions of Visual Studio (Ie. 2003 & 2005 versions).
Are there any other things I need to consider ?
I'm probably going for the 32 bit version of Windows 7.
Thanks in advance,
Bazza
I would suggest you get the 64-bit version: there's really no reason to be running a 32-bit operating system in this day and age (unless you have some esoteric hardware that doesn't have 64-bit drivers, but that's exeedingly rare: especially on Windows 7).
I think IIS 7.5 is included in Home Premium, but I think the Professional SKU is probably the best bang-for-buck version. You don't actually need IIS for ASP.NET work anyway, the development server that's included with Visual Studio is usually the best option anyway (it doesn't require Administrator privileges to debug).
Other than that, they'll all run SQL Server fine, and I see no reason why older versions of Visual Studio won't run, either (there may be issues with UAC, but nothing too dramatic for day-to-day use).
We want to switch a web server from Windows 2003 to Windows 2003 Enterprise (64 bits) to use 8GB of RAM. Will IIS 6.0 and an ASPNET 1.1 application be able to benefit from the change?
Since ASP.Net 1.1 has no x64 support, you are limited to running IIS 6 using 32 bit worker processes. The /3GB switch doesn't do anything on x64, but x64 natively gives 32bit processes 4 GB instead of 2GB, so you will have more memory available for your worker proces.
You will need to set the AppPools to 32 bit:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
You could consider tweaking the ASP.net memory from 60% of the application to 80%, which we've had some success.
<system.web>
<processModel memoryLimit="80" />
</system.web>
This can stress the app pool when you get up into the 1.2GB to 1.6 GB range.
Other things to consider is that most ASP.Net 1.1 applications have no issues when run in a 2.0 application pool, allowing you to easily convert your 1.1 32 bit application to a 2.0 64 bit application. This doesn't require any recompilation, just change the app pool to 2.0, then switch to x64 using the above ADSUTIL.VBS script (set to 0 rather than 1).
My understanding is that there was a virtual address space limitation of 3 GB in ASP.NET 1.1, and that it was never made 64 bit compatible, though 2.0 was.
You can get IIS 6.0 to run 32 bit (i.e. ASP.NET 1.1) on the 64 OS, but it will be in a 32 bit mode (along with anything else hosted, including ASP.NET 2.0 sites).
Microsoft article on switching between 32 bit and 64 bit
The memory limit is 2GB unless you use the /3GB switch on the process which will use 1GB of the kernel space for the process itself. The only way to go beyond 3GB with IIS is to run the 64-bit version.