mirrors/acsm-calibre-plugin
mirrors/acsm-calibre-plugin
1
0
Fork 0
mirror of https://github.com/Leseratte10/acsm-calibre-plugin.git synced 2024-12-22 09:19:55 +06:00
Code Issues Projects Releases Wiki Activity

Create error page

Florian Bach 2021-12-17 14:13:43 +01:00
parent d73bec53a7
commit d33bec78fc
1 changed files with 474 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

474
Adobe-error-codes.md Normal file

@ -0,0 +1,474 @@
This page is supposed to contain a full list of all Adobe ADEPT errors and warnings, including their cause and potential solutions.
### E_ACT_CERTIFICATE_SYNTAX
This error occurs if the activation service certificate is invalid and can't be parsed properly. This either means your authorization got corrupted (try to de-authorize ADE, then try again), or it's an Adobe server issue.
If this happens with the Calibre plugin, please open a bug report.
### E_ACT_CERTIFICATE_INVALID
This error occurs if the activation service certificate can be parsed correctly, but isn't authorized to act as activation certificate. This either means your authorization got corrupted (try to de-authorize ADE, then try again), or it's an Adobe server issue.
If this happens with the Calibre plugin, please open a bug report.
### E_ACT_NOT_READY
This error occurs when the RMSDK is unable to find a proper user record for book fulfillment. This may mean that the application developer failed to call `setUser()`, or that the user data has somehow gotten corrupted. If you're an end user and you're getting this error message in ADE, try de-authorizing ADE and authorize it again. If you're getting this error in the Calibre plugin, please open a bug report and attach the log file.
### E_ACT_SCHOOL_MODEL_INCOMPATIBLE_SOFT
This error occurs with books with the new "school" licensing model which is only supported in RMSDK11 or newer. If you're trying to fulfill such a book in older versions, you'll receive this error message. You'll need to update to at least RMSDK11 / ADE 4.0 to be able to fulfill and open this book.
### E_ACT_TOO_MANY_ACTIVATIONS
This error occurs while trying to authorize a new computer or eReader. It means that you've exceeded the maximum amount of devices on your account (which seems to be 6 computers + 6 eReaders, plus one additional computer and eReader each year). To fix this issue, you'll either need to use a new AdobeID (which would mean you no longer have access to the books linked to the previous AdobeID), or you can try contacting the [Adobe support](https://helpx.adobe.com/support/digital-editions.html) and ask them to reset the activation count for your AdobeID.
Note that even with the error `E_ACT_TOO_MANY_ACTIVATIONS` it is possible to grab the eBook decryption key from Adobe's servers for DRM removal; for more details see the `get_key_from_Adobe.py` script in the repository.
### E_ADEPT_BAD_USER_CREDENTIALS
This error occurs if ADE thinks it should be authorized, but then fails to find the corresponding user data. Try de-authorizing ADE, then authorize it again. If you receive this error in the Calibre plugin, please open a bug report.
### E_ADEPT_CORE_ACTIVATION_TOKEN_EXPIRED
ADE / the Adobe servers support a time-restricted authorization, meaning, you can authorize a computer to your AdobeID and have this authorization automatically disable after a given time. This error is what occurs after the activation is expired.
### E_ADEPT_CORE_ACTIVATION_TOKEN_SIGNATURE
This error occurs when the signature of the activation token is invalid. Try de-authorizing ADE and authorize it again if that happens. If this occurs with the Calibre plugin, please open a bug report.
### E_ADEPT_CORE_BAD_LICENSE_CERTIFICATE
This error occurs when the license certificate cannot be parsed. If this happens, try to re-authorize ADE.
### E_ADEPT_CORE_BAD_PRIVATE_LICENSE_KEY
This seems to occur when the private key for the user account is invalid. Seems to be an internal error state. If this continues to occur, try de-authorizing ADE, then authorize it again.
### E_ADEPT_CORE_DECRYPT_LICENSE_KEY
This error means that while the book you tried to open is licensed to your AdobeID, the application was still unable to decrypt the encrypted license key included in the rights.xml file. The most common cause for this is that you're trying to open a book with the new Adobe DRM (ADE 3.0 or newer) in an older application that doesn't yet support the new DRM. Try opening the file in a newer version of ADE, or in a reader application based on RMSDK10 or newer.
### E_ADEPT_CORE_DEVICE_NOT_ACTIVATED
Currently there's no information about this error.
### E_ADEPT_CORE_ENC_MISMATCH
Currently there's no information about this error.
### E_ADEPT_CORE_INVALID_ENCRYPTED_KEY
This error occurs if the encrypted license key in the rights.xml file is invalid (too short or something). Try re-downloading the book if that happens.
### E_ADEPT_CORE_INVALID_PUBLIC_LICENSE_KEY
Currently there's no information about this error.
### E_ADEPT_CORE_KEY_INFO_INVALID
The "keyInfo" field of the "encryptedKey" tag has an unexpected value. The value will be included in the detailed error message.
### E_ADEPT_CORE_KEY_MISMATCH
Currently there's no information about this error.
### E_ADEPT_CORE_KEY_SCRAMBLE
Currently there's no information about this error.
### E_ADEPT_CORE_LICENSE_SIGNATURE
This error means that the fulfillmentResponse license (or the license included in a book) is most likely correctly signed with the distributor's certificate, but the distributor's certificate hasn't been signed by Adobe. Most likely this is an issue with the distributor (or with Adobe) and nothing you can fix yourself. If this doesn't happen during download but while opening a book you've already downloaded before, try re-downloading it.
### E_ADEPT_CORE_LOAN_CERT_MISSING
This error means ADE can't find the certificate to validate a loan token signature.
### E_ADEPT_CORE_LOAN_SIGNATURE
The exact reason for this error is unknown (yet), but it seems to be a client issue in ADE, with it getting confused as to which certificates to use. Try uninstalling ADE and re-installing it, and if this doesn't help, de-authorize and authorize it again. If you're getting this error in the Calibre plugin, please open a bug report.
### E_ADEPT_CORE_LOCKBOX_DECRYPT
Currently there's no information about this error.
### E_ADEPT_CORE_LOCKBOX_DESCRAMBLING_FAILED
Currently there's no information about this error.
### E_ADEPT_CORE_LOCKBOX_FORMAT
Currently there's no information about this error.
### E_ADEPT_CORE_MISSING_LICENSE_CERTIFICATE
Currently there's no information about this error.
### E_ADEPT_CORE_NO_DEVICES
This error happens when ADE cannot find device information to manage an existing authorization. Try re-authorizing ADE if this happens.
### E_ADEPT_CORE_NO_LICENSE
Currently there's no information about this error.
### E_ADEPT_CORE_NO_LICENSE_URL
This seems to occur if ADE fails to extract the licenseURL from a rights.xml object. Try re-downloading the book if this occurs.
### E_ADEPT_CORE_NO_LOCKBOX
Currently there's no information about this error.
### E_ADEPT_CORE_OPERATOR_MISMATCH
This happens if the operatorURL for a given book doesn't match what ADE expects. If that happens, try to re-download the book.
### E_ADEPT_CORE_PASSHASH_NOT_FOUND
This error occurs if the PassHash credentials (B&N) are invalid.
### E_ADEPT_CORE_USER_NOT_ACTIVATED
This happens when ADE is not activated while opening a document. Seems to be an internal error state that isn't communicated to the user?
### E_ADEPT_DATABASE_NO_TRANSACTIONS
This is an error on the distributor's server. More specifically, their database server is misconfigured and not in transactional mode. If you're an end user, there's nothing you can do to fix this. Contact the distributor for help.
If you are the distributor, add the following configuration to the `[mysqld]` section of your MySQL config file (my.cnf or my.ini), then restart the database server: `default-storage-engine = InnoDB`
### E_ADEPT_DATABASE_UPGRADE_NOT_SUPPORTED
This error occurs if the distributor has recently updated the ACS server to a new version and there's issues with database migration. If you're an end user, there's nothing you can do to fix this. Contact the distributor for help.
If you are the distributor, check the ACS log file for more details on what exactly failed with the database upgrade.
### E_ADEPT_DISTRIBUTOR_AUTH
This error message occurs during fulfillment of a book, if the book distributor doesn't have your AdobeID account information in the database. ADE (and this plugin) usually catch this error and automatically trigger a new /Auth request to that distributor. If a fulfill request results in this error message anyways.
If this error happens in ADE and it occurs with all books, your activation might be broken. Try removing the existing authorization and re-authorize ADE. If this error happens in the plugin, or it happens in ADE but only with one particular book, this is most likely an issue with how the ACSM file was created, which means, the book distributor has to fix this issue.
### E_ADEPT_DOCUMENT_CREATE_ERROR
This seems to be an internal ADE error state that happens when ADE is unable to initialize the document rendering library.
### E_ADEPT_DOCUMENT_OPEN_ERROR
This occurs when ADE is unable to open the downloaded document. Check if it's corrupted, maybe try re-downloading it. Otherwise it looks like a bug in ADE.
### E_ADEPT_DOCUMENT_EMPTY
This error occurs when the downloaded document / book file is empty and ADE cannot check its mime type. Try downloading the book again.
### E_ADEPT_DOCUMENT_TOO_SHORT
This error occurs when the downloaded document / book file is too short for ADE to reliably detect the mime type. Try downloading the book again.
### E_ADEPT_DOCUMENT_TYPE_UNKNOWN
This error doesn't usually mean that the program was unable to figure out the document type, it more likely means the program was unable to download the encrypted book from the distributor's servers at all.
If you're an end user, make sure the internet connection on your device works properly, and that no Internet Security software is blocking the access to download the books. If you are using ADE 1.7.2 or older, this might also be an issue with HTTPS.
If you are the distributor, perform the usual checks on your webserver. Check if the media URL is set correctly, check if the webserver has read access, and restart the webserver if there's still issues.
### E_ADEPT_INVALID_FULFILLMENT_ITEM
Currently there's no information about this error. If you do receive this error with the Calibre plugin, please open a bug report.
### E_ADEPT_IO
This error can unfortunately have different reasons. It can mean that you don't have a proper internet connection or that it's getting filtered by some software, or it can mean that there's an issue with the book distributor's servers.
If you are the distributor, check the following things:
* Make sure your database is in transactional mode - for more details, see [E_ADEPT_DATABASE_NO_TRANSACTIONS](#E_ADEPT_DATABASE_NO_TRANSACTIONS)
* Make sure your fulfillment server has the correct certificate - for more details, see [E_LIC_LICENSE_SIGN_ERROR](#E_LIC_LICENSE_SIGN_ERROR)
* Check the fulfillment log file for additional error messages.
### E_ADEPT_MISSING_ELEMENT
If you're receiving this error in a known-good application (like ADE or this plugin), it usually means that the URLLink download link was corrupted or got trimmed. Try re-downloading the ACSM file.
If you're developing your own application to connect to Adobe's servers, this means that one of the mandatory elements / tags in the XML request is missing. The detailed error description, if present, usually tells you which element is missing if that's the case.
### E_ADEPT_NETWORK
This error occurs when a network request returned invalid data or failed completely. It usually means there's an issue with your internet connection (check if there's firewalls or security software blocking the connection), but it can also mean that there's a server issue.
### E_ADEPT_NO_ANONYMOUS_USER
This occurs if you're trying to link an anonymous authorization to an AdobeID, but Adobe thinks that your anonymous authorization is already an AdobeID-based authorization. This error is similar to [E_AUTH_USER_ALREADY_REGISTERED](#E_AUTH_USER_ALREADY_REGISTERED), with the difference being that with `E_ADEPT_NO_ANONYMOUS_USER` the client already knows the authorization change is not going to work, while with `E_AUTH_USER_ALREADY_REGISTERED` it's the server that denies the link request.
### E_ADEPT_NO_FULFILLMENT_RESULT
This error occurs during fulfillment if ADE is not happy with the response from the server, meaning, it received neither an `<error>` nor a `fulfillmentResult` token. This is an error with the distributor's server and nothing you can fix yourself.
### E_ADEPT_NO_OPERATOR_URL
This occurs during fulfillment if the `<operatorURL>` tag in the ACSM file is missing or corrupted. Try re-downloading the ACSM file, if that doesn't help you'll need to contact the distributor.
### E_ADEPT_NO_TOKEN
This error occurs during fulfillment and it means that the software was unable to find the fulfillmentToken inside the ACSM file, or that there were any errors parsing the ACSM file. If you know how XML works you can try to fix this yourself, but usually this is something the distributor needs to fix. Try to re-download the ACSM file and see if that helps.
### E_ADEPT_REQUEST_EXPIRED
This means that the ACSM file you're trying to fulfill is expired. By default, ACSM files are only valid for 60 minutes (though a distributor can change that time if they want to). Go to the book distributor's website and redownload the ACSM file again, and then it should work.
If you're the distributor, you can change the validity period in the ACS Admin Console, in the Distributor tab, in the section "Distributor Info".
### E_ADEPT_SIGNIN_CONNECTION_EXCEPTION
This error can occur if you're trying to sign in with a non-Adobe AdobeID (meaning, a Vendor ID). It usually means that the vendor's authentication server has an invalid SSL certificate. If you're an end user, there's not much you can do - try again later. If you're the Vendor ID operator, check the SSL certificate that your authentication server is using.
### E_ADEPT_UNKNOWN
As the name already implies, this is a "fallback" error code for unknown errors. Check the additional error description to hopefully figure out what it means and how to fix it.
### E_ADEPT_XML_SYNTAX
This means that there's been an invalid XML syntax somewhere. Unfortunately, the error message rarely contains information on where and why that happened...
### E_AUTH_BAD_DEVICE_KEY
This means that ADE was unable to access the device encryption key, or that the key is invalid. This can sometimes happen on MacOS if ADE is unable to access the key from the keychain. If you're on a Mac, try opening the keychain manager, then grant all applications access to the "Digital Editions" key named "deviceKey", and see if that helps.
If it doesn't, or if you are on Windows, try re-authorizing ADE.
If you receive this error with the Calibre plugin, please open a bug report.
### E_AUTH_BAD_DEVICE_KEY_OR_PKCS12
This means that either ADE was unable to access the device encryption key (see [E_AUTH_BAD_DEVICE_KEY](#E_AUTH_BAD_DEVICE_KEY)), or that it was unable to use that key to decrypt the PKCS12 certificate. This can mean (on Windows) that the Crypt entropy has changed. The easiest way to fix this is to de-authorize ADE and authorize it again.
### E_AUTH_BAD_SERVER_RESPONSE
This error occurs when the server response to a login request is missing one or more of the required fields ("user", "pkcs12", "licenseCertificate" or "encryptedPrivateLicenseKey"). This is usually an issue on Adobe's server and nothing you can fix yourself.
### E_AUTH_CERTIFICATE_SYNTAX
This error occurs if the authentication service certificate is invalid and can't be parsed properly. This either means your authorization got corrupted (try to de-authorize ADE, then try again), or it's an Adobe server issue.
If this happens with the Calibre plugin, please open a bug report.
### E_AUTH_CERTIFICATE_INVALID
This error occurs if the authentication service certificate can be parsed correctly, but isn't authorized to act as authentication certificate. This either means your authorization got corrupted (try to de-authorize ADE, then try again), or it's an Adobe server issue.
If this happens with the Calibre plugin, please open a bug report.
### E_AUTH_FAILED
This error occurs while logging in with an ADE account. If the additional error parameter is `CUS05051`, this means that your mail address or password is wrong. If the additional error parameter contains `LOGIN_FAILED`, this might indicate an issue with your 2FA setup - if you have 2FA enabled on your AdobeID account, try logging in through the Adobe website, disable 2FA, and see if that helps.
### E_AUTH_NOT_READY
This error occurs when ADE tries to perform the necessary account authorization steps out of order (technical details: authenticationServiceURL or certificate are empty while trying to log in). It usually means the activation got corrupted for whatever reason. Try de-authorizing ADE by pressing Ctrl+Shift+D, then authorize it again and see if that helps. If it doesn't, you'll need to manually cleanup the activation. On MacOS, you do that by deleting the `/Users/Library/Application Support/Adobe/Digital Editions/activation.dat` file, on Windows by deleting the `HKEY_CURRENT_USER\Software\Adobe\Adept` branch from the Registry.
If you're receiving this error with the Calibre plugin, please open a bug report.
### E_AUTH_USER_ALREADY_REGISTERED
If you authorize your computer without an AdobeID, there is a way to link this particular anonymous authorization to a new AdobeID afterwards. By doing this, your AdobeID will import the unique user UUID of your anonymous authorization. This only works if the AdobeID has never been used before and thus hasn't been assigned its own user UUID yet. If you've used the AdobeID before, linking your anonymous authorization to this AdobeID will fail with the error message `E_AUTH_USER_ALREADY_REGISTERED` as it's not possible to change the UUID of your AdobeID to the one of your anonymous authorization.
The solution to this is to create a new AdobeID and then immediately link the anonymous authorization to this new AdobeID before adding the AdobeID to a device. Or, if you don't care about the books currently linked to your anonymous authorization, you can de-authorize ADE (or the plugin) by pressing Ctrl+Shift+D, and then authorize it again with your AdobeID. Note that that means you'll lose access to all books linked to that anonymous authorization.
This error is similar to [E_ADEPT_NO_ANONYMOUS_USER](#E_ADEPT_NO_ANONYMOUS_USER), with the difference being that with `E_AUTH_USER_ALREADY_REGISTERED` the client already knows the authorization change is not going to work, while with `E_ADEPT_NO_ANONYMOUS_USER` it's the server that denies the link request.
### E_AUTH_USERID_INUSE
This error is also related to linking anonymous authorizations to an AdobeID. It occurs if the unique user UUID of your anonymous authorization has already been linked to an AdobeID. For example, if you have an anonymous authorization in the plugin, then export that to another computer so you have an identical clone of the authorization. If you then try to link that authorization to two different AdobeIDs on the two computers, you will get the error `E_AUTH_USERID_INUSE` as the anonymous authorization has already been converted to an AdobeID. In normal operation, this should never occur.
### E_BAD_LOAN_ID
This can happen while returning a Loan if ADE is unable to figure out the operatorURL for a given loan. This is usually a bug in ADE (or corrupted loan data) and nothing you can fix.
### E_IO_CANNOT_CREATE_FILE
This occurs during book download if ADE is unable to create a temporary file. Check the access rights, maybe try restarting ADE or your computer, then try again.
### E_IO_DOCUMENT_WRITE
This occurs after book download, if ADE is unable to copy the temporary file to its actual destination. Check access rights, maybe try restarting ADE or your computer, then try again.
### E_IO_NO_UNIQUE_FILE_PATH
Currently there's no information about this error.
### E_IO_TEMP_FILE_WRITE
This occurs during book download if ADE cannot write to the temporary file. Check the access rights, maybe try restarting ADE or your computer, then try again.
### E_LIC_ALREADY_FULFILLED_BY_ANOTHER_USER
This error means exactly what it says in the error name - you're trying to fulfill a book that's already licensed to another user. Maybe you mixed up different AdobeIDs, or your authorization has changed between the first fulfillment of the book and the current attempt.
If you can't figure out a solution, you can contact the distributor (book store) and request that they generate a new ACSM / a new license.
### E_LIC_CERTIFICATE_SYNTAX
This error occurs if the license / fulfillment certificate is invalid and can't be parsed properly. This is usually an issue on the distributor's servers.
If this happens with the Calibre plugin, please open a bug report.
### E_LIC_CERTIFICATE_INVALID
This error occurs if the activation service certificate can be parsed correctly, but isn't authorized to act as activation certificate. This is usually an issue on the distributor's servers.
If this happens with the Calibre plugin, please open a bug report.
### E_LIC_CONNECTION_PROBLEM
This error means that ACS failed to connect to the Adobe Signing server to verify the validity of an ACSM file. As an end user, there's not much you can do to fix this. If you're the distributor, check the Tomcat and fulfillment server log files for more details about this error.
### E_LIC_INTERNAL_ERROR
There's been an internal error like a failed assertion while handling the fulfillment result. This is usually a bug in ADE. Try restarting ADE and see if that makes the error go away. If you encounter this error in the Calibre plugin, please open a bug report.
### E_LIC_INVALID_RESPONSE
One of the required parameters in a fulfillmentResponse is missing. This might be an issue with the operator's server.
### E_LIC_LICENSE_MISSING_OR_MALFORMED
This error occurs when the license field in the fulfillment response is missing or corrupted. That's most likely an issue on the server. If you're receiving this error in the Calibre plugin, please open a bug report.
### E_LIC_LICENSE_SIGN_ERROR
This error usually occurs when the ACS server is using an invalid certificate. As an end user, there's nothing you can do about this - contact your distributor.
If you are the distributor, make sure you're using the correct signing server, make sure the fulfillment URL is correct and identical to the one in the certificate, and that you are using the correct certificate file.
### E_LIC_MALFORMED_RESPONSE
This means that the licenseServiceInfo response is malformed or missing some required components. This is usually an issue on Adobe's servers.
### E_LIC_NO_DISTRIBUTION_RIGHTS
This error means that the distributor's server has no rights to re-distribute the book. This usually means that the distributor has mis-configured their server, by either trying to generate a loan token for a bought book, or a "buy" token for a loaned book. There's nothing an end user can do to fix this.
### E_LIC_NO_ITEMS_AVAILABLE
This error means that you're trying to loan a particular book, but the distributor currently doesn't have any copies of that book available (the licenses are all loaned out to other people). Usually, the libraries' systems are supposed to catch that and don't even give you access to an ACSM file if that's the case, but if these systems fail or are configured wrong, you may encounter this error while trying to fulfill an eBook.
It can also mean that the book has been added to the ACS server incorrectly - in this case the distributor is going to have to fix that on their server, too.
### E_LIC_TOO_MANY_LICENSE_URLS
Currently there's no information about this error. If you do receive this error with the Calibre plugin, please open a bug report.
### E_LIC_WRONG_OPERATOR_KEY
This error usually means the distributor made a mistake while creating the ACSM file. Most likely, the fulfillment URL in the ACSM file and the fulfillment URL configured on the ACS server don't match, or the operator has configured the wrong p12 certificate on the ACS server. There's nothing an end user can do to fix this, this issue needs to be reported to the distributor (the one who gave you the ACSM file).
### E_PACK_DATABASE
This isn't a user-facing error, it will only be returned on the distributor's side when trying to add an eBook to the ACS server. It means that there's been an error inserting the new record(s) into the database. More information will usually be provided with the error message.
### E_PACK_DUPLICATE_SRC
This isn't a user-facing error, it will only be returned on the distributor's side when trying to add an eBook to the ACS server. It means that you're trying to upload a book with an ID that already exists on the ACS server. If you are trying to upload a new book, use a different ID. If you're trying to replace an existing book, make sure the `<action>` tag has the correct value ("replace") and that your packaging configuration file allows updating / replacing books (set `com.adobe.adept.packaging.allowURLCollisionsOnReplace=true`)
### E_PACK_ERROR
This isn't a user-facing error, it will only be returned on the distributor's side when trying to add an eBook to the ACS server. It usually means that either the book filename is invalid (or contains unsupported special characters), in this case usually combined with the string "MALFORMED" in the error details. Or, if this occurs with the string "null" in the error details, the tool was able to find and open the book file, but there's been an error with the book contents. Check the trace log for more information.
### E_PACK_INCORRECT_FORMAT
This isn't a user-facing error, it will only be returned on the distributor's side when trying to add an eBook to the ACS server. It means that the mimetype / the `<dc:format>` tag for the book is set to the wrong value. It needs to be one of `application/pdf`, `application/epub+zip`, or possibly `application/epub`.
### E_URLLINK_AUTH
This error occurs while downloading an ACSM file, before it's even imported into ADE (or this plugin). It means that the signature parameter inside the URLLink request is wrong or invalid. This is an error that the distributor (the shop you're trying to get the ACSM from) needs to fix. It usually means that they either messed up the distributor's name, either in the link or on the ACS; or that they're using the wrong shared secret value to create the signature.
### E_URLLINK_NO_DISTRIBUTION_RIGHTS
This error is almost identical to the [E_LIC_NO_DISTRIBUTION_RIGHTS](#E_LIC_NO_DISTRIBUTION_RIGHTS) error. Check that entry for more details.
### E_URLLINK_PARAMETER_SYNTAX
This error occurs while downloading an ACSM file, and it means that one of the GET parameters passed to the server has an invalid syntax, for example, additional whitespace or other invalid characters included with the data. The detailed error message usually contains information on which of the parameters / fields is invalid. If you're an end user, try redownloading the ACSM file. If that doesn't help, the distributor will need to fix this.
### GBLINK_AUTH_SIGNATURE_NOMATCH
This error means that the signature for the ACSM file download request was invalid. This usually means the link got corrupted somehow. Try re-downloading the ACSM from a fresh link.
### W_ADEPT_CORE_ACTIVATION_CERT_NOT_FOUND
This is a warning that occurs when ADE is unable to find the certificate for the activation server. The URL will be included in the error details. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_EXPIRED
This is only a warning, and it occurs in the rare case where an ACSM file is still valid (not expired), but the book file that's included only has a temporary license (like from a library) and is already expired. You will be able to download the book, but you will not be able to read it.
### W_ADEPT_CORE_DEVICE_ID_NOT_FOUND
This is a warning that occurs when ADE is unable to find the device ID in the given activation record. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_DEVICE_TYPE_MISMATCH
This is a warning that occurs when the device type in the given activation record is not what ADE is expecting. The corresponding deviceID may be included in the error message. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_DUPLICATE_LOAN_TOKENS
This happens with duplicate loan tokens. ADE will automatically remove one of the duplicates.
### W_ADEPT_CORE_EXPIRED
This warning seems to occur when (trying to) open a loaned book that's already expired.
### W_ADEPT_CORE_FINGERPRINT_MISMATCH
This is a warning that occurs when the fingerprint in the given activation record is not what ADE is expecting. The corresponding deviceID may be included in the error message. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_INVALID_ACTIVATION_SERVICE_INFO
This seems to occur when the activationServiceURL or Certificate is empty. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_INVALID_CREDENTIALS
This is a warning that occurs when ADE is unable to read data (the exact missing data is given in the detailed error description) from the user object. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_INVALID_EXPIRATION
This warning occurs when ADE is trying to parse an expiration date and the data seems to be invalid.
### W_ADEPT_CORE_INVALID_LOAN_TOKEN
This warning occurs if the loan token signature is invalid.
### W_ADEPT_CORE_LICENSE_CERT_NOT_FOUND
This occurs when ADE fails to find a certificate for a given license when opening a book. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_LOAN_NOT_ON_RECORD
This warning occurs when opening a loaned book, but the loanID hasn't been found in the user's loan token.
### W_ADEPT_CORE_LOAN_TOKEN_NOT_FOUND
This warning occurs when opening a loaned book, but the particular loan token hasn't been found in the user object.
### W_ADEPT_CORE_NO_LOAN_TOKENS_FOUND
This warning occurs when opening a loaned book, but there are no loan tokens in the user object.
### W_ADEPT_CORE_USER_CREDENTIALS_NOT_FOUND
This is a warning that occurs when ADE did find a userID in the given activation record, but was unable to find the matching user in its database. The corresponding userID may be included in the error message. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_USER_ID_NOT_FOUND
This is a warning that occurs when ADE is unable to find the user ID in the given activation record. The corresponding deviceID may be included in the error message. This may be intended - no idea in which cases this warning is legitimate and in which cases it's not.
### W_ADEPT_CORE_WRONG_DEVICE
This warning occurs when you're trying to open a book on a particular device but the book is linked to a different device (under the same account).
### W_ADEPT_CORE_WRONG_DEVICE_TYPE
This warning occurs when you're trying to open a book, but that book isn't valid for your current device type.