|
- The license for this product is invalid. This error is
returned if the installed license is not valid for the current version of the product.
-
- This product is not licensed to perform this operation. A
licensed copy of the product must be installed to create patch files or packages.
-
- An invalid parameter has been passed to the function. This
is a general error which occurs when a required parameter is not passed correctly to a
function. Typically this indicates that an invalid memory address has been specified.
-
- An invalid handle has been passed to the function. This
error is returned when an invalid package handle has been specified. The handle may have
been previously closed, or contains an invalid value.
-
- No handles are available. This error is returned when all
available package handles have been allocated for the current process. A maximum of 256
handles may be opened by a process. Unused package handles should be closed, which will
release any locks on the package and free the handle.
-
- The specified buffer is too small to contain the requested
data. Increase the amount of memory allocated for the buffer and call the function again.
-
- Out of memory. All available memory on the process heap has
been allocated.
-
- Internal state error. There has been an unexpected change in
the internal state information maintained by the library. This error may indicate memory
corruption within the application.
-
- Access denied. The current process does not have permission
to access the file or resource on the local system. Accessing or updating system files may
require that the current process have administrator privileges.
-
- The current operation has been canceled.
-
- The specified file path does not exist. One or more of the
directories in the file path do not exist.
-
- The specified file could not be found on the local system.
-
- The specified file is not available. This error is returned
if the operating system has indicated that the file has been moved to offline storage.
-
- The specified file already exists on the local system. This
error is returned when a file exists and cannot be overwritten.
-
- The specified file is empty. This error is returned when any
empty file is specified as a parameter to a function which requires that the file contain
one or more bytes of data.
-
- The specified file is read-only and cannot be modified. This
error is returned when a target file has the read-only attribute set, and the option to
overwrite existing files has not been specified.
-
- The specified file has been modified. This error is returned
when an attempt is made to update a file which has already been modified.
-
- No files were found that matched the specified file name.
This error is typically returned when a file wildcard does not match any files in the
directory.
-
- No files have been modified. This error is returned when
comparing two directories, and no files have been added, removed or modified.
-
- The specified files are identical. No operation is performed
because there is no difference between the two files.
-
- The specified file name is invalid. The file name may
contain invalid characters or one of the components of the file path may not specify a
directory.
-
- The specified file path name is invalid or is not a
directory. This error is returned when a regular file name is passed as a function
parameter, or one of the components of the path is not a directory.
-
- The specified file installation path is invalid. This error
is returned when one of the components of the installation path is not a directory.
-
- The file modification time is newer than the specified time
value. This error is returned when a reference file has a newer modification timestamp
than the updated file. This indicates that the reference file has been modified after the
updated file was created or modified.
-
- The file version is newer than the specified version. This
error is returned when a reference file version number is greater than the updated file's
version number. This indicates that the reference file has been modified after the updated
file was created.
-
- The specified file version is invalid. The version number
for the file does not match the version information stored in the patch file.
-
- The specified platform identifier is invalid. This error is
returned when an invalid platform is specified as a parameter to a function, or when a
patch file contains invalid information about the platform that it may be applied on.
-
- The specified platform is not supported. This error is
returned when an attempt is made to apply a patch file on a platform that is not
supported. For example, attempting to apply a patch targeted for the Windows NT/2000/XP
platform on a Windows 95 system.
-
- The specified file has not been digitally signed or the
signature is invalid. This error is returned when it is required that a Windows PE module
(an executable, library or control) be digitally signed, but the signature is either not
present, or is not trusted on the local system.
-
- An invalid password was specified. The patch file or package
requires a password to access the file. Passwords may be of any length, and are
case-sensitive.
-
- The specified expiration period is invalid. This error
occurs when attempting to specify an expiration period that exceeds the maximum number of
days that a patch may be applied before it expires. To specify that a patch or package
file should never expire, use a value of zero.
-
- The specified patch file has expired. The creator of the
patch has limited the number of days that the patch may be applied on target systems.
-
- The specified package file has expired. The creator of the
package has limited the number of days that the patch may be applied on target systems.
-
- Unable to create the specified file path. This error is
returned when an attempt to create a directory path fails because one of the path
components already exists or the current process has insufficient permission to create the
directory.
-
- The specified file has not been created. This error is
returned when a file could not be created on the local system. The current process may not
have permission to create the file, or there may not be sufficient available disk space on
the selected volume.
-
- The specified file has not been modified. This error is
returned when a file cannot be updated on the local system. The current process may not
have permission to modify the file, or there may not be sufficient available disk space to
create a temporary copy of the file during the update process.
-
- Unable to replace the specified file. The error occurs if
the specified file is in use by another process and cannot be replaced when the system is
restarted.
-
- Unable to remove the specified file. This error occurs if
the file is currently in use and it cannot be removed after the system is restarted.
-
- Unable to extract the specified file. This error occurs if
an attempt is made to extract a file that is to be removed from the system. If a file is
to be removed, only information about the target file is stored in the package. There is
no data available to extract.
-
- The specified file does not contain compressed data. This
error is returned if the file has not been compressed, or if the data has been corrupted.
-
- The specified file could not be expanded. This error may
occur if the process does not have read permission to access the file, or if there is not
enough temporary disk space to store the expanded data.
-
- Unable to create a copy of the specified file. This error
occurs if the process does not have permission to create a copy of the file. This may
occur if process cannot read the original file, create a new copy of the file in the
specified directory, or if the destination file already exists and has the read-only
attribute set.
-
- Unable to compress the specified data stream. This error
indicates a failure in the internal data compression engine.
-
- Unable to create a backup copy of the specified file. This
error occurs if the process does not have permission to create a backup copy of the file.
This may occur if process cannot read the original file, or create the copy of the file in
the same directory as the original file.
-
- The specified patch package revert file is invalid. This
error is returned if the file does not exist, does not specify a regular file or does not
have the appropriate signature that identifies it as a package revert (undo) file.
-
- Unable to revert the previously applied package. This error
occurs when an attempt to revert an applied package has failed, and may indicate a
corrupted revert file.
-
- The specified file contains an invalid header block. This
error occurs if an incorrect file was specified or if the file data has been corrupted.
-
- The patch file was created using an unsupported algorithm.
This error occurs if a patch file was created with a later version of the library using a
different algorithm or if the patch file has been corrupted.
-
- The specified file contains an invalid checksum value. This
error indicates that the patch file data has been corrupted.
-
- The specified file is not a supported file type. This error
occurs if a directory or device file was specified instead of a regular file.
-
- The specified file contains an invalid file size value. This
error occurs when applying a patch and indicates that the original file on the local
system is not the same size as the file that was used to generate the patch.
-
- The specified file contains an invalid timestamp. This error
occurs when applying a patch and indicates that the original modification timestamp on the
local file is not the same time as the modification time for the file at the time the
patch was created.
-
- The specified file contains an invalid hunk record. This
error indicates that the patch file data has been corrupted.
-
- The specified file contains an invalid data block. This
error indicates that the patch file data has been corrupted.
-
- An invalid encryption context has been specified. This error
indicates a failure in the internal encryption engine used to create secure patch and
package files.
-
- Unable to decrypt the data stream using the specified
context. This error occurs if a patch file was created with a later version of the library
using a different encryption algorithm or if the patch file has been corrupted.
-
- Unable to encrypt the data stream using the specified
context. This error indicates a failure in the internal encryption engine used to create
secure patch and package files.
-
- Unable to create the specified file. This error occurs if
the process does not have permission to create a file in the specified directory.
-
- Unable to open the specified file. This error occurs if the
process does not have permission to access the specified file, or if the file has been
opened for exclusive access by another process.
-
- Unable to read from the specified file. This error occurs if
the process does not have permission to read the contents of the file.
-
- Unable to read the specified data block. This error occurs
if a data block cannot be read from a patch file. The process may not have permission to
read the file or the file data may be corrupted.
-
- Unable to read the specified hunk record. This error occurs
if a hunk record cannot be read from a patch file. The process may not have permission to
read the file or the hunk record chain may be corrupted.
-
- Unable to write to the specified file. This error occurs if
the process does not have permission to write to the file, or if there is insufficient
disk space to store the data.
-
- Unable to write the specified data block. This error occurs
if the process does not have permission to write to the file, or if there is insufficient
disk space to store the data.
-
- Unable to write the specified hunk record. This error occurs
if the process does not have permission to write to the file, or if there is insufficient
disk space to store the data.
-
- End of file. This error occurs when reading data and the end
of the file is encountered unexpectedly. This indicates that the file data may be
corrupted.
-
- The specified package has been opened in read-only mode. To
modify the package contents, including deleting or renaming files in the package, it must
be opened in update mode.
-
- The specified package is locked by another process. This
error occurs when another process attempts to access a package while that package is being
updated or applied on the local system.
-
- No resource table has been created for this package. This
error occurs when attempting to load a package resource and no resources have been stored
in the package.
-
- The specified package resource table is invalid. This error
indicates that the resource table in the package has been corrupted.
-
- The specified resource does not exist in the package. This
error occurs when attempting to load a resource that has not been stored in the package.
-
- The specified property value identifier is invalid.
-
- The specified property has not been defined. This error
occurs when attempting to read a package property value that has not been previously
defined.
-
- The specified file has been locked by another process. This
error is returned if a file on the target system has been opened exclusively by another
process and cannot be read. The process which has opened the file must be terminated
before applying the update.
|
|