# Troubleshooting your migration This section lists solutions to error messages that may display during migration. Any text below that is inside curly brackets `{}` will be replaced with the exact value or name of your entities. On the main import page, you can click the blue icons to review an entity in a new tab. ![Main import details page, entity with warning](https://help.qlik.com/en-US/nprinting/February2025/Content/Resources/Images/ui_migrate_ResultsWarn.png) If an entity has error or warning messages, solve them, and go back to the import page. ![PixelPerf report with migration warning](https://help.qlik.com/en-US/nprinting/February2025/Content/Resources/Images/ui_migrate_EntityWarning.png) ## Main import page The following messages are only displayed on the main migration page. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Unsupported NSQ file version. Please open the NSQ project with NPrinting 16, then save and export it again. You are trying to import a QlikView NPrinting 16 project with the .nsq file saved in an old format. To solve: 1. Open the original .nsq file in a recent QlikView NPrinting 16 version. 2. Save it, even if you did not modify anything, to force the conversion to a supported format 3. Export the project again. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The NPrinting 16 project does not contain any connections. You are trying to import a QlikView NPrinting 16 project without any connections. To solve: Check the connections in QlikView NPrinting 16, and export the project again. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The uploaded file is not a valid NPrinting 16 exported project You are uploading an exported project file (.zip) that does not contain an .nsq file. To solve: Export the project again in QlikView NPrinting 16. ## Filters [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter variable import failed: {name} The import of a variable filter failed. Check that the variable `{name}` exists in the related .qvw. To solve, try one or more of the following: * Create the variable in the .qvw and refresh the connection cache. * Modify the filter, in order to avoid using the variable. * Delete the filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter field import failed because linked fields are not supported: {name} Linked fields are not supported in Qlik NPrinting November 2019 or newer. To solve: Manually modify the filter to use the original fields from different connections. The filter will work as expected, but can not be applied as a level, page, or cycle. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter bookmark import failed because QlikView bookmarks are not supported: {name} Bookmark filters are not supported by Qlik NPrinting November 2019 or newer. To solve: Manually modify the filter to recreate the bookmark using the original fields. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Fields with 'Lock' applied are not supported. This filter may behave differently than the original: {name} The QlikView lock field option is not supported in Qlik NPrinting November 2019 or newer. To solve: Manually update the created filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Cannot import field: {name}. This QlikView field is used in multiple fields: {qvId} QlikView NPrinting 16 filters that use the same field more than once are not supported in Qlik NPrinting November 2019 or newer. To solve: Manually update the generated filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Cannot import filter variable: {name}. This QlikView variable is used in another filter: {qvId} QlikView NPrinting 16 filters that use the same variable more than once are not supported in Qlik NPrinting November 2019 or newer. To solve: Manually update the generated filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Field skipped because it has no values: {name} You are trying to import a filter without field values, which does not have the Clear all selections option flagged. To solve: Manually add the field in the newly created filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter field import failed: {name} The connection to the field `{name}` does not exist in the imported QlikView NPrinting 16 project. To solve, try one or more of the following: * Manually update the imported filter. * Delete the filter. * Update the QlikView NPrinting 16 project, export it, and import it again. ## Reports [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Report filter import failed: {name} The import of the filter `{name}` associated with the report failed because the filter was not found. To solve: Manually create the missing filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Report object filter import failed: {name} The import of the filter `{name}`, used in the report as an object filter, failed. To solve: Manually create the missing filter, and add it as an object filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Report condition import failed: {name} The import of the condition `{name}` associated with the report failed. To solve: Manually create the missing condition, and add it to the report. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Customizing 'Field to add report name' when cycling is not supported: {name} In Qlik NPrinting 19 November or newer, you cannot add the value of a field to the report file name if it is different than the field used in the cycle. To solve: Manually modify how the report file name is created using supported dynamic naming features. See: [Cycling your reports](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/ReportsDevelopment/Cycling-your-reports.htm) and [Dynamic report names](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/ReportsDevelopment/Dynamic-report-naming.htm). [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter needs to be verified: {name} An entity is using the filter `{name}` that has errors or warning messages. To solve: Resolve the errors or warning in the filter `{name}`. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Connection not found: {name}. It is related to the cycle field: {field} The connection `{name}` of the field `{field}` used in a cycle is missing. To solve: Manually add the cycled field. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Connection not found: {name}. It is related to a variable used in dynamic naming: {variable} The connection `{name}` to the variable `{variable}` used in dynamic naming is missing. To solve: Manually update the dynamic naming configuration by adding the variable. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### QlikView variable used in dynamic naming not found: {name} The QlikView variable `{name}` used in dynamic naming is missing. To solve: Manually update the dynamic naming configuration. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Unsupported variable type: {name} The type of the variable `{name}` used in the imported dynamic naming configuration is not supported. To solve: Open the report and edit the dynamic naming configuration. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### QlikView object not found: {name} The QlikView object `{name}` used in the report template is missing. To solve: Recreate the object in the source .qvw and regenerate the connection cache. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Error reading QlikView entity A generic error occurred while reading a QlikViewentity. The error exists the imported QlikView NPrinting 16 project. To solve: 1. Open the entity that generates the error. 2. Update the entity and make sure it is working properly. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### No template file was found for this report The report template file is missing. To solve: * Check that the template file is present in the source QlikView NPrinting 16 project. It is a file-based system, so the template may have been deleted from the original templates folder. In this case, you must retrieve it from a backup or recreate it in the Qlik NPrinting installation. * Check that the QlikView NPrinting 16 report contains the correct path to the template included the filename. The syntax could have been modified to an incorrect value. * If you find the file in the QlikView NPrinting 16 templates folder, you can manually create the report in your Qlik NPrinting installation and use it as custom template. Then: * Open it in the Qlik NPrinting Designer and add the needed QlikView entities in the treeview, or * Export and import the QlikView NPrinting 16 project again, and verify the template is correct. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Template conversion failed The report template conversion failed. To solve: 1. Open the template in Qlik NPrinting Designer. 2. Solve the error messages that appear. 3. Click on Save and Close. This will force the conversion to run again. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Some entities in this report are not present in the connection cache Some entities used in the template are missing from the connection cache. To solve: 1. Open the template in Qlik NPrinting Designer to get a detailed list of the missing entities. 2. Solve the list by creating the missing entities in the source .qvw document. Or remove them from the template. 3. Regenerate the connection cache. These errors may also appear in the QlikView NPrinting 16 project. For example, if the entities were deleted from the .qvw, but still used in the template. In this case: 1. Solve the errors in the QlikView NPrinting 16 installation. 2. Export and import it again. ## Conditions [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Condition needs to be verified: {name} The imported condition `{name}` used in a report in a task has warning or error messages. To solve: Verify and correct the listed errors. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Connection not found: {name} The connection `{name}` used in the imported condition is missing. To solve: Manually update the condition. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Operator not found: {name} The imported condition operator `{name}` is missing. To solve: Update the condition by setting a supported operator. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Values option not found: {name} The values option `{name}` used in the imported condition is missing. To solve: Open the condition and update it. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### QlikView variable not found: {name} The QlikView variable `{name}` used in the imported condition is missing. To solve: * Change the condition by using an existing variable. * Create the variable in the source .qvw and refresh the connection cache. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### QlikView chart not found: {name} The QlikView chart `{name}` used by the imported condition is missing. To solve: Create the chart in the source .qvw and refresh the connection cache. ## Task [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Task filter import failed: {name} The filter `{name}` used in the imported task is missing. To solve: Manually create the filter and associate it to the task. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Filter needs to be verified: {name} An entity is using the filter `{name}`, which has errors or warning messages. To solve: Resolve the errors or warnings in the filter. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Report needs to be verified: {name} You are trying to use the report `{name}`, which has warning or error messages, in a task. To solve: Open the report `{name}` and correct the errors. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Task report import failed: {name} The report `{name}` used in the imported task is missing. To solve: 1. Check the import logs to see if there was an error during the import of the report. 2. Create the report in your Qlik NPrinting November 2019 installation from scratch. Or use the QlikView NPrinting 16 template as custom template. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Task report was skipped: {name}. Another report exists with the same settings and output format: {format} In Qlik NPrinting November 2019 or newer, you cannot add the same report with the same output format and the same quality more than one time for each task. Only the first report is imported and the rest will be skipped. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Task report import failed: {name}. The output format is not supported: {format} Some output formats (like Word documents with macros .docm and PixelPerfect reports as .csv) are not supported by Qlik NPrinting November 2019 or newer. To solve: Add the report to the task and select one of the supported output formats. See: [Report output formats](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/DistributionSchedulesAutomation/Report-output-formats.htm). [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Task report import failed: {name}. The output format {format} is not supported with {type} reports You are trying to import the report `{name}` in a task with an unsupported output format `{format}`. To solve: Add the report to the task and select one of the supported output formats. See: [Report output formats](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/DistributionSchedulesAutomation/Report-output-formats.htm). [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The coloration type {type} is not supported for this task report: {name} Color is the only supported mode in Qlik NPrinting November 2019 or newer. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Multi page advanced setting is not supported for this task report: {name} Report multi-paging is not supported for the report `{name}`. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Custom separator is not supported. Comma will be used instead for task report: {name} The use of custom separators is not supported in Qlik NPrinting November 2019 or newer. They will be replaced by commas. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Custom page range is not supported for this task report: {name} Custom page ranges are not supported for the report `{name}` in the task. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### This tag is not supported for the task email: {name} Qlik NPrinting November 2019 or newer does not support certain email body tags. To solve: Update the email body accordingly. See: [Planning your migration](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/Migrate/Before-you-migrate.htm). [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Using an external HTML file as email body is not supported: {name} You cannot use an external HTML file as an email body. To solve: Copy the content of the HTML file and paste it in the email body editor. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Attaching external files to the task email is not supported: {name} External email attachments are not supported. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### Email footer image is not supported: {name} Email footer images are not supported. You cannot add them manually. To solve, try one of the following: * Edit the email body by embedding the image * Create an HTML body text with the image. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### ‘Create an archive containing the compressed reports' option is not supported You cannot create an archive containing the compressed reports. To solve: Send reports uncompressed. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### 'Low' and 'Medium' report quality are not supported. 'Normal' will be used instead for this task report: {name} 'Low' and 'Medium' report quality are not supported. To solve: Manually update the quality setting. See: [Image quality](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/ReportsDevelopment/Image-quality.htm). [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### 'Printer configuration for hard copies' option is not supported Qlik NPrinting November 2019 or newer cannot send generated reports directly to printers. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The NPrinting 16 task output folder was set to 'Task output folder' QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The NPrinting 16 task output folder was set to 'Recipient folder' QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The NPrinting 16 task output folder was set to 'Task folder with recipient subfolder' QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks. [](https://help.qlik.com/en-US/nprinting/Content/NPrinting/Migrate/Troubleshoot-migration.htm) #### The NPrinting 16 task output folder was set to 'Custom folder' QlikView NPrinting 16 destinations are not imported, you must add them manually to the imported tasks. ## Learn more * [Planning your migration](https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/Migrate/Before-you-migrate.htm)