Digital Publishing Solution (DPS 2015) is now part of Adobe Experience Manager Mobile.

This document contains solutions to messages that you can encounter while using the Migration tool to convert Digital Publishing Suite content to Experience Manager Mobile.

Error messages after clicking the Migrate button

Account has not been found or is not an application account

Details: Folios can only be migrated from an account that has an Application role.

Solution: Check that the Adobe ID of the account is correct and that it has been assigned an Application role in the DPS dashboard.

Folios in this migration request overlap with a migration that is in progress

Details: Another migration operation is in progress, which is trying to migrate the same set of folios.

Solution: Wait for the migration in progress to complete and try again.

There are too many folios in the migration request, a maximum of 25 folios are supported per request

Details: Only 25 folios or full rendition in one migration are allowed.

Solution: Either select fewer than 25 folios or select full rendition and try again.

You are not authorized to migrate content. Please contact your Project administrator.

Details: You need to have permissions to add content and run the migration.

Solution: Verify your permissions to ensure that you are allowed to add content.

There was an error with the migration request

Details: An error prevented the migration request from starting.

Solution: Try again later, or contact the Adobe Support team.

Error messages from migration logs

Folio format for "folio name" is too old, only versions 1.7.0 and later are supported.

Folio format for article "article name" in folio "folio name" is too old, only versions 1.7.0 and later are supported.

Details: Migration only supports folios or articles for version 1.7.0 and later.

Solution: Convert folio to a newer format.

Folio "folio name" is missing one of the required metadata (Product ID, Publication Date, or manifestXRef) and cannot be migrated.

Details: Folio data is incomplete; one of the parameters is missing. If published from Folio Producer, this error should not happen; if it does, contact Adobe Support.

Solution: Correct the missing data and try again.

There was a problem converting the folio "folio name."

There was a problem converting article "article name" in folio "folio name."

Details: Most of the times this error indicates a problem with migration service.

Solution: Contact Adobe Support.

Folio "folio name" is corrupt and will not be migrated.

Article "article name" in "folio name" is corrupt and will not be migrated.

Details: Usually, this error is an indication that the folio file is broken. If it is not, contact Adobe DPS Support.

Solution: Fix the broken folio and try again.

Folio "folio name" "landscape" orientation is not supported.

Article "article name" in "folio name" "landscape" orientation is not supported.

Details: The user chose the wrong orientation for folios to migrate. The user interface doesn't try to auto-detect the recommended orientation for your folios. However, sometimes it isn't possible in the premigration step, or your rendition contains both landscape and portrait orientation folios.

Solution: Choose the proper orientation and try again or ignore this error if it's not valid.

Folio "folio name;" there was a problem communicating with the Distribution Service, the operation failed after five retries.

There was a problem communicating with the Distribution Service, the operation failed after five retries.

Details: This error indicates a problem communicating with the old Distribution Service.

Solution: Retry after some time. If that doesn't solve the error, contact Adobe Support.

The folio "folio name" was not found on the Distribution Service.

Details: This error indicates a mismatch in the data that the Distribution Service returns.

Solution: Retry. If the error persists, contact Adobe Support.

Folio "folio name;" there was a problem communicating with the server, the operation failed after five retries.

There was a problem communicating with the server, the operation failed after five retries.

Details: This error indicates a problem communicating with the producer service.

Solution: Wait, and then retry. If the error persists, contact Adobe Support.

Internal server error while migrating folio "folio name;" contact Adobe Support.

Details: Usually, this error indicates a severe problem with the migration service.

Solution: Contact Adobe Support.

ID generation error while migrating folio "folio;" contact Adobe Support.

Details: This error indicates that a folio could not be migrated, because the name in the new system overlaps with an existing one.

Solution: Contact Adobe Support.

Article "article name" in "folio name" contains an invalid file and will not be migrated.

Details: This error indicates that one file in specified article has an invalid filename, characters “;” and “?” are not supported in filenames.

Solution: Update your folio and remove invalid characters.

Warning messages from migration logs

Folio "folio name" with ID "folio ID" is an invalid rendition for folio with ID "folio name," and will not be migrated.

Details: This message doesn't indicate an actual problem. Your account contains duplicate folios for the same rendition. Usually, these folios are not available from Folio Producer and you cannot delete them. Depending on different parameters, they appear in viewers, or not. If duplicate folios aren't a problem, check that the migrated folio is complete and correct, and ignore this error. 

Solution: If the wrong folio is migrated, contact Adobe DPS Support to remove invalid folios from your old DPS account and remigrate.

There are "201" articles in folio "folio name," the maximum number of migrated articles is "200" in pre-release; created collection is incomplete.

Details: This restriction is temporary, and will be removed soon. 

Solution: No workaround.

Info messages from migration logs

Collection "collection name" was created from folio "folio name"

Details: This message is a note that links old folios with collections (it is a link to a collection in AEM Mobile).

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy