E_ADEPT_REQUEST_EXPIRED workflow SIGN_IN error

This error occurs when trying to activate a reader application, typically when using a non-Adobe Vendor ID. If it is not your own Vendor ID that is causing this error to occur, please contact Support at Datalogics.

The cause of this error has to do with the SSL certificate on the vendor's authentication server. The problem with the certificate may be a subtle one. Some browsers may not see anything wrong if you visit the authentication server's status page, but other applications, such as reader apps, will see errors. You should run the SSL certificate to the strictest SSL checker you can find to try to diagnose the problem and then resolve it.

Problem / Error	Solution(s) / Info
java.lang.Error: Problem reading key and certificate from keystore	Password in fulfillment.conf may be incorrect (including extra white space) p12 (certificate) may be corrupted
E_LSGN_NO_CERTIFICATE and/or E_LIC_LICENSE_SIGN_ERROR	Certificate may be expired or corrupted There may be a hostfile redirect that's invalid The NA/EU Signing Server may be down (uncommon) If the issue is not persistent across all files, then the issue may lie with the problematic files, in which case, try replacing the files.
E_URLLINK_NO_SUCH_RESOURCE_ITEM	Check resourceitem.item and resourcekey.defaultitem in the database. Both should be set to 0.
E_ADEPT_NO_TOKEN	Certificate may be expired or corrupted Something may be wrong with the acsm file Check the fulfillment log for more info
Permissions wrong on ebook(s)	Edit the XML file used in the packaging requests. See Chapters 8 and 11 of the ACS User Manual.
java.lang.NoClassDefFoundError: Could not initialize class com.adobe.adept.packaging.pdf.PDFPackager	Remove "MD5" from the disabled algorithms in java.security file
java.lang.IllegalArgumentException: Can not set java.util.Date field com.adobe.adept.common.persist.LastCleanupData.lasttime to java.time.LocalDateTime	JDBC may need to be downgraded. ACS sets datetime fields to NULL in the mySQL DB, which is not allowed in newer versions of JDBC.
E_ADEPT_DOCUMENT_TOO_SHORT	Tomcat may not be able to access the media folder There may be a prohibitive or incorrect firewall configuration Fulfillment URL may be incorrect in config file(s) and/or resourceitem table
E_CLOUD_ACSM_UPLOAD_MISSING_PARAMETER	Harmless; has to do with an Adobe cloud sync technology that is not operational. The error can be silenced by adding this line to the fulfillment.conf: com.adobe.adept.fulfillment.enableEbookCloudUpload=false
E_ADEPT_UNKNOWN and Out of Memory Error when packaging	Check packaging.log file. If "java.lang.OutOfMemoryError: Java heap space" is there, try increasing java's heap size. You could also use the ACS datapath method to package large data files. You can find more about using datapath method in the ACS documentation included with the product, or in the Adobe Content Server Packaging Guide. See "What do I do if I run out of memory when running the Upload Test Tool?" in the Troubleshooting section.
E_ADEPT_IO and/or "IO Error on Network Request / Error #2038"	Check the description of the error message. Make sure your fulfillment server's port is open to outside internet access. Your Adobe Content Server database is set to be transactional. For MySQL, this means that all tables should use Innodb engine type. For other database types, please consult your database manual for instructions on setting up a transactional database. If you still have trouble, verify that you have the correct certificate for this fulfillment server, and check the fulfillment logfile. The book .acsm link may be expired. In this case, go to Admin Console, check the Link Exp field for the bookstore distributor by selecting the distributor under the Distributors tab. The Link Exp should not be longer than 24 days. Admin Console cannot properly set the link expiration to dates longer than 24 days.
E_LIC_NO_ITEMS_AVAILABLE	A common cause for this error is that the book being downloaded is not part of a valid distributor. The book likely still exists in the system under "All Items" within the admin console, but it was removed from the distributor specified in the fulfillment link (GBLink). To resolve this error, the book must be added back into the distributor that is being specified in the fulfillment link.
E_ACT_TOO_MANY_ACTIVATIONS	When you get this error, usually from a reader application or on a device, this means that you have exceeded the number of allowed activations.
E_ADEPT_DATABASE_NO_TRANSACTIONS	When starting Tomcat or deploying a web app, you may see this error in the log files. The most common cause is not having your database set to transactional only. To fix that, find your MySQL config file. In Windows, it's the my.ini file; in UNIX, it's my.cnf. Adding the following line to the [mysqld] section will make the database transactional only: <pre>default-storage-engine = InnoDB</pre> If you already have a line defining the default storage engine, replace it with that one. Case matters. Then, stop Tomcat, restart MySQL, then start Tomcat again.
E_ACT_NOT_READY	If you see this error while using ADE, follow these steps: Deactivate the app Close the app Restart it Reactivate If you are using ADE, and you don't see the menu option to deactivate (or to erase authorization), you can deactivate with control+shift+D in Windows. On Mac, use command+shift+D. If this doesn't work, look at this Adobe Systems help page.
E_ADEPT_SIGNIN_CONNECTION_EXCEPTION	This error occurs when trying to activate a reader application, typically when using a non-Adobe Vendor ID. If it is not your own Vendor ID that is causing this error to occur, please contact Support at Datalogics. The cause of this error has to do with the SSL certificate on the vendor's authentication server. The problem with the certificate may be a subtle one. Some browsers may not see anything wrong if you visit the authentication server's status page, but other applications, such as reader apps, will see errors. You should run the SSL certificate to the strictest SSL checker you can find to try to diagnose the problem and then resolve it.
E_ADEPT_REQUEST_EXPIRED workflow SIGN_IN error	This error can be caused by an incorrect clock time, date, or time zone, or some combination of these system settings. When you download an PDF or epub, the Adobe activation records timestamp information from the Adobe activation server. This information is stored inside the book. When you attempt to open the book, this information is compared to your current system information. If your system has an incorrect time, date, or time zone, the activation server disallows the request and you cannot read the book. Carefully check the system time, date, and time zone on your machine to make sure that they match the time/date/zone when you purchased the PDF or epub. In most cases this will solve the error.
E_PACK_INCORRECT_FORMAT	If you see this error, check the XML file used to package the book. Make sure that the metadata field dc:formatis is one of these values: application/pdf application/epub+zip or possibly application/epub Make sure that the value matches the format of the file to be packaged.
E_LIC_ALREADY_FULFILLED_BY_ANOTHER_USER	In most cases, this is a pretty basic error. It simply means that the user is trying to fulfill a book that has been previously fulfilled by a different Adobe ID. Possibly the user has several IDs and has mixed them up, or several users are sharing with the same device. Either way, it is up to the customers to make sure they are using their own download links or ACSM files. The general cause of the error is that the ACSM file has been used to download this book by another account. Make sure that ADE is signed into the original account that fulfilled this book. If you are still getting this error no matter what account you use, you must get a new ACSM file from the bookstore/provider so that you can download your book. Always check to make sure that you are not signed into ADE as an anonymous user before you fulfill your book. Anonymous users are one time use accounts and once they've been signed out all books fulfilled to this anonymous user would be permanently unreadable. Trying to use the ACSM file again under a different account, anonymous or not, would present this error.
E_PACK_DUPLICATE_SRC	This error occurs during packaging when the resource ID provided for packaging conflicts with an existing resource. If you're not trying to replace an existing book, the solution would be to simply change the ID you're providing, or omit it altogether since ACS will assign one automatically. If you are trying to replace a book, make sure that your packaging configuration file allows for replacements. Add the line provided below if it is missing, or make sure it's set to "true." Be sure to restart Tomcat (or your equivalent server software, if necessary) after any change to a configuration file. com.adobe.adept.packaging.allowURLCollisionsOnReplace=true After you complete the change, make sure that you're specifying that this book is supposed to be a replacement. If packaging from the command line is using the Upload Test tool, add this line to the top of your book's corresponding XML file, right after the <packaging...> element: <action>replace</action> If you're forming and sending the web request directly to the packaging server using your own methods, add the action attribute to the packaging element instead, like this: <package xmlns="http://ns.adobe.com/adept" action="replace">
E_URLLINK_NO_DISTRIBUTION_RIGHTS error from ADE or ACS	The error message E_URLLINK_NO_DISTRIBUTION_RIGHTS usually appears when a book to be downloaded has not been assigned to a distributor on the Adobe Content Server or the book has not been assigned the requested distributor rights permissions. Usually the Adobe Digital Editions returns this error to the user. In ADE, you may see this error: Unable to download. Error getting License. License Server Communication Problem: E_ADEPT_NO_TOKEN. You can also see this error by opening the problematic ACSM file. In the returned ACSM file from Adobe Content Server (ACS), you may see the following content: <error xmlns="http://ns.adobe.com/adept" data="E_URLLINK_NO_DISTRIBUTION_RIGHTS urn:uuid:d07cd8da-ab8c-491d-87da-b63735712dd3 buy http://.../fulfillment/URLLink.acsm"/> There are several reasons why a book might not have been added to the appropriate distributor's book catalog on the server side. The book was not added to a distributor when the book is newly packaged (uploaded). A book is deleted and then re-added, and the user forgot to add the book to the distributor again. When the book is removed then repackaged using the same resource ID, you will need to make sure to assign the book to the distributor again. When the book is deleted it is deleted from the distributor's list as well. So after the same book is added back (either by adding or replacing), it is necessary to re-assign the book to the appropriate distributor. Check the distributor rights. For example, if you're getting the same error as above but with the word "loan" instead of "buy" between the resource ID and the URL, you need to make sure you've set up a separate distribution right for the book to be loanable. This distribution right should be named "loan" and should allow the book to be returnable with a certain number of copies available (or -1 for unlimited). Ensure that the RESID in the GBLink matches the ID of the book in the database/admin console. If a book was [re]packaged and uploaded where an identical one already exists it might have acquired a new RESID. Make sure the new one is added to the correct distributor and the old one is removed or handled correctly. If you have already sent the book metadata including its resource ID to the store catalog, there is no need to update the store catalog as long as the resource ID and other metadata stay the same after you repackage the book.
E_ADEPT_MISSING_ELEMENT	If you see this error when fulfilling a book, make sure that there are no blank spaces or other special characters in the GBLink URL that might terminate the URL prematurely before all parameters can be processed by the web server. For example, the link might look like this: http://..:8080/fulfillment/Fulfill expiration When it is supposed to look like this: http://..:8080/fulfillment/Fulfill_expiration
E_PACK_FILE_READ "Permission Denied"	This error appears during packaging. The error output will say E_PACK_FILE_READ, followed by the book file's full path, and the string "(Permission denied)". The most likely cause of this error is that the file does not have proper read permissions. For Unix systems especially, check the permissions on each of the book files, and for the directory where they are stored. Make sure that the title has full read permissions to ensure that packaging works. Even with seemingly proper permissions, however, the error may still occur based on the file's location in the system. Sometimes, if the book is stored in a subdirectory of /root, this error might appear. Moving the book file from /root to /home might solve this problem.
E_URLLINK_AUTH error from ACS download link	This error can happen when you try to download an ebook from the download link. Adobe Digital Editions may display the E_URLLINK_AUTH error. If you open the .acsm file associated with the download, the file may contain the error code: <error xmlns="http://ns.adobe.com/adept" data="E_URLLINK_AUTH http://yourebook. domain.com/fulfillment/URLLink.acsm"/> If you see this error, it usually means that the download link is not generating properly. If you are a reader, please contact your ebook provider. If you are the provider, please check the download link or GBLink for the following: The store name, or distributor name, also known as the field ordersource in the link, matches the distributor's name in ACS. The shared secret used to sign the link is indeed the shared secret for this distributor. For the application code to generate the GBLink, make sure that the shared secret is base64 decoded. In the application code, make sure that only the portion of the link after the "URLLink.acsm?" is signed. Do not include the URL address up to the question mark. If you still have problems in your own GBLink generation, make sure that the sample bookstore works with the same distributor. See the ACS Quick Start and the User Manual for detailed instructions on how to set up the bookstore. Both of these documents are provided with the ACS software installation package.
E_LIC_WRONG_OPERATOR_KEY	If you see this error when trying to fulfill a book from Adobe Content Server, the likely reason is that your fulfillment URL in the fulfillment config file does not match the fulfillment URL created by Datalogics. Please compare the URL you have in your fulfillment config file to the one used to create the certificate by Datalogics. This information is provided usually with the certificate from Datalogics. Some of the common causes are listed below. If you believe that the URL you are using is correct, contact our support team. Please send the fulfillment config file and the certificate p12 file so we have the information needed to investigate the issue. Common causes of mismatches are: You have multiple certificates for different URLs, please check to make sure that you are using the right URL, p12 file and the password. The port number doesn't match, or is missing either from the certificate or the fulfillment config file. There is a trailing white space at the end of the URL in your fulfillment config file after the URL. There is a subfolder added or missing from the URL. It is common to have requested the certificate one way but installed it another. You are using https not http. Trailing white space at the end of the URL when the certificate is created.
E_ADEPT_CORE_LOAN_SIGNATURE	This error may occur after Adobe Content Server signing a server switch, so as to switch from the EU Adobe Signing Server to the NA server, for example. We offer a few suggested solutions below. While the steps below have been known to solve the issue, it is possible that not all steps are required. Regardless, this seems to be a client issue in ADE: Delete manifest.xml from the "My Digital Editions" directory on the client machine. Restart Digital Editions. This will regenerate that file. Delete temporary internet files, cookies, etc. for your browser. De-authorize ADE (Ctrl+Shift+D on Windows) Re-authorize ADE Download a book. It should now work. A totally clean reinstallation of ADE may work as well: Uninstall ADE using either a program manager or the uninstall file itself. Remove the "My Digital Editions" directory. Download and install the latest version of ADE.
E_PACK_ERROR null error from packaging books in ACS	If you get the E_PACK_ERROR with the following sample detailed message: <error xmlns="http://ns.adobe.com/adept" data="E_PACK_ERROR http://acs.com:8080/packaging/Package null"> And your packaging file contains the follow trace log: 03 may 2012 13:40:23,081 ERROR Package: Error in packaging java.io.IOException: No META-INF/container.xml found at com.adobe.adept.packaging.epub.EPubPackager.readOCF(EPubPackager.java:182) at com.adobe.adept.packaging.epub.EPubPackager.loadFile(EPubPackager.java:689) at com.adobe.adept.packaging.epub.EPubPackager.(EPubPackager.java:137) Please check the Java version you are using. If you are using an older version, upgrading Java may resolve this issue.
E_LIC_CONNECTION_PROBLEM	Typically, this error occurs when ACS can't connect to the Adobe Signing Server and will be indicated by a red X on the fulfillment status check. First, make sure that the signing server URL is entered correctly in the fulfillment configuration file, and that the NA server is being used: https://nasigningservice.adobe.com/licensesign Adobe Systems has renewed their SSL certificate and has entered the server URL in upper case. For servers with a locale of EN_US, this isn't a problem. Other servers may be case sensitive. In that case, you may see this error in the log files: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching nasigningservice.adobe.com found. If so, the server URL in the fulfillment config file should be entered in uppercase like this: https://NASIGNINGSERVICE.ADOBE.COM/licensesign If the error persists, look at the Tomcat log file and the fulfillment log file. One of these log files might provide further details on the cause of the failed check.

ACS Errors and Troubleshooting