ASP: ActiveX cannot create Scripting. FileSystemObject object Solution

An error is reported when an ASP Website generates a static page:

Microsoft VBScript runtime error '800a01ad'
ActiveX parts cannot create objects: 'scripting. filesystemobobject'

In fact, this problem is quite common. The cause of the error is that the server does not support the FSO component. Mainstream CMS systems such as fengxun, kexun, and Yuyi often encounter this situation, because they all adopt static Generation Mechanisms and require FSO component support. Before you start, you must first use an ASP probe to test the server's support for FSO components. Generally, we use Windows 2003 servers.
Next, let's talk about my specific solution. I have analyzed the cause of each possible error and hope to help you.

1) The "scrrun. dll" file is not registered. Line C: \ WINDOWS \ system32. Check whether the scrrun. dll file exists. If not, copy one from the i386 directory of the system installation directory. Next, choose Start> run the following command to register the FSO component:
Regsvr32.exe % windir %/system32/scrrun. dll enables the server's support for the FSO component. to disable the FSO component, run the following command:

Regsvr32.exe/u % windir %/system32/scrrun. dll is normal here, and your problem can be solved.

2) if not, check whether ActiveX control is disabled in the browser. Normally, it won't. Unless it is a server, the security level will be strictly limited. In this case, adjust the security level of the browser to medium or low.
3) your server itself does not support the FSO component.
4) permission issues. Perform the following operations in sequence:
Start Menu-> Run-> regedit-> OK, locate HKEY_CLASSES_ROOT \ Scripting in sequence. fileSystemObject, right-click "permission", and add Everyone and Internet Guest Account (IUSR ...) user Permissions. Restart IIS.
5) Appendix: solutions to Scripting. Dictionary components not supported by the server
The above steps can perfectly solve the problem of ActiveX Object creation failure. If you still find that the scripting.dictionarycomponent is not supported and the solution is complete, see the first step to execute the regsvr32.exe % windir %/system32/scrrun. dll command. If the problem persists, you can add permissions to the object in the Registry by referring to step 4. If you encounter a similar problem, you know how to solve it!
6) Appendix: Server. CreateObject failure solution. A similar error may be prompted when we execute the program, as shown below:
Server Object error 'asp 0177: 800401f3'
Server. CreateObject failed
/Include/test. asp, open test. asp in line 38, check the line 38 of the source code, and check whether the creation object is written incorrectly. The standard format should be:

<% Set fso = Server. CreateObject ("Scripting. FileSystemObject") %>
This situation is mostly caused by careless programmers. In fact, the Scripting. FileSystemObject component can be renamed, which increases the server security. We can change it in the Registry as follows:
Choose "start"> "run"> "regedit"> "OK", locate "HKEY_CLASSES_ROOT \ Scripting. FileSystemObject", right-click "RENAME", and then execute the first step to register the scrrun. dll file. Note that you need to create an object with the new name when writing a program. Otherwise, an error is reported. 7) Attachment: built-in IIS Components
Have you found that the cause of these problems lies in the IIS components? The following section provides the common IIS components for your reference:
MSWC. AdRotator
MSWC. BrowserType
MSWC. NextLink
MSWC. Tools
MSWC. Status
MSWC. Counters
SWC. PermissionChecker
WScript. Shell
Microsoft. XMLHTTP
Scripting. FileSystemObject
ADODB. summary: ActiveX cannot create Scripting. similar problems of FileSystemObject objects are generally solved in a similar way. The main idea should be clear: first, consider the component registration problem, and secondly, the component permission problem. If the server configuration is correct, check your program source code carefully!