Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Failed to enable ASP.NET web extensions. Installation will not continue - Mail Security 6

Updated: 21 May 2010 | 12 comments
DavidTj's picture
0 0 Votes
Login to vote
Hi all...

I've recently purchased Mail Security 6.0.3.201 for the company I am working for and attempting to install it on my Windows Server 2003 64 bit + Exchange 2007 server.

However, after confirming all options and proceeding with the install, a DOS window quickly pops up then out (too quick to see what's displayed), and an error dialog box appears displaying...

"Failed to enable ASP.NET web extensions. Installation will not continue."

and the installer Finishes.

It appears that this error message is unique as I haven't been able to find any articles anywhere.

I've made sure that Active Server pages, ASP.NET 2.050727 are set to allowed in IIS Manager.  No joy!
Here is the content of the SMSMSE60_Setup.log file...
----------
SMSMSE Install Started: Wed Oct 03 07:36:38 2007
fnPreCheckOSAndExchange
Installer is 64 bit
fnCheckExchangeTransportServiceInstalled
Installer is 64 bit
Exchange Transport Service Is Installed
Exchange Transport Service Is Running
fnPreCheckIISInstalled
IIS Is Installed and Running
SetDefaultNotificationEmailAddress
fnStubGetProcessCount
fnGetSystemProperty
hrGetDomainDN Successful
fnGetSystemProperty Current Domain is XXX
MSi Property CURRENT_DOMAIN=XXX
fnGetReinstallProductMsiProperties
unable to determine previous installation INSTALLDIR for product
fnCheckForPreviousVersion
previousConsoleInstalled
invokeSymantecCmafUpgradeUtility
C:\TEMP\{FADF1E3A-A727-4F49-B50D-7D33A61CAC64}\Symantec.Cmaf.Upgrade.exe  v smsmse 60 s
Symantec.Cmaf.Upgrade.exe exec success, return code : 0
invoke previous console check succeeded : 0
No previous version of console installed
fnVerifyPortNumber
fnMsiGetFeatureSelected
fnMsiGetFeatureSelected: Server feature selected
fnMsiGetFeatureSelected
fnMsiGetFeatureSelected: Server feature selected
fnVerifySMSMSEPreRequisiteComponents
verifySMSMSEPreRequisiteComponents
adobeReaderVersionInstalled
Failed Adobe 8.0 Reader requirement is not met on the target system
dotNetFxVersionInstalled
using dot net framework directory from existing MSI Property
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
MDACVersionInstalled
directXVersionInstalled
All prerequisites are met for Server install
fnReCheckPortNumber
fnResolveEmailAddress
Administrator@domain.com.au
fnVerifySMSMSESMTPServerHostReachable
Able to reach the Exchange Web Services Address
localhost
Installer is 64 bit
fnInstall_MSXML6
MSXML6 is already present, No need to install
----------

Is there anyone out there that could help me?  I've submitted a case with Symantec Tech Support but they have had to escalate it to a senior engineer!



Message Edited by DavidTj on 10-04-2007 05:36 PM

Message Edited by DavidTj on 10-04-2007 05:36 PM

Discussion Filed Under:

Comments

Kevin.Purcell's picture
26
Oct
2007
0 Votes 0
Login to vote

I had this same problem. It took 4 calls to symantec (and we have platnium support). I got a person that pointed me at this KB article and then I wound up stumbling onto the real solution by accident.

Try this.

Navigate to c:\windows\inf\wsh.inf

Right click the wsh.inf file and select install. This will reinstall the windows scripting host and associate itself with .vbs. After this try to run the symantec installer. It should work for you now!

Let me know if you have success.

Sunil's picture
25
Nov
2007
0 Votes 0
Login to vote

Hi Kevin,

I tried solution which you told to try but not positive success, Still i am getting same error which is mentioned by David T. in the top.

Could you tell me what all services need to be running or stopped during Symantec Mail security installation.

lkeller's picture
11
Dec
2007
0 Votes 0
Login to vote

I had the same problem, and there isnt any information on the web directly relating to this. However, in my case, it came down to it really being an ASP issue. Run through this article and try to install again.

http://support.microsoft.com/default.aspx?scid=kb;...

Let me know if that helps!

Thanks,
Lucas Keller

nambesal's picture
14
Dec
2007
0 Votes 0
Login to vote

I'm having the same issue.   I've tried all the suggestions already posted and am still getting the same ASP.NET warning.   Please help.
Jin Zhao's picture
06
Jun
2008
0 Votes 0
Login to vote

May you have to install all feature of IIS 7.
Since SMSMSE used mostly feature of IIS7.
 
for instance, IIS6 scripting tools.
Marc S.'s picture
11
Jun
2008
3 Votes +3
Login to vote

On Windows Server 2008 x64, Exchange 2007 SP1 and SMSE 6.06.235 I had the same problem.
 
Solution: You need to add the IIS 6 Scripting Tools Role Service under IIS 6 Management Compatibility
LanceSalkind's picture
11
Jun
2008
0 Votes 0
Login to vote

Hello Marc,
 
Since I loaded the FTP upgrade I do not have the IIS 6 Management Compatibility option.
 
Could you please detail the steps to execute the fix.
 
Thanks!
 
Lance
Messen's picture
28
Jul
2008
0 Votes 0
Login to vote

Thanks a lot. Worked for me with the IIS 6 compatibilty :-)

 

 

Marc S.'s picture
28
Jul
2008
0 Votes 0
Login to vote

Lance,

 

The IIS 6 compatibility option is part of the Windows Operating system, not a setting in Symantec Mail Security.

In Windows 2008 you have server roles one of which leads to installing IIS 7.

But SMS is not compatible with IIS 7 as is, you have to add the IIS 6 backwards compatibility option. 

That way SMS can use IIS 6 scripting to configure the IIS server to create the SMS website.

Fullor's picture
29
Aug
2008
0 Votes 0
Login to vote

Also worked for me with the IIS 6 compatibilty :-)

Jay327's picture
06
Oct
2008
0 Votes 0
Login to vote

Marc S. wrote:

On Windows Server 2008 x64, Exchange 2007 SP1 and SMSE 6.06.235 I had the same problem.
Solution: You need to add the IIS 6 Scripting Tools Role Service under IIS 6 Management Compatibility

 

Thanks! This worked for me.

DerekAndrews's picture
22
Jul
2009
0 Votes 0
Login to vote

IIS compat

The IIS compatability worked perfectly for us, too.  Thank you!