????

Your IP : 3.129.194.130

Current Path : C:/Windows/System32/inetsrv/en-US/

Current File : C:/Windows/System32/inetsrv/en-US/iiscfg.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!j

�7@ <g8.rdata�@@.rsrcp h@@{��B
T88{��B$��8.rdata8x.rdata$zzzdbg p.rsrc$01p!�e.rsrc$02 ��-S�Kɓ�#?7g��Ce*���Tc�{��B`�0�H�h������������� 0 @ Ph!�� "j��%D��%�]�ȃt�MUI����P\U1���J�gI&���㢟9@qv��������MUIen-US

Server Application ID: %s

Server Application Name: %sG

The serious nature of this error has caused the process to terminate.

Error Code = 0x%08x : %s4

Catalog Internals Information:

File: %s, Line: %dError in %s(%d): %sError in %s(%d), hr = %x: %sError in %s(%d), %s: %s+

Application information is not available.

Exception: %s

Address: %s

Call Stack:

Assertion Failure:

Component Prog ID: %s

Method Name: %sPA

Process Name: %s�����L����4��������������:��<��T>��?���#����%�����%����`'����6����`7����XF�����H8��9���Y=��=��8]SVC%0

Catalog%0

8Config Schema Compile%0

<>%0

�Ignoring Element with a name of length greater than 1023 characters (%1).%2%3%4%5%0

Element found (%1) that does NOT match one of the defined Metabase Classes. See mbschema.xml for valid class definitions.%2%3%4%5%0

0It is illegal to have an element called 'Custom' at this level of the XML. 'Custom' elements must have a parent node. Incorrect XML:%1%2%3%4%5%0

A Location attribute is required but was not found on property (%1). Ignoring property due to missing location. Incorrect XML:%2%3%4%5%0

The property (%1) is not valid for the class it has been associated with. This property will be ignored. Incorrect XML:%2%3%4%5%0

lThe compiled schema file (%1) is invalid. This is typically due to an upgrade just occurring or the file is corrupt. The default shipped schema will be used instead.%2%3%4%5%0

(Invalid flag (%1). Ignoring the property with the invalid flag value. Check the schema for the correct flag values. Incorrect XML:%2%3%4%5%0

\Invalid Flag(s). Property (%1) has Value (%2), which is out of the legal range for this property (%3). Check the schema for the legal flag range. Incorrect XML:%4%5%0

�Custom elements are allowed on %1 only. Move or delete this custom element. Incorrect XML:%2%3%4%5%0

�Unable to find metabase property %1. The schema indicates that this property is required.%2%3%4%5%0

LAn odd number of characters was specified for a binary attribute value (%1). Binary values must be specified in even number of characters (ex: FFFE01).%2%3%4%5%0

�A binary attribute value (%1) contains a non-hex character. Valid characters are 0-9, a-f and A-F.%2%3%4%5%0

<At this level in the XML a Custom element expected, but an unknown element was found. Mark as Custom or delete this element. Incorrect XML:%1%2%3%4%5%0

LCustom element found; but it does not have the required Location property on its parent element. Fix the parent's Location property. Incorrect XML:%1%2%3%4%5%0

Custom Property has name (%1) which conflicts with ID (%2) as defined in the schema. Fix the name or ID. Incorrect XML:%3%4%5%0

A Custom element was found but it is missing the required 'ID' attribute. Ignoring this element. Incorrect XML:%1%2%3%4%5%0

LA Custom Property (%1) was found but contained no 'Type' attribute. Defaulting to 'String'. Recommend explicitly specifying the type. Incorrect XML:%2%3%4%5%0

Invalid Boolean Value (%1), Ignoring property with unknown Boolean value. Valid Boolean values are TRUE/FALSE or 0/1.%2%3%4%5%0

�Invalid Enum Value (%2) for %1, Ignoring property. Refer to the schema for valid Enum values.%3%4%5%0

Duplicate location found (%1). Ignoring the properties found in duplicate location. Make sure each location is unique.%2%3%4%5%0

Internal Error: %1. This is often due to low memory/resource conditions, try closing other programs to free memory.%2%3%4%5%0

�Schema Compilation Error: Flag specified (%1) is not a valid Flag for Table (%2). This flag will be ignored.%3%4%5%0

�Win32 API call failed: Call (%1). Make sure no files are locked, consider restarting the system to resolve.%2%3%4%5%0

LProperty (%1) defined in schema has the Property ID (%2) which collides with property (%3) already defined. Ignoring the latter property. Incorrect XML:%4%5%0

�Property (%1) defined in schema is attempting to use Property ID (%2) which was already being used by another property. Update the Name or ID. Ignoring this property. Incorrect XML:%3%4%5%0

0Element (%1) has content (%2). The metabase uses attribute values, not element content. This can happen if an open bracket < is omitted.%3%4%5%0

�Custom property (%1) has no value. Ignoring this property %2%3%4%5%0

�XML Attribute has value ("") which is not permitted. Ignoring this property.%1%2%3%4%5%0

�Resetting the read only attribute on the metabase file. This is required for backwards compatibility.%1%2%3%4%5%0

HA file with the highest minor number possible was already found. Hence cannot generate a higher minor file that contains the successfully applied user edits. We will apply the user edits to the file with the highest minor. It is recommended that you cleanup the minor files.%1%2%3%4%5%0

A child node without a properly formed parent node was found. Ignoring it. Check spelling and format of location properties.%1%2%3%4%5%0

�Unable to decrypt the secure property. Ignoring the property.%1%2%3%4%5%0

�Edits on secure properties are not allowed. Ignoring the edit on the secure property.%1%2%3%4%5%0

HFile (%1) not found.%2%3%4%5%0

�Error parsing XML file.%1Reason: %2 Incorrect XML: %3%4%5%0

�The XML file (%1) is valid, but failed to parse. This is typically due to the file being in use. It can also be an internal error. Refer this error to your support professional.%2%3%4%5%0

0Class (%1) not found in metabase OR found in inappropriate location or position. Refer to the schema for correct class name or location.%2%3%4%5%0

�Error retrieving default schema table (%1). It may be necessary to reinstall/fix the installation.%2%3%4%5%0

Out of memory during schema compile or writing the schema file. Try freeing memory by closing other programs.%1%2%3%4%5%0

�Schema Compilation Error in Inheritance: Referenced Column (%1) is a Directive column, this is not supported.%2%3%4%5%0

TSchema Compilation Error in Inheritance: The referenced element:property (%1:%2) is a Flag or Enum. But there are no Flag/Enum values defined in the schema.%3%4%5%0

8Schema Compilation Error: DefaultValue is too large. Lower the default to be less than the maximum size (%1) bytes. Invalid property is (%2).%3%4%5%0

DSchema Compilation Error: Specifying a DefaultValue on a FixedLength MultiString is not allowed. Remove this attribute. Invalid property is (%1).%2%3%4%5%0

Schema Compilation Error: Attribute (%1) not found. This attribute is required to correctly compile. Incorrect XML (%2).%3%4%5%0

,Schema Compilation Error: Attribute (%1) has value (%2), exceeds the maximum allowed number of characters. The maximum characters is (%3).%4%5%0

@Schema Compilation Error: Attribute (InheritsPropertiesFrom) has value (%1). Correct the attribute to be in the form (IISConfigObject::Property).%2%3%4%5%0

Schema Compilation Error: Property attempted to inherit from table (%1). Properties may only inherit from table (%2).%3%4%5%0

�Schema Compilation Error: Required database (%1) not found. Either an internal error occurred OR this DLL was incorrectly set as the IIS product when schema for IIS does not exist.%2%3%4%5%0

�Schema Compilation Error: Data type (%1) unknown. Refer to the schema for valid data types.%2%3%4%5%0

DSchema Compilation Error: Enum specified (%1) is not a valid Enum for Table (%2). Check the spelling and refer to the schema for valid enum values.%3%4%5%0

PNo file name supplied.%1%2%3%4%5%0

lFile name supplied (...%1) is too long.%2%3%4%5%0

�Invalid character found in value (%1). Strings typed as BYTES must have only 0-9, a-f, A-F.%2%3%4%5%0

�Invalid boolean string value (%1). The only legal BOOL values are: true, false, 0, 1, yes, no, on, off.%2%3%4%5%0

Invalid enum value (%1). One enum value may be supplied. The following are examples of legal enum values for this property: %2 %3 %4%5%0

xInvalid flag value (%1). Multiple flags may be separated by a comma, the | character and/or a space. The following are examples of legal flag values for this property: %2 %3 %4%5%0

lThe file (%1) is not write accessible.%2%3%4%5%0

\Parent table does not exist.%1%2%3%4%5%0

�PrimaryKey column (%1) is NULL. Parent table does not exist.%2%3%4%5%0

�A Column (%1) is NULL. This column is marked as NOTNULLABLE, so a value must be provided.%2%3%4%5%0

�Attempted to Insert a new row; but a row with the same Primary Key already exists. Updated the row instead.%1%2%3%4%5%0

�Attempted to Update a row; but no row matching the Primary Key currently exists. Insert a new row instead.%1%2%3%4%5%0

|Invalid enum value (%2) supplied for Column (%1)%3%4%5%0

�Two rows within the XML have the same primary key.%1%2%3%4%5%0

`Two properties with the same name (%1), under Location (%2) were specified in the XML. Make sure names are unique within a location. Ignoring the latter property.%3%4%5%0

$The file (%1) contains too many warnings. No more warnings will be reported during this operation. Resolve the current warnings.%2%3%4%5%0

,Invalid Numeric Value. Check the value to make sure it does not contain non-numeric characters. Ignoring property. Incorrect XML:%1%2%3%4%5%0

Two properties with the same ID (%1), under Location (%2) were specified in the XML. Ignoring the latter property.%3%4%5%0

�Invalid boolean string value (%1). The only legal BOOL values are: true, false.%2%3%4%5%0

�Schema Compilation Error: There were too many classes or properties defined.%1%2%3%4%5%0

�Numeric Property (%1) from Collection (%2) has value (%3) which is outside the legal range (%4).%5%0

Schema information could not be read because could not fetch or read the binary file where the information resides.%1%2%3%4%5%0

�Could not find a history file with the same major version number as the one being edited, therefore these edits can not be processed. Try increasing the number of history files or editing a newer version of the metabase.xml file.%1%2%3%4%5%0

�A warning/error occurred while processing text edits to the metabase file. The file with the warning/error has been copied into the history directory with the name Errors appended to it.%1%2%3%4%5%0

�An error occurred while determining what text edits were made to the metabase file, no changes were applied.%1%2%3%4%5%0

�An internal error occurred while parsing edits to the metabase file, some changes may not have been applied. %1%2%3%4%5%0

�An error occurred while applying text edits to the metabase. The metabase may be locked in memory.%1%2%3%4%5%0

PAn error occurred while applying text edits to the history file, check for disk full, look for corresponding events in the event log for more details.%1%2%3%4%5%0

�An error occurred during the processing of text edits. Due to this error, no further text edits will be processed. It is necessary to restart the IISAdmin process to recover.%1%2%3%4%5%0

HUnable to read the edited metabase file (tried 10 times). Check for (a) Missing metabase file or (b) Locked metabase file or (c) XML syntax errors.%1%2%3%4%5%0

�An internal error occurred while processing the text edits that were applied to the metabase. May be out-of-memory, look for corresponding events in the event log for more details.%1%2%3%4%5%0

|An error occurred while processing text edits to the metabase file. Normally the file with the error would be copied to the History folder, however an error prevented this.%1%2%3%4%5%0

�An error occurred while saving the metabase file. This can happen when the metabase XML file is in use by another program, or if the disk is full. Check for corresponding events in the event log for more details.%1%2%3%4%5%0

xA notification client threw an exception. %1%2%3%4%5%0

xThe event firing thread died unexpectedly. %1%2%3%4%5%0

�The configured value for the property MaxHistoryFiles is being ignored and it is being defaulted. This may be because it conflicted with the EnableEditWhileRunning and/or EnableHistory property. Please fix the configured value.%1%2%3%4%5%0

XCould not copy the edited metabase file therefore cannot process user edits. May be disk full, look for related errors in the event log for more details.%1%2%3%4%5%0

�An edited metabase path was not found. The path may have already been deleted.%1%2%3%4%5%0

t4VS_VERSION_INFO��
|O
|O?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationHFileDescriptionIIS Catalog DLLh$FileVersion10.0.20348.1 (WinBuild.160101.0800)6InternalNameiiscfg.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenameiiscfg.dll.mui\ProductNameInternet Information Services>
ProductVersion10.0.20348.1DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD