Microsoft KB Archive/828874

= Use of ABO to Extend IIS Metabase Schema Is Not Supported =

Article ID: 828874

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Platform Software Development Kit-January 2000 Edition
 * Microsoft Internet Information Server 4.0
 * Microsoft Internet Information Services 5.0
 * Microsoft Internet Information Services 5.1
 * Microsoft Internet Information Services 6.0

-





SYMPTOMS
Changes that are made to the Microsoft Internet Information Server (IIS) 6 schema with a program that uses the IMSAdminBase interface (Admin Base Objects (ABOs) may not remain after you restart IIS 6. This same program may work fine with IIS 5.



CAUSE
Use of the IIS Admin Base Object (ABO) to extend the metabase schema is not supported.



RESOLUTION
Use Active Directory Service Interfaces (ADSI) to extend the metabase schema. Also use ADSI to set and to retrieve values in the metabase.



STATUS
This behavior is by design.



MORE INFORMATION
The program that uses ABO may try to extend the schema by adding an entry under /Schema/Properties/Names. This is not sufficient. For example, entries under /Schema/Properties/Defaults and /Schema/Properties/Types must be added. If you add an entry under /Schema/Properties/Types, a structure must be passed as the pbMDData member of the METADATA_RECORD structure. This structure is not published and is only used internally by IIS. In IIS 6, extra code was added to make sure that the metabase schema is well formatted. This code was added to safeguard IIS against possible incorrect edits of the MBSchema.xml file. These edits are also not supported by IIS. This extra code prevents the malformed property from being persisted in the metabase.

For more information about how to extend the IIS metabase schema by using ADSI, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/aa670750(VS.71).aspx

IIS 5 may accept the addition of data under /Schema/Properties/Names, but IIS 5 does not support this. It works because the metabase is not aware of the semantic of the /Schema in IIS 5.

