Upgrading ACS from 4.0 to 4.1 or 4.2, and to 5.0, 6.0, and 6.5

ACS 6 has added a few database fields to support new business models. These changes should be added to the database schema automatically after you update the WAR files from ACS versions 4.1 and above.

Since Version 5.0, Java 1.7 is required. Previous versions of ACS were compatible with Java 1.5 and 1.6, but version 5 and 6 require that you upgrade to Java 1.7. We recommend that you upgrade Java first, confirm that the rest of your system still functions as expected, then upgrade ACS.

There shouldn't be any changes required in your store to continue using ACS after upgrading to newer versions of ACS, including ACS 6. There are new business models supported in ACS 6. However, none of these new models require changes from how you interface with ACS services.

To update (upgrade) Adobe Content Server from 4.0 to 4.1 or newer versions, please follow the instructions in the User Guide to migrate the database properly first. There's one additional step discussed at the end of this solution. Also, always make sure that the database is set to be transactional.

In 4.1, there is a subtle change in how the status check is performed. Status executes by (amongst other things) calling certain URLs on its own service, essentially to make sure that calls over the web service interface will operate properly. In 4.1, those certain URLs are constructed to go to “localhost”. If you are binding your Tomcat to a specific address (for example, the fulfillment server address), you need to configure to allow localhost calls to see status check complete, by adding something like this:

<connector address="" port="8080" protocol="HTTP/1.1" connectiontimeout="20000" redirectport="8443"></connector>

to your Tomcat server config file.

After you are done with the database migration, before you copy over the war files from the 4.1 version, make sure that you follow these steps:

  • Stop the Tomcat services.
  • Remove the folders: admin, fulfillment and packaging from Tomcat's Webapps folder. If you've made any changes to the properties file in those folders, back them up first.
  • Remove the older versions of 3 war files.
  • Copy over the new war files.
  • Restart Tomcat services.

If you're updating from version 4.0 to newer versions, you can follow the same database migration for upgrading to 4.1. If the migration ran successfully, there is no need to use the intermediate versions first; you can go directly to the latest version once the database migration is complete. All newer versions, 4.2, 5.0 and 6.0, will make the database changes when the service starts again.

It is critical that you delete the old ACS servlet folders before starting Tomcat with the new war files.

Adobe Content Server

  1. Adobe Content Server
  2. Release Notes
  3. System Requirements
  4. Upgrading ACS from 4.0 to 4.1 or 4.2, and to 5.0, 6.0, and 6.5
  5. Adobe Content Server: General
  6. ACS and eCommerce Stores
  7. Activations in Adobe RMSDK and Adobe Digital Editions
  8. Adobe Vendor ID specifications
  9. Vendor ID Workflow
  10. Changing the fulfillment URL in ACS
  11. Developing and Using Packaging Tools in ACS
  12. Adding Digital Rights Management (DRM) permission tags to eBooks when packaging them
  13. How does passhash work in Adobe Content Server and RMSDK reader applications?
  14. Join Account Workflow and Multiple Activations
  15. Opening NOOK books in Adobe Digital Editions
  16. PDF Compatibility, Adobe Digital Editions and Adobe Content Server
  17. Removing the Adobe Digital Edition authorization when it fails (erase authorization)
  18. Replacing an Existing Book in ACS
  19. Setting up ACS with Microsoft SQL Server Database
  20. Setting up Books for Loan in ACS
  21. Working with EPUBVER
  22. Working with Readium
  23. Adobe Content Server: Errors and Error Messages
  24. Admin Console Login Error
  25. Admin Console in ACS not handling large numbers of books
  26. Could not load database driver, ACS Status check 404/500 error
  27. E_ACT_SCHOOL_MODEL_INCOMPATIBLE_SOFT error, incorrect version of ADE
  28. E_ADEPT_CORE_LOAN_SIGNATURE error from Adobe Content Server
  31. E_ADEPT_DOCUMENT_TYPE_UNKNOWN error from ADE or other readers
  32. E_ADEPT_IO error from Adobe E-Book Reader Applications
  33. E_ADEPT_MISSING_ELEMENT from Adobe Content Server
  34. E_ADEPT_NO_TOKEN error Getting License: License Server Communication Problem:
  35. E_ADEPT_REQUEST_EXPIRED: Ebook download error from ADE or other e-readers
  37. E_ADEPT_UNKNOWN and Out of Memory error from ACS packaging
  39. E_LIC_CONNECTION_PROBLEM or Adobe Signing Server returns No Running error
  40. E_LIC_LICENSE_SIGN_ERROR from Adobe Content Server
  41. E_LIC_WRONG_OPERATOR_KEY Error from Adobe Content Server
  42. E_PACK_DATABASE Error from Adobe Content Server packaging
  43. E_PACK_DUPLICATE_SRC Packaging Error
  44. E_PACK_ERROR "MALFORMED" or "NullPointerException"
  45. E_PACK_ERROR null error from packaging books in ACS
  46. E_PACK_INCORRECT_FORMAT error from packaging
  47. E_URLLINK_AUTH error from ACS download link
  50. EPUB file failed to package - Error about incorrect language field
  51. Foreign Key Constraint Error when trying to delete resources in ACS
  52. Fulfillment status check 500 error - P12 BadPaddingException: Given final block not properly padded
  53. Fulfillment status check returns HTTP error code -500 or 404
  54. GBLINK_AUTH_SIGNATURE_NOMATCH error with ACS GBLink sent through email
  55. IO Error on Network Request? Error #2038
  56. Java Memory Error, Packaging Large Files
  57. Login Error: Change or Reset Admin Console Password
  58. MySQL error in your SQL syntax, check manual for “????”
  59. Packaging error, E_PACK_FILE_READ Permission Denied
  60. Print or copy permission shows zero pages in ADE on second device or computer
  61. Required Property Missing, ACS Status Check returns 404 error
  62. Unexpected end of ZLIB input stream
  64. XMLSigningSerializer.php generates incorrect <hmac> code in ACS

Feedback and Knowledge Base