ASP not working...

[DXD]

Here we go again:

http://www.chris.ward.name/ASPTEST.ASP

the file is there but I get a 404 error.

Why is asp not working on this website what do I need to look at? .NET works for my main site www.dynamicbydesign.com

really not sure what to look at.

[KyleMulligan]

Looks like you don't have ASP enabled for the site. Check in Helm to make sure the domain has ASP resources available and enabled.

[DXD]

It was checked as being installed. So I unchecked it. Save. Rechecked it. Save and now it works.

It seems that I have to do this with all my new domains/sites

although it's ON by default it's not really ON and it has to be unchecked and rechecked for all of those items (ASP, ASP.NET, PHP, PERL)

Any ideas?

[FabioCalegari]

Hi!

I have the same problem in my site
see: http://www.simova.com.br/teste.asp - don't show the asp :(

The paths are OK (C:\WINNT\etc...)..

>>
It was checked as being installed.
So I unchecked it. Save. Rechecked it. Save and now it works.
<<
Don't works for me... :(

Any idea?

Thank's
Fabio
PS: sorry my poor english - I'm brazilian

[Cerixus]

I'm having the same issue. I also tried the fix above with no luck. ASP.NET v1.1... and Active Server Pages are both set to "Allow" in my web service extensions.

[DXD]

Try this below:

Registering ASP.NET on IIS after installing the .NET Framework
If you install the .NET Framework on a system that has IIS already installed, IIS is automatically configured to handle requests to ASP.NET pages, and to redirect the execution to the ASP.NET runtime. However, it may happen that you installed the framework on a Windows 2000 Professional system where IIS was not already present, and just later decided to add IIS. Registering ASP.NET on IIS is not just a matter of associating the various .aspx, .asmx, .axd, .ashx and the other ASP.NET extensions to the aspnet_isapi.dll ISAPI, more has to be done to create the ASP.NET account and to set it for ASP.NET requests, register the ISAPI itself and other stuff. Doing all this manually can be a difficult operation, and requires a good understanding of many details. Fortunately there is an utility, shipped with the .NET Framework but not documented, that can take care of these configuration chores for you. The utility is aspnet_regiis.exe, it is located under %WindowsDir%\Microsoft.NET\Framework\vx.y.zzzz\ and you should call it with the -i parameter: aspnet_regiis.exe -i

[Cerixus]

I had this same problem. Check the "Application Extensions" in the "Application Configuration" area of the domain in the IIS manager. Most of my extensions point to C:\Windows\system32... which does NOT exist as Windows is installed to c:\winnt\. The odd thing is, the "Default Website" points to the correct folder, but any new domains do not. I was under the impression new domains were created using the default website as a template, but apparently that's not the case. ANYWAY, try changing the path to asp_isapi.dll to the correct folder and you should be good to go!

[webguy]

I realize this is an extremely old post, considering technology, but I just had my 2000 server crash and it was provisioned as a 2003 due to end of life on 2000. I am having the same problem, where Helm creates the site and when it does so it sets the Application Configuration paths to C:\Windows\etc... instead of C:\WINNT\etc... Is there a fix for this? We only have about 80 some odd domains to add, but it appears this is going to be an ongoing issue when my customers add new domains. Highly unacceptable if this is the case. :(

[KyleMulligan]

Change the path in the Helm IIS service(s) and then run the restore tool on your sites.