You can refer to Appendix A in the MessageStats Quick Start guide or below are the same steps in the guide.
Fixing Microsoft .NET Configuration Issues
MessageStats Reports require that, at minimum, Microsoft .Net Framework 2.0 be installed on the server on which the web-based reports are hosted. If you have problems accessing MessageStats Reports, you can check the following settings that affect ASP Active Server Page (ASP) configuration. To check if Active Server Pages are enabled (Windows Server 2003)
1. Open the IIS Manager snap-in and select Web Service Extensions.
2. Verify that the Active Server Pages setting is set to Allowed.
3. Restart the IIS service.
4. Check if you can access the MessageStats Reports.
For Windows Server 2008, IIS 7.0 is required. Also the Web Server (IIS) role must be installed and
certain role services must be enabled. See “IIS Role Services on Windows Server 2008” on page 16 for
more information.
Installing IIS After Service Pack Can Break ASP
If you install Internet Information Services (IIS) after a Windows Server 2003 Service Pack has been
installed, IIS may fail to serve Active Service Pages (ASP). For example, you might see one of the
following error messages:
• Service Unavailable
• HTTP error 401.2
• Page cannot be displayed
This problem is caused by there being a mix of IIS files installed, both Windows Server 2003 release files
and Windows Server 2003 Service Pack files (either Service Pack 1 or Service Pack 2).
To identify the problem, check the version number properties for the Asp.dll file. If the version is
6.0.3790.0, the file is the release version but should be the service pack version.
The solution for this issue is to reinstall the Windows Server 2003 Service Pack.
Repairing IIS Mappings for ASP.NET
In some Microsoft environments, you may encounter a configuration issue with Microsoft .NET which can prevent MessageStats from reporting information correctly. The error indicates that Microsoft .NET Framework version 2.0 must be installed on the IIS server that hosts MessageStats Reports, and that Microsoft ASP.NET must be enabled on the virtual directory that contains MessageStats Reports.
If you are sure that the Microsoft .NET Framework is installed, and ASP.NET is enabled you may need to repair the IIS mappings for ASP.NET. The following procedure is based on the Microsoft Knowledge Base article 306005. Use the procedure to configure Microsoft ASP.NET. Similar issues can arise with Windows 2000 Server and Windows XP. In both cases, the solution is to reinstall the service pack after IIS has been installed.
To fix configuration mappings for ASP.NET
1. Run the Aspnet_regiis.exe utility:
a) Click Start and select Run.
b) In the Open text box, type cmd and click OK.
c) Navigate to the .NET Framework directory. (%windir%\Microsoft.NET\Framework\version\)
For example, at the command prompt, type the following:
CD /D "%windir%\Microsoft.NET\Framework\v2.0.50727"
d) Type the following command: aspnet_regiis.exe -i
e) Press ENTER.
2. Restart the IIS Service:
a) Click Start and select Run.
b) Type iisreset and press ENTER.
If Repairing the IIS Mappings for ASP.NET Fails
If you follow the procedure to repair the IIS mappings and you still see the error, the cause might be
that the Network Service is not granted the correct permission to write to the IIS metabase.
To grant permissions to the Network Service to write to the IIS metabase
1. Click Start and select Run.
2. In the Open text box, type cmd and click OK.
3. Navigate to the .NET Framework directory. (%windir%\Microsoft.NET\Framework\version\)
For example, at the command prompt, type the following:
CD /D "%windir%\Microsoft.NET\Framework\v2.0.50727"
4. Type the following command: aspnet_regiis.exe -ga “nt authority\network service”
The “-ga” option grants the specified user or group access to the IIS metabase and other directories that
are used by ASP.NET.
In this path, the version represents the .NET Framework directory version that is installed on the
server. Replace the placeholder in the example with an actual version number.
Running Reports on 64-Bit Operating Systems on Windows Server 2003
MessageStats Reports can be installed on 64-bit operating systems but, on Windows Server 2003, IIS must be reconfigured to allow MessageStats Reports to operate correctly. On 64-bit operating systems, you must reconfigure IIS to run in 32-bit mode. For instructions on how to configure IIS to run either the 32-bit version of ASP.NET, see the Microsoft Knowledgebase Article 894435 (
http://support.microsoft.com/?id=894435).
This procedure can cause application compatibility issues with other web applications installed on the same IIS Web Server so it is recommended that MessageStats Reports be run only on servers without other web applications. For Windows Server 2008 64-bit operating systems, you do not need to manually reconfigure IIS since
Windows automatically detects and configures IIS to run in 32-bit mode for MessageStats Reports.