Switch ASP.Net with 32 bits

Today, when I am trying to check the VPS client server and getting error of services unavailable all of the time.

As I do not know what is being installed earlier, hence I am checking it’s PHP and ASP.Net version. Finally, it is found out the problem came from the ASP.Net.

As the VPS is running Hyper-V with VPS, hence a 64 bits OS used. Hence changing the ASP.Net to 32 bits could get it fixed.

By changing the ASP.Net from 64 bits to 32 bits, you may refer to the step as below.
1. Open a command prompt.
2. Enable the 32 bits environment.

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

3. Reapply the ASP.Net.

%SYSTEMROOT%\Microsoft.NET\Framework64\vx.xxx\aspnet_regiis.exe -i

where the x.xxx version is your .Net Framework version.

Switch from 64 bits to 32 bits in Windows Server 2003

People always discuss if the apps could support in 64 bits server since the 64 bits server arrive to the market and you might not know that the Windows server ASP and ASP.Net could be turn from 64 bits to 32 bits.

To convert your IIS to be used 32 bits apps, open a command prompt and run the following command.
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

So, now your 64 bits server(IIS) could run 32 bits application without any issue. And you will now need to register the 32 bits .Net Framework as 32 bits framework is not installed by default.
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

Well done, you have done for all.

Using ASP.Net MVC with different IIS

ASP.Net MVC is ASP.Net Modeling view controller where used to manage information and notify obeservers when that information changes.

To setting up ASP.Net MVC, you could setting it through IIS 6.0 or IIS 7.x.

  • IIS 7.x (integrated mode) – No special setting needed.
  • IIS 7.x (classic mode) – some setting needed to apply.
  • IIS 6.x or below – some setting needed to apply.

The setting needed as mentioned above actually is referring to creating the wildcard script map.

If you don’t want to use the URL mapping, you may actually ignore the setting as said, however if you want to use the mapping setting, you may refer as detail below.

IIS 7.0 with classic mode:

1.  Open IIS 7.0, select your application in the Connections window.
2. Make sure that the Features view is selected.
3. Double-click the Handler Mappings button.
4. Click the Add Wildcard Script Map link.

5. Enter the path to the aspnet_isapi.dll file (You can copy this path from the PageHandlerFactory script map)
6. Enter the name MVC.
7. Click the OK button.

IIS 6.0 or below:

1.  Right-click a website and select Properties.
2. Select the Home Directory tab.
3. Click the Configuration button.
4. Select the Mappings tab.
5. Click the Insert button.

6. Paste the path to the aspnet_isapi.dll into the Executable field (you can copy this path from the script map for .aspx files).
7. Uncheck the checkbox labeled Verify that file exists.
8. Click the OK button.