ActiveX parts cannot create objects: 'scripting. filesystemobobject'

Microsoft VBScript runtime error '800a01ad'

ActiveX parts cannot create objects: 'scripting. filesystemobobject'

This error indicates that the FSO component in IIS is not enabled.

The following describes how to enable and disable the FSO control.
Windows 98 System
Enter the following command in the doscommand line status:
Close the command: regsvr32/u c: \ WINDOWS \ SYSTEM \ scrrun. dll
Open the command: regsvr32 C: \ WINDOWS \ SYSTEM \ scrrun. dll
Win2000 system:
Enter the following command in the CMD command line status:
Close the command: regsvr32/U c: \ winnt \ system32 \ scrrun. dll
Open the command: regsvr32 c: \ winnt \ system32 \ scrrun. dll
Win2003:
Run regsvr32 scrrun. dll.
To disable the FSO component, run regsvr32/u scrrun. dll.

My system is 2003, but I did n back using the 2003 system method, but it still didn't work. I tested my system with an ASP probe and still didn't use FSO. Finally, I found a solution with my friend's help.

The error persists after multiple message injection and startup because you do not have the permission.

, Do not know how to cause, the following provides a solution

Permission error. open registry and add permission!
In start-run, enter

Regedit, and then find hkey_classes_root \ SCR using pting. FileSystemObject

Right-click permission and add

Everyone, Internet Guest Account (IUSR...) User OK, and then restart IIS to get it done!

YesterdayProgramWhen I encountered that IIS does not support FSO, it took a lot of effort to make my IIS support the FSO component, but today's debugging program appeared again

Server Object error 'asp 0177: 800401f3'

Server. Createobject failed

I checked the output of objects that cannot be created. The scripting. dictionary was searched on the Internet again. The solution was regsvr32 scrrun. dll. Didn't the problem be solved yesterday! I thought my scrrun. dll was broken and copied from another machine. I registered it again, but the problem persists. After cool for a while, I suddenly thought that yesterday's FSO needs to go to the Registry to grant permissions. This object is also in the FSO component, and it may also need to be assigned permissions. I tried to find it in the registry, so I found that this object exists in the registry, I will give it to 'scripting. the FileSystemObject 'weighted method adds permissions. The problem is solved.

After this problem is solved, another mswc. browsertype 800401f3 is returned. Now I have some experience. First I found the component that it belongs to, maybe msxml3.dll. After registering, I went to the Registry and typed it. I added the permission and set it to another one.

I found that these are all self-generated IIS components. I don't think it is necessary to register them first. Instead, you can directly go to the Registry and grant the permission. Except that a component may have been detached, You need to register it first.

Generally, the steps for adding permissions to components are as follows:

Regedit, and find the component object name corresponding to hkey_classes_root.

Right-click permission and add

Everyone, Internet Guest Account (IUSR...) User OK, and then restart IIS to get it done!

IIS comes with the following components:

mswc. adrotator
mswc. browsertype
mswc. nextlink
mswc. tools
mswc. status
mswc. counters
SWC. permissionchecker
wscript. shell
Microsoft. XMLHTTP
scripting. fileSystemObject
ADODB. connection