File name: | iiscfg.dll.mui |
Size: | 27648 byte |
MD5: | a4eee5cfa2b3cad127f978fa2f853dc9 |
SHA1: | 4f19be6005d70cefb2e50d55e08721a649ef82b6 |
SHA256: | 0ecc997781321e62cb901b581f8854697d401ec979e6e89db9958e8d6b25ecfa |
Operating systems: | Windows 10 |
Extension: | MUI |
If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.
id | English (U.S.) | English |
---|---|---|
353 | Server Application ID: %s |
Server Application ID: %s |
354 | Server Application Name: %s |
Server Application Name: %s |
355 | The serious nature of this error has caused the process to terminate. |
The serious nature of this error has caused the process to terminate. |
356 | Error Code = 0x%08x : %s |
Error Code = 0x%08x : %s |
357 | Catalog Internals Information: File: %s, Line: %d |
Catalog Internals Information: File: %s, Line: %d |
358 | Error in %s(%d): %s | Error in %s(%d): %s |
359 | Error in %s(%d), hr = %x: %s | Error in %s(%d), hr = %x: %s |
360 | Error in %s(%d), %s: %s | Error in %s(%d), %s: %s |
361 | Application information is not available. |
Application information is not available. |
362 | Exception: %s |
Exception: %s |
363 | Address: %s |
Address: %s |
364 | Call Stack: |
Call Stack: |
365 | Assertion Failure: |
Assertion Failure: |
366 | Component Prog ID: %s |
Component Prog ID: %s |
367 | Method Name: %s |
Method Name: %s |
368 | Process Name: %s |
Process Name: %s |
0x1 | SVC%0 | SVC%0 |
0x2 | Catalog%0 | Catalog%0 |
0x3 | Config Schema Compile%0 | Config Schema Compile%0 |
0x4 | %0 | %0 |
0x800210B4 | Ignoring Element with a name of length greater than 1023 characters (%1).%2%3%4%5%0 | Ignoring Element with a name of length greater than 1023 characters (%1).%2%3%4%5%0 |
0x800210B5 | 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 | 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 |
0x800210B6 | It 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 | It 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 |
0x800210B7 | 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 | 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 |
0x800210B8 | 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 | 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 |
0x800210B9 | The 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 | The 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 |
0x800210BA | 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 (%1). Ignoring the property with the invalid flag value. Check the schema for the correct flag values. Incorrect XML:%2%3%4%5%0 |
0x800210BB | 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 | 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 |
0x800210BC | Custom elements are allowed on %1 only. Move or delete this custom element. Incorrect XML:%2%3%4%5%0 | Custom elements are allowed on %1 only. Move or delete this custom element. Incorrect XML:%2%3%4%5%0 |
0x800210BD | Unable to find metabase property %1. The schema indicates that this property is required.%2%3%4%5%0 | Unable to find metabase property %1. The schema indicates that this property is required.%2%3%4%5%0 |
0x800210BE | An 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 | An 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 |
0x800210BF | 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 | 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 |
0x800210C1 | 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 | 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 |
0x800210C2 | Custom 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 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 |
0x800210C3 | 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 | 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 |
0x800210C4 | A Custom element was found but it is missing the required 'ID' attribute. Ignoring this element. Incorrect XML:%1%2%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 |
0x800210C5 | A 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 | A 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 |
0x800210C6 | 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 Boolean Value (%1), Ignoring property with unknown Boolean value. Valid Boolean values are TRUE/FALSE or 0/1.%2%3%4%5%0 |
0x800210C7 | Invalid Enum Value (%2) for %1, Ignoring property. Refer to the schema for valid Enum values.%3%4%5%0 | Invalid Enum Value (%2) for %1, Ignoring property. Refer to the schema for valid Enum values.%3%4%5%0 |
0x800210D5 | Duplicate location found (%1). Ignoring the properties found in duplicate location. Make sure each location is unique.%2%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 |
0x800210D6 | Internal Error: %1. This is often due to low memory/resource conditions, try closing other programs to free memory.%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 |
0x800210D8 | Schema Compilation Error: Flag specified (%1) is not a valid Flag for Table (%2). This flag will be ignored.%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 |
0x800210D9 | Win32 API call failed: Call (%1). Make sure no files are locked, consider restarting the system to resolve.%2%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 |
0x800210EC | Property (%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 has the Property ID (%2) which collides with property (%3) already defined. Ignoring the latter property. Incorrect XML:%4%5%0 |
0x800210ED | 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 | 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 |
0x800210EE | Element (%1) has content (%2). The metabase uses attribute values, not element content. This can happen if an open bracket | Element (%1) has content (%2). The metabase uses attribute values, not element content. This can happen if an open bracket |
0x800210EF | Custom property (%1) has no value. Ignoring this property %2%3%4%5%0 | Custom property (%1) has no value. Ignoring this property %2%3%4%5%0 |
0x800210F0 | XML Attribute has value (\"\") which is not permitted. Ignoring this property.%1%2%3%4%5%0 | XML Attribute has value (\"\") which is not permitted. Ignoring this property.%1%2%3%4%5%0 |
0x8002C83A | Resetting the read only attribute on the metabase file. This is required for backwards compatibility.%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 |
0x8002C83B | A 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 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 |
0x8002C83C | 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 | 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 |
0x8002C83E | Unable to decrypt the secure property. Ignoring the property.%1%2%3%4%5%0 | Unable to decrypt the secure property. Ignoring the property.%1%2%3%4%5%0 |
0x8002C83F | Edits on secure properties are not allowed. Ignoring the edit on the secure 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 |
0xC00210B2 | File (%1) not found.%2%3%4%5%0 | File (%1) not found.%2%3%4%5%0 |
0xC00210B3 | Error parsing XML file.%1Reason: %2 Incorrect XML: %3%4%5%0 | Error parsing XML file.%1Reason: %2 Incorrect XML: %3%4%5%0 |
0xC00210C0 | 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 | 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 |
0xC00210C8 | Class (%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 | Class (%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 |
0xC00210C9 | Error retrieving default schema table (%1). It may be necessary to reinstall/fix the installation.%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 |
0xC00210CA | Out of memory during schema compile or writing the schema file. Try freeing memory by closing other programs.%1%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 |
0xC00210CB | Schema Compilation Error in Inheritance: Referenced Column (%1) is a Directive column, this is not supported.%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 |
0xC00210CC | Schema 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 | Schema 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 |
0xC00210CD | Schema 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 | Schema 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 |
0xC00210CE | Schema 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: Specifying a DefaultValue on a FixedLength MultiString is not allowed. Remove this attribute. Invalid property is (%1).%2%3%4%5%0 |
0xC00210CF | 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) not found. This attribute is required to correctly compile. Incorrect XML (%2).%3%4%5%0 |
0xC00210D0 | 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 (%1) has value (%2), exceeds the maximum allowed number of characters. The maximum characters is (%3).%4%5%0 |
0xC00210D1 | 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: Attribute (InheritsPropertiesFrom) has value (%1). Correct the attribute to be in the form (IISConfigObject::Property).%2%3%4%5%0 |
0xC00210D2 | Schema Compilation Error: Property attempted to inherit from table (%1). Properties may only inherit from table (%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 |
0xC00210D3 | 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: 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 |
0xC00210D4 | Schema Compilation Error: Data type (%1) unknown. Refer to the schema for valid data types.%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 |
0xC00210D7 | Schema 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 | Schema 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 |
0xC00210DA | No file name supplied.%1%2%3%4%5%0 | No file name supplied.%1%2%3%4%5%0 |
0xC00210DB | File name supplied (...%1) is too long.%2%3%4%5%0 | File name supplied (...%1) is too long.%2%3%4%5%0 |
0xC00210DC | 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 character found in value (%1). Strings typed as BYTES must have only 0-9, a-f, A-F.%2%3%4%5%0 |
0xC00210DD | 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 boolean string value (%1). The only legal BOOL values are: true, false, 0, 1, yes, no, on, off.%2%3%4%5%0 |
0xC00210DE | 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 | 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 |
0xC00210DF | Invalid 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 | Invalid 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 |
0xC00210E0 | The file (%1) is not write accessible.%2%3%4%5%0 | The file (%1) is not write accessible.%2%3%4%5%0 |
0xC00210E1 | Parent table does not exist.%1%2%3%4%5%0 | Parent table does not exist.%1%2%3%4%5%0 |
0xC00210E2 | PrimaryKey column (%1) is NULL. Parent table does not exist.%2%3%4%5%0 | PrimaryKey column (%1) is NULL. Parent table does not exist.%2%3%4%5%0 |
0xC00210E3 | A Column (%1) is NULL. This column is marked as NOTNULLABLE, so a value must be provided.%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 |
0xC00210E4 | 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 Insert a new row; but a row with the same Primary Key already exists. Updated the row instead.%1%2%3%4%5%0 |
0xC00210E5 | 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 | 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 |
0xC00210E6 | Invalid enum value (%2) supplied for Column (%1)%3%4%5%0 | Invalid enum value (%2) supplied for Column (%1)%3%4%5%0 |
0xC00210E7 | Two rows within the XML have the same primary key.%1%2%3%4%5%0 | Two rows within the XML have the same primary key.%1%2%3%4%5%0 |
0xC00210E8 | 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 | 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 |
0xC00210E9 | 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 | 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 |
0xC00210EA | 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 | 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 |
0xC00210EB | Two properties with the same ID (%1), under Location (%2) were specified in the XML. Ignoring the latter property.%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 |
0xC00210F1 | Invalid boolean string value (%1). The only legal BOOL values are: true, false.%2%3%4%5%0 | Invalid boolean string value (%1). The only legal BOOL values are: true, false.%2%3%4%5%0 |
0xC00210F2 | Schema Compilation Error: There were too many classes or properties defined.%1%2%3%4%5%0 | Schema Compilation Error: There were too many classes or properties defined.%1%2%3%4%5%0 |
0xC00210F3 | Numeric Property (%1) from Collection (%2) has value (%3) which is outside the legal range (%4).%5%0 | Numeric Property (%1) from Collection (%2) has value (%3) which is outside the legal range (%4).%5%0 |
0xC002C811 | 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 | 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 |
0xC002C812 | 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 | 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 |
0xC002C813 | 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 | 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 |
0xC002C814 | 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 error occurred while determining what text edits were made to the metabase file, no changes were applied.%1%2%3%4%5%0 |
0xC002C815 | 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 internal error occurred while parsing edits to the metabase file, some changes may not have been applied. %1%2%3%4%5%0 |
0xC002C816 | An error occurred while applying text edits to the metabase. The metabase may be locked in memory.%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 |
0xC002C817 | An 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 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 |
0xC002C818 | 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 | 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 |
0xC002C819 | Unable 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 | Unable 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 |
0xC002C81A | 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 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 |
0xC002C81B | 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 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 |
0xC002C81C | 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 | 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 |
0xC002C81D | A notification client threw an exception. %1%2%3%4%5%0 | A notification client threw an exception. %1%2%3%4%5%0 |
0xC002C81E | The event firing thread died unexpectedly. %1%2%3%4%5%0 | The event firing thread died unexpectedly. %1%2%3%4%5%0 |
0xC002C838 | 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 | 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 |
0xC002C839 | Could 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 | Could 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 |
0xC002C83D | An edited metabase path was not found. The path may have already been deleted.%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 |
File Description: | IIS Catalog DLL |
File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
Company Name: | Microsoft Corporation |
Internal Name: | iiscfg.dll |
Legal Copyright: | © Microsoft Corporation. All rights reserved. |
Original Filename: | iiscfg.dll.mui |
Product Name: | Internet Information Services |
Product Version: | 10.0.15063.0 |
Translation: | 0x409, 1200 |