Problems with Windows installation IIS (IIS cannot be installed, prompting "Setup cannot copy file Iisapp.vbs") _win server

This is a typical Windows security database problem, you can use the following methods to resolve this issue:

Windows security database, in%windir%\security\database.
Taiwan's database, the mainland is called the data base. With a dedicated Esentutl.exe tool in the Windows operating system, this is a DOS tool that you can use to view and repair Windows security repositories.

Like I did once. An error occurred while installing the components of IIS:
************************
Replication error Installer cannot copy file iisapp.vbs. Verify that the location specified below is correct, or change it and insert a ' Service Pack 1 CD-ROM ' on the specified drive.
When replication source: C:\Windows\ServicePackFiles\i386 [browse] [retry] [Cancel]

************************
This is due to damage to the Windows security database. can be repaired with Esentutl.exe.

To see its usage, use the following directive: Esentutl/? The following prompts are displayed:
Microsoft (r) Windows (r) Database Utilities Version 5.2 Copyright (C) Microsoft Corporation. All Rights Reserved. Description:maintenance Utilities for Microsoft (R) Windows (r) databases. MODES of operation:defragmentation:esentutl/d [options] recovery:esentutl/r [Options] integrity:esentutl/g [options ] checksum:esentutl/k [Options] repair:esentutl/p [options] File Dump:esentutl/m[mode-modifier] <<<<< Press a key for further help >>>>>
D=defragmentation, R=recovery, g=integrity, K=checksum, P=repair, M=file duMp =>

Visible, check the integrity of the database, to use/g, such as: esentutl/g C:\Windows\security\database\secedit.sdb

To fix this Windows security database, use the following directive: esentutl/p C:\Windows\security\database\secedit.


Repair the system database with the Esentutl tool 1

Windows has a large number of interconnected databases. Of course, the primary database is the registry, which contains all the information about the system, the user, and the application settings. However, Windows also contains a large number of other databases that you normally have not heard of. These databases are saved in the form of a system database file, and the suffix is sdb. Some of these records the installation of the application. You will find that usually their file name is setup.sdb. Others record the status of the service pack with filenames like this: Apphelp.sdb, apph_sp. SDB, Drvmain.sdb, Msimain.sdb and Sysmain.sdb. There are other databases to track security or other system settings that are not shown in the registry, such as Secedit.sdb. In short, Windows hides a lot of information in addition to the registry. You can access all of these other databases using the Extensible Storage Engine technology tool (extensible Storage Engine Technology Utility, ESENTUTL).

It's not you. Every SDB file on your hard disk is a database. The confusion is that Microsoft also uses the SDB extension on some text files. For example, the setup.sdb of Visual Studio is a text file. The file can tell you a lot about the application, but that information is not a format that esentutl can manage. The correct SDB file includes binary data.

Warning: The Esentutl tool is extremely powerful. Improper application on the wrong file will erase the security information or cause your system to fail to start. So make sure you fully understand the tool before you use it. Remember to make a backup before modifying any database. Validate these modifications as much as possible prior to doing so through the Microsoft Knowledge Base (Microsoft Knowledge Base).

The Esentutl tool does not provide you with a lot of help information. In fact, it's hard to find where to mention the tool in all Windows Help files or many other Microsoft resources. One place you can find a reference to it is the Microsoft Knowledge Base. Many windows problems require you to fix them with the Esentutl tool. You can use "ESEnTUtl site:support.microsoft.com" as a keyword in google search for some examples from Microsoft's Knowledge Base about the tool usage.

There are several modes of esentutl operation. Each pattern performs a different task on the SDB file. Here is the syntax for each pattern:

Defragmentation mode: esentutl/d < database file name > [options]

Recovery mode: ESENTUTL/R [Options]

Integrity Check mode: esentutl/g < database file name > [options]

Repair mode: esentutl/p < database file name > [options]

Checksum mode: esentutl/k < database file name > [options]

File dump mode: esentutl/m[mode modifier] < filename >

Replication mode: esentutl/y < source > [Options] * * * * * * only for VISTA operating system * * *

The above options vary according to the pattern. However, some options are common in all modes. Here are the General options:

/8 defines a database paging size of 8KB. Under normal circumstances, Esentutl automatically detects paging size. Use this option only if the Microsoft Knowledge Base tells you, or if you are having problems reading the database.

/O disables the Microsoft logo. You can use this option to create a report output or as input to another database.

/s < stream file name > set file name for streaming data output. The default setting is None. Use this option when you want to send data using streaming data technology, rather than a simple dump. This option applies to defragmentation, integrity checking, repair, and file dump mode.

/T < database filename > Set temp database file name. The default setting is temp-dfrg*. EDB. Typically, you do not need to change the database file name because Esentutl already supports multiple staging databases. This option is available for defragmentation, integrity checking, and Repair mode.

Note: Some modes use the same option switch for different purposes. Therefore, do not assume that the/F switch in defragmentation mode and the/F switch in the Integrity check mode perform the same task.