During installation the following error message is displayed: "Failed to enable ASP.NET web extensions"

Article:TECH90073  |  Created: 2008-01-12  |  Updated: 2013-10-30  |  Article URL http://www.symantec.com/docs/TECH90073
Article Type
Technical Solution


Subject

Issue



The error message "Failed to enable ASP.NET web extensions. Installation will not continue" appears when you install Symantec Mail Security for Microsoft Exchange (SMSMSE).  The installer does not continue and SMSMSE is not installed.

 


Error




 


Environment




 


Cause



There are various causes and solutions listed below.

 


Solution



Use one of the following solutions:

 

In Windows Server 2008, enable IIS 6 Scripting Tools

1. Open Server Manager.
2. Expand Roles.
3. Expand Web Server (IIS).
4. Click Add Role Services.
5. Check Management Tools|IIS 6 Compatibility|IIS 6 Scripting Tools.
7. Click Install.

Ensure ASP.NET have been added under Role Services

Ensuring all the above ASP.NET and .NET requirements are in place.

NOTE:  As of SMSMSE 6.5.7 and higher the installer checks the ASP.NET pre-requisites at the beginning of the installation.  The installer does not proceed to this error message if ASP.NET is not already installed.

In Windows Server 2003, make sure that ASP.NET v2.0.50727 is allowed in Internet Information Services (IIS) Manager

1. Open IIS Manager.
2.
Expand the Exchange server.
3. Click the Web Service Extensions folder.
4. In the list on the right make sure that ASP.NET v2.0.50727 is set to Allowed.
5. If ASP.NET is not listed please contact Microsoft for assistance.

Ensure iisext.vbs can be run

  • Make sure that the following Microsoft files are in the <Windows Dir>\system32\ folder:

    • iisext.vbs
    • iisschlp.wsc
    • cscript.exe
      If the files are not in the system 32 folder, please contact Microsoft for further assistance.
  •  Run this command to determine what extensions exist in IIS 6. 

<Windows Dir>\system32\cscript.exe <Windows Dir>\system32\iisext.vbs /ListExt

The response should be similar to this:

Connecting to server ...Done
HTTPODBC
SSINC
WEBDAV
ASP.NET v2.0.50727
MSExchangeClienetAccess
MSEXCHANGE
SMSMSE
BITSEXTS
ASP

The list does not need to match exactly the example above, but this command should return a list of some extensions.
The installer runs this command as a test to register the ASP.NET web extensions with IIS. If this script is not functioning
properly, this command reveals that issue. If an error is returned when attempting to run this command, please contact
Microsoft for further assistance troubleshooting why iisext.vbs is not functioning as expected.

 

  • If the iisext.vbs command shows the following error message: 

Could not create an instance of the IIsScriptHelper object.
Please, check if the Microsoft.IIsScriptHelper is registered.

Perform the following to register the IIsScriptHelper:

1. Open a windows command prompt.
2. CD to directory <windows>\system32.
3. Run the following command: regsvr32 IisScHlp.wsc.

  • On Windows 2008 R2, if the iisext.vbs command shows the following:

                     Connecting to server ...Done

                     ASP.NET v4.0.30319

          This means ASP.NET v4.0 is the only version installed. Please download and install ASP.NET v3.5 as well.

Ensure install of Mail Security for Exchange is being started from setup.exe.  Not from the .msi in the x86 or x64 folders.

Installing from setup.exe will detect the appropriate Operating System platform and install the correct version of Mail Security.

NOTE:  As of SMSMSE 6.5.7 the installer checks the pre-requisite of ASP.NET.  If the MSI is run instead of the setup.exe then the installer reports the following required item is missing:

ASP.NET Web Extension 2.0

Therefore this error is not reported with 6.5.7 and higher.

 

Additional Troubleshooting

The following command line is being executed when this error message appears in the installer:

<Windows Dir>\system32\iisext.vbs /enext "ASP.NET v2.0.50727"

Running this from the command line may show additional information as to the source of the trouble. 

If this command works it is necessary to obtain a Microsoft Process Monitor log to determine what is going on in the sub process.

 


Attachments

Web_Server_Features_Installed.jpg (130 kBytes)

Supplemental Materials

SourceETrack
Value2378133

SourceETrack
Value2274962

SourceETrack
Value2771028


Legacy ID



2008081210523154


Article URL http://www.symantec.com/docs/TECH90073


Terms of use for this information are found in Legal Notices