ASP.NET 2.0 or ASP.NET 1.1 is not displayed as a choice when viewing the Properties of my IIS Site.
If you installed the .NET Framework before Internet Information Services, you will need reinstall the ASP.NET Pointers. You can do this by following these instructions (you must be a local administrator to perform these actions):
- Open a command prompt window
- If you need to reinstall ASP.NET 1.1, type:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i
- If you need to reinstall ASP.NET 2.0, type:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i
- To uninstall ASP.NET 1.1, type:
%SYSTEMOOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe –u
- To uninstall ASP.NET 2.0, type:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –u
- Open the Internet Information Systems Manager Console. Go to “Web Services Extensions”. Make sure that both ASP.NET 1.1 and 2.0 are Allowed.
What ASP.NET Versions are required for my Smartertools product?
SmarterTicket 2.x – ASP.NET 1.1
SmarterMail 1.x, 2.x, 3.x – ASP.NET 1.1
SmarterMail 4.x, 5.x – ASP.NET 2.0
SmarterStats 2.x, 3.x – ASP.NET 1.1
SmarterStats 4.x - ASP.NET 2.0 (.NET 3.5 Framework must be installed)
SmarterTrack 3.x - ASP.NET 2.0 (.NET 3.5 Framework must be installed)
Will my SmarterTools product run on Windows 2003 64-bit?
All SmarterTools products have the capability of running in a Windows 2003 64-bit environment. However, they may require that IIS run in 32-bit compatibility mode.
If the product that you are running requires ASP.NET 1.1, you must run IIS in 32-bit compatibility mode. The .NET 1.1 Framework is not available in 64-bit.
To set IIS in 32-bit compatibility mode, run this from the command-line:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
To disable 32-bit compatibility mode, run this from the command-line:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Once, either of these scripts are executed, you will need to reinstall ASP.NET:
For ASP.NET 2.0, run:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i
For ASP.NET 1.1, run:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i
SmarterMail 4.x and 5.x require .NET 2.0. However, the .NET 2.0 Framework is available in 64-bit. If you are running IIS in 64-bit mode, SmarterMail will be able to run without any issues.
If you wish to run IIS in 32-bit mode, when you add the SmarterMail web interface to IIS, you will receive an error stating “Bad Data”, when trying to access the interface.
To resolve this issue, you have 3 options:
Option 1: Running SmarterMail v4.x and IIS in 64 bit mode
SmarterMail v4.x runs properly in Windows 2003 Server when IIS, ASP.NET 2.0, and SmarterMail are all running in 64 bit mode. If IIS is switched from 32 bit to 64 bit mode then all previously working sites that utilize ASP.NET 1.1 will stop working.
Option 2: SmarterMail v4.x running 64 bit and IIS running 32 bit
When the SmarterMail v4.x Service (mailservice.exe) is running in 64 bit mode, it is incompatible with IIS running in 32 bit mode.
During the installation process, SMarterMail 4.x checks the CPU to determine if the CPU is 32-bit or 64-bit. When this occurs, the installer will install the 64-bit or 32-bit of the .NET 2.0 Framework (depending on the CPU). The IIS Sites will then all be converted to 2.0, instead of 1.1. If any IIS Sites were using 1.1 before .NET 2.0 was installed, they will be set to 2.0, and thus may not operate correctly.
You will need to check your IIS configuration. Is it 32 or 64 bit mode? To do this, look at the metabase.xml file in the windows\system32\inetsrv\ directory. Look for Enable32BitAppOnWin64, if the value is set to 'True' then IIS is running in 32 bit mode, if it is 'False' then it is in 64 bit mode.
So, to resolve this issue SmarterMail v4.x MailService needs to be forced to run in 32 bit mode, please read the next paragraph before proceeding.
IMPORTANT NOTES: This article contains information about modifying the source code on your server. Modifying source code can be problematic and may have unforeseeable complications and negative interactions, up to and including data loss. Before attempting any such modification, it is vital to back up the entire system, plot a path of system recovery, and have a thorough understanding of system recovery methods. If you choose to modify source code, you do so at your own risk. The authors of this article and SmarterTools assume no liability or responsibility for any potential consequences resulting from this choice, nor should you interpret this article as a recommendation for your particular system or circumstance.”
We recommend that you follow the procedure below, in order to force the MailService.exe to run in 32 bit mode:
Uninstall ASP.NET 2.0 using Add/Remove Programs
Download and install ASP.NET 2.0 SDKs (Software Developers Kit), here is the link http://www.asp.net/downloads/essential/
At the command line type, navigate to the location of the corflag.exe file:
To enabled 32bit support:
corflags.exe <type complete path to mailservice.exe executable> /32BIT+
or
To disable 32bit support:
corflags.exe <type complete path to mailservice.exe executable> /32BIT-
For more information on the CorFlags Conversion Tool go to:
http:///
Option 3: Using SmarterMail’s Default web server with IIS in 32 bit mode and ASP.NET version Switcher.
The installation of SmarterMail v4.x by default installs ASP.NET 2.0. This will overwrite the existing ASP.NET 1.1 pointers with ASP.NET 2.0, thereby, the site stops working.
To resolve this issue you will need to run an application called ASPNETVersionSwitcher.exe. This will allow you to configure the ASP.NET version being utilized by each IIS site. Stop the SmarterMail IIS site and use the SmarterMail default web server which runs on port 9998. Next, create an IIS website for mail.example.com and then create an aspx redirector page that points to mail.example.com:9998.
How do I configure an IIS Site for my SmarterTools product?
SmarterMail 5.x:
http://help.smartertools.com/SmarterMail/v5/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterMail 4.x:
http://help.smartertools.com/SmarterMail/v4/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterMail 3.x:
http://help.smartertools.com/SmarterMail/v3/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterMail 2.x:
http://help.smartertools.com/SmarterMail/v2/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterMail 1.x:
http://help.smartertools.com/SmarterMail/v1/T2/4.htm
SmarterStats 4.x:
http://help.smartertools.com/SmarterStats/v4/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterStats 3.x:
http://help.smartertools.com/SmarterStats/v3/Topics/SystemAdmin/Installation/ConvertingToIIS.aspx
SmarterStats 2.x:
http://help.smartertools.com/SmarterStats/v2/T2/3.htm
SmarterTrack 3.x:
http://help.smartertools.com/SmarterTrack/v3/Topics/Installation/RunIISSite.aspx
SmarterTicket 2.x:
http://help.smartertools.com/SmarterTicket/v2/Topics/Admin/Installation/ConvertingToIIS.aspx
What is a hostheader?
A host header is used to administer multiple web sites if you have access to a limited number of IP Addresses. Each site in IIS can only be assigned a single IP and port (i.e., 192.168.1.1:80). To get around this limitation, you can assign a unique port to each site. This can get cumbersome. Customers will need to enter the port each time they wish to access the web interface. For example, if you set your SmarterMail site to port 8081, they would have to access: http://mail.example.com:8081. If you wish for your customers to only access http://mail.example.com/, you will have to use host headers. You can do this by assigning (as in the previous case), mail.example.com, as a host header.
The only other requirement is that the A record for mail.example.com, must be configured for the same IP that the IIS site is configured for.