Windows / Headers / imapi2fserror.h
imapi2fserror.h
Associated Error Codes
Below is a list of error codes found for this header.
| Symbolic | Value | Description |
|---|---|---|
| IMAPI_E_FSI_INTERNAL_ERROR | 0xc0aab100 | Internal file system error occurred. |
| IMAPI_E_INVALID_PARAM | 0xc0aab101 | The value specified for parameter '%1!ls!' is not valid. |
| IMAPI_E_READONLY | 0xc0aab102 | FileSystemImage object is in read only mode. |
| IMAPI_E_NO_OUTPUT | 0xc0aab103 | No output file system specified. |
| IMAPI_E_INVALID_VOLUME_NAME | 0xc0aab104 | The specified Volume Identifier is either too long or contains one or more invalid characters. |
| IMAPI_E_INVALID_DATE | 0xc0aab105 | Invalid file dates. %1!ls! time is earlier than %2!ls! time. |
| IMAPI_E_FILE_SYSTEM_NOT_EMPTY | 0xc0aab106 | The file system must be empty for this function. |
| IMAPI_E_NOT_FILE | 0xc0aab108 | Specified path '%1!ls!' does not identify a file. |
| IMAPI_E_NOT_DIR | 0xc0aab109 | Specified path '%1!ls!' does not identify a directory. |
| IMAPI_E_DIR_NOT_EMPTY | 0xc0aab10a | The directory '%1!s!' is not empty. |
| IMAPI_E_NOT_IN_FILE_SYSTEM | 0xc0aab10b | '%1!ls!' is not part of the file system. It must be added to complete this operation. |
| IMAPI_E_INVALID_PATH | 0xc0aab110 | Path '%1!s!' is badly formed or contains invalid characters. |
| IMAPI_E_RESTRICTED_NAME_VIOLATION | 0xc0aab111 | The name '%1!ls!' specified is not legal: Name of file or directory object created while the UseRestrictedCharacterSet property is set may only contain ANSI characters. |
| IMAPI_E_DUP_NAME | 0xc0aab112 | '%1!ls!' name already exists. |
| IMAPI_E_NO_UNIQUE_NAME | 0xc0aab113 | Attempt to add '%1!ls!' failed: cannot create a file-system-specific unique name for the %2!ls! file system. |
| IMAPI_E_ITEM_NOT_FOUND | 0xc0aab118 | Cannot find item '%1!ls!' in FileSystemImage hierarchy. |
| IMAPI_E_FILE_NOT_FOUND | 0xc0aab119 | The file '%1!s!' not found in FileSystemImage hierarchy. |
| IMAPI_E_DIR_NOT_FOUND | 0xc0aab11a | The directory '%1!s!' not found in FileSystemImage hierarchy. |
| IMAPI_E_IMAGE_SIZE_LIMIT | 0xc0aab120 | Adding '%1!ls!' would result in a result image having a size larger than the current configured limit. |
| IMAPI_E_IMAGE_TOO_BIG | 0xc0aab121 | Value specified for FreeMediaBlocks property is too small for estimated image size based on current data. |
| IMAPI_E_DATA_STREAM_INCONSISTENCY | 0xc0aab128 | Data stream supplied for file '%1!ls!' is inconsistent: expected %2!I64d! bytes, found %3!I64d!. |
| IMAPI_E_DATA_STREAM_READ_FAILURE | 0xc0aab129 | Cannot read data from stream supplied for file '%1!ls!'. |
| IMAPI_E_DATA_STREAM_CREATE_FAILURE | 0xc0aab12a | The following error was encountered when trying to create data stream for '%1!ls!': |
| IMAPI_E_DIRECTORY_READ_FAILURE | 0xc0aab12b | The following error was encountered when trying to enumerate files in directory '%1!ls!': |
| IMAPI_E_TOO_MANY_DIRS | 0xc0aab130 | This file system image has too many directories for the %1!ls! file system. |
| IMAPI_E_ISO9660_LEVELS | 0xc0aab131 | ISO9660 is limited to 8 levels of directories. |
| IMAPI_E_DATA_TOO_BIG | 0xc0aab132 | Data file is too large for '%1!ls!' file system. |
| IMAPI_E_INCOMPATIBLE_PREVIOUS_SESSION | 0xc0aab133 | Operation failed because of incompatible layout of the previous session imported from the medium. |
| IMAPI_E_STASHFILE_OPEN_FAILURE | 0xc0aab138 | Cannot initialize %1!ls! stash file. |
| IMAPI_E_STASHFILE_SEEK_FAILURE | 0xc0aab139 | Error seeking in '%1!ls!' stash file. |
| IMAPI_E_STASHFILE_WRITE_FAILURE | 0xc0aab13a | Error encountered writing to '%1!ls!' stash file. |
| IMAPI_E_STASHFILE_READ_FAILURE | 0xc0aab13b | Error encountered reading from '%1!ls!' stash file. |
| IMAPI_E_INVALID_WORKING_DIRECTORY | 0xc0aab140 | The working directory '%1!ls!' is not valid. |
| IMAPI_E_WORKING_DIRECTORY_SPACE | 0xc0aab141 | Cannot set working directory to '%1!ls!'. Space available is %2!I64d! bytes, approximately %3!I64d! bytes required. |
| IMAPI_E_STASHFILE_MOVE | 0xc0aab142 | Attempt to move the data stash file to directory '%1!ls!' was not successful. |
| IMAPI_E_BOOT_IMAGE_DATA | 0xc0aab148 | The boot object could not be added to the image. |
| IMAPI_E_BOOT_OBJECT_CONFLICT | 0xc0aab149 | A boot object can only be included in an initial disc image. |
| IMAPI_E_BOOT_EMULATION_IMAGE_SIZE_MISMATCH | 0xc0aab14a | The emulation type requested does not match the boot image size. |
| IMAPI_E_EMPTY_DISC | 0xc0aab150 | Optical media is empty. |
| IMAPI_E_NO_SUPPORTED_FILE_SYSTEM | 0xc0aab151 | The specified disc does not contain one of the supported file systems. |
| IMAPI_E_FILE_SYSTEM_NOT_FOUND | 0xc0aab152 | The specified disc does not contain a '%1!ls!' file system. |
| IMAPI_E_FILE_SYSTEM_READ_CONSISTENCY_ERROR | 0xc0aab153 | Consistency error encountered while importing the '%1!ls!' file system. |
| IMAPI_E_FILE_SYSTEM_FEATURE_NOT_SUPPORTED | 0xc0aab154 | The '%1!ls!'file system on the selected disc contains a feature not supported for import. |
| IMAPI_E_IMPORT_TYPE_COLLISION_FILE_EXISTS_AS_DIRECTORY | 0xc0aab155 | Could not import %2!ls! file system from disc. The file '%1!ls!' already exists within the image hierarchy as a directory. |
| IMAPI_E_IMPORT_SEEK_FAILURE | 0xc0aab156 | Cannot seek to block %1!I64d! on source disc. |
| IMAPI_E_IMPORT_READ_FAILURE | 0xc0aab157 | Import from previous session failed due to an error reading a block on the media (most likely block %1!u!). |
| IMAPI_E_DISC_MISMATCH | 0xc0aab158 | Current disc is not the same one from which file system was imported. |
| IMAPI_E_IMPORT_MEDIA_NOT_ALLOWED | 0xc0aab159 | IMAPI does not allow multi-session with the current media type. |
| IMAPI_E_UDF_NOT_WRITE_COMPATIBLE | 0xc0aab15a | IMAPI can not do multi-session with the current media because it does not support a compatible UDF revision for write. |
| IMAPI_E_INCOMPATIBLE_MULTISESSION_TYPE | 0xc0aab15b | IMAPI does not support the multisession type requested. |
| IMAPI_E_NO_COMPATIBLE_MULTISESSION_TYPE | 0xc0aab15c | IMAPI supports none of the multisession type(s) provided on the current media. |
| IMAPI_E_MULTISESSION_NOT_SET | 0xc0aab15d | MultisessionInterfaces property must be set prior calling this method. |
| IMAPI_E_IMPORT_TYPE_COLLISION_DIRECTORY_EXISTS_AS_FILE | 0xc0aab15e | Could not import %2!ls! file system from disc. The directory '%1!ls!' already exists within the image hierarchy as a file. |
| IMAPI_S_IMAGE_FEATURE_NOT_SUPPORTED | 0xaab15f | Feature is not supported for the current file system revision, image will be created without this feature. |
| IMAPI_E_PROPERTY_NOT_ACCESSIBLE | 0xc0aab160 | Property '%1!ls!' is not accessible |
| IMAPI_E_UDF_REVISION_CHANGE_NOT_ALLOWED | 0xc0aab161 | UDF revision cannot be changed because of the previously imported session |
| IMAPI_E_BAD_MULTISESSION_PARAMETER | 0xc0aab162 | One of the multisession parameters cannot be retrieved or has a wrong value. |
| IMAPI_E_FILE_SYSTEM_CHANGE_NOT_ALLOWED | 0xc0aab163 | You cannot change the file system to be created, because the file system in the imported session and the one in the new session must match. |
| IMAPI_E_IMAGEMANAGER_IMAGE_NOT_ALIGNED | 0xc0aab200 | The image is not 2kb aligned. Only 2048 bytes aligned images are supported. |
| IMAPI_E_IMAGEMANAGER_NO_VALID_VD_FOUND | 0xc0aab201 | No valid file system Volume Descriptor was found in the iso image. This image format is not supported and the resulting disc might not be readable. |
| IMAPI_E_IMAGEMANAGER_NO_IMAGE | 0xc0aab202 | No image was set (neither path nor stream was given). |
| IMAPI_E_IMAGEMANAGER_IMAGE_TOO_BIG | 0xc0aab203 | Image size exceeds MAXLONG sectors - too big. |
| 62 entries | ||