SoFunction
Updated on 2025-04-13

Detailed explanation of common ASP errors and solutions summary Recommended

IIS Tips:
Active Server Pages Error 'ASP 0201'
The default script language is invalid
The default scripting language specified for this application is invalid.

The methods for collecting online are:
Method 1
Running regsvr32 /u
regsvr32
Also, if it still doesn't work, you can try uninstalling iis, then delete the wwwroot directory, and reinstall IIS.

Method 2
1. Delete "internet information service",
2. Restart the machine, press F8 to enter "safe mode".
3. Rename "C:\Inetpub", "c:\windows\", and "c:\windows\system32\inetsrv" in safe mode.
4. Restart the machine, install "Internet Information Service" in normal mode, and delete the rename file after installation.
5. If the problem cannot be solved, open "Internet Information Service" and "restart IIS".

Method 3(This is done OK!)
1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services.
2. In the console tree, click the default web site. In the Display pane, right-click the Default Web Site, and then click Properties.
3. In the Anonymous Access and Authentication Control on the Directory Security tab, click Edit.
4. In the Authentication Method Properties page, click to remove the anonymous access checkmark.

====================

This is a pretty common asp error, which is usually caused by the following reasons:
Before we use a variety of ways to solve this problem, let's take a look at the error itself.
Like a complete error message? Any of the reasons that may cause this problem will get us the following message:


Active Server Pages Error 'ASP 0201'
Error invalid default scripting language
The default scripting language that the application should be is invalid

This error is usually caused by an "unsupported scripting language" that IIS does not recognize. How to fix it now?
Try the following steps:

1. Confirm that the appropriate scripting language is defined in IIS. (Enter IIS Management - select site - properties - home directory - configuration - options - default ASP language), confirm that the default ASP language is set to VBscrīpt (default) or Jscrīpt (if you prefer Javascript scripts)

2. Note that if the first line of your code contains <%Language="language"%>, it will overwrite the above settings, so check carefully to ensure that you have no spelling errors. It should be <%Language="VBscraīpt"%>

3. Sometimes, incomplete DLL registration of script citation can also cause this problem. Please download the latest version of script citation to try.

4. Now, we need to confirm that some DLL files were not registered when installing the script. For example, you can try to register a DLL in the following way:
regsvr32 %windir%\system32\VBscrī
regsvr32 %windir%\system32\Jscrī
regsvr32 %windir%\system32\Inetsrv\


5. Continue, if you haven't solved this problem yet, it looks like permissions are causing the problem.
For example: make anonymous users access the iusr_computer name of the website. This user does not have read permissions for the relevant DLL. You can try to give the DLL file in (4) to the anonymous user read permission.

6. Next step, if you still see the same error, you need to try to follow another step to ensure that the relevant permissions are correct. Refer to the following documents:
IIS 4 - User and NTFS permissions required for IIS 4 (/?id=187506)IIS 5 - How to set the required user and NTFS permissions for IIS5 (/?id=271071)IIS 6 - IIS6.0 default user and NTFS permissions (/?id=812614)

7. If you follow the above steps strictly, you should not see this error again, unless you forget some configurations in the above steps. You can temporarily add the iusr_computer name user to the local administrator group. Note that this is just to find the problem. When the problem is solved, you must not add anonymous users to the administrator group.
If you join the administrator group, the problem has been solved. It is certain that this is because of permission issues. Please follow the steps above to check the permission settings again. If it still does not resolve, please delete the anonymous user from the administrator group and then consult other relevant professional and technical personnel.