You may have come across this error:
Active Server Pages error 'ASP 0201' Invalid Default Script The default script language specified for this application is invalid. or Active Server Pages error 'ASP 0129' Unknown scripting language The scripting language '<lang>' is not found on the server. or HTTP/1.1 Invalid Default Script Language |
First, make sure that the page you're trying to load doesn't have a typo, e.g. <% @language=VBSkirt %>.
You can start by the helpful advice in
KB #296626. Make sure your default scripting language is set to a valid option; most commonly, this is VBScript, but could be JScript or other languages. (I have read at least one suggestion that this be in UPPER CASE.)
If you are going to change the default scripting language, make sure *everyone* involved with the server knows this change is going to take place!
Several people have suggested an IISRESET, re-registering asp.dll/scrrun.dll, adding IUSR_MachineName to the Administrators group, dropping and re-creating the application, installing the latest scripting engines from
Microsoft Script Downloads, rebooting the machine — some gave up and rebuilt their machines from scratch. Here is what worked for me, as this happened to me recently when I added R2 to a Windows 2003 SP1 machine. After nothing else that I found on the web worked, I tried the suggestion that didn't make any sense. I went into IIS Manager, right-clicked the web site, and on the Home Directory tab, I hit Configuration. Then I went to the debugging tab, enabled both Server- and Client-side debugging, hit OK, OK, quit IIS Manager, and ran IISRESET.
Suddenly, the error went away. So, something to try, even though it doesn't make a lot of sense...