Regarding the similar problem that ActiveX cannot create Scripting.FileSystemObject objects, the solutions are generally similar. The main thing is to have a clear mind: first consider the component registration issue, and secondly the component permission issue. If there is no problem with the server configuration, then check it carefully. Take a look at your program source code
I encountered a problem today. An ASP website reported an error when generating a static page:
Microsoft VBScript runtime error error '800a01ad'
ActiveX component cannot create object: 'Scripting.FileSystemObject'
In fact, this problem is relatively common. The reason for the error is that the server does not support the FSO component. This situation is often encountered in mainstream ASP CMS systems such as Fengxun, Kexun, and Dongyi, because they all adopt static generation mechanisms and require FSO component support. Before starting, you must first use the ASP probe to test the server's support for FSO components. Usually we use a Windows 2003 server.
Below I will talk about my specific solution ideas, and I will analyze each possible reason for error reporting. I hope it will be helpful to you.
1) The "scrrun.dll" file is not registered. Go to the C:/WINDOWS/system32 folder and see if there is a scrrun.dll file. If not, go to the i386 folder in the system installation directory and copy it. Next, start menu->run the following command to register the FSO component:
regsvr32.exe %windir%/system32/scrrun.dll This enables the server to support the FSO component. If you want to turn off the FSO component, run the following command:
regsvr32.exe /u %windir%/system32/scrrun.dll is normal and your problem will be solved.
2) If it still doesn't work, check whether the ActiveX control is disabled in the browser. Normally it won't happen, unless it's a server, the security level will be strictly restricted. If this is the case, just adjust the browser's security level to medium-low.
3) Your server itself does not support FSO components.
4) Consider permission issues. Perform the following operations in sequence:
Start menu -> Run -> regedit -> OK, find HKEY_CLASSES_ROOT/Scripting.FileSystemObject in turn, right-click "Permissions", add the permissions of Everyone, Internet Guest Account (IUSR...) users, and restart IIS to solve the problem.
5) Attachment: Solution to the problem that the server does not support the Scripting.Dictionary component
Through the above steps, you can perfectly solve the problem of ActiveX object creation failure. If there is still a problem that the Scripting.Dictionary component is not supported, the solution is similar. Refer to the first step and execute the regsvr32.exe %windir%/system32/scrrun.dll command. If it is not resolved yet, consider the permission issue. You can refer to step 4 to add permissions to this object in the registry. Draw inferences from one example and know how to solve it if you encounter similar problems again!
6) Attachment: Solution to Server.CreateObject failure. When we execute the program, we may be prompted with similar errors, as follows:
Server object error 'ASP 0177: 800401f3'
Server.CreateObject failed
/include/test.asp, open test.asp at line 38, check the source code near line 38, and see if there is any error in the writing method of creating the object. The standard writing method should be:
<% Set fso = Server.CreateObject("Scripting.FileSystemObject") %>
This situation is mostly caused by carelessness on the part of the programmer. In fact, the Scripting.FileSystemObject component can be renamed, which will increase the security of the server. We can change it in the registry as follows:
Start menu->Run->regedit->OK, find HKEY_CLASSES_ROOT/Scripting.FileSystemObject in turn, right-click "Rename", and then execute the first step to register the scrrun.dll file. Note that when you write the program, you must create the object with this new name, otherwise an error will be reported. 7) Attachment: IIS comes with components
Have you discovered that the causes of these problems all lie in IIS's own components? Here are some common IIS components for reference:
MSWC.AdRotator
MSWC.BrowserType
MSWC.NextLink
MSWC.Tools
MSWC.Status
MSWC.Counters
SWC.PermissionChecker
WScript.Shell
Microsoft.XMLHTTP
Scripting.FileSystemObject
ADODB.Connection To summarize, regarding the similar problem that ActiveX cannot create Scripting.FileSystemObject objects, the solutions are generally similar. The main thing is to have clear ideas: first consider the component registration issue, and secondly the component permission issue. If there is no problem with the server configuration If so, then carefully check your program source code!