Reloading connection metadata

Connection metadata contains information about the data and structures of linked QlikView documents or Qlik Sense apps.

Qlik NPrinting automatically uploads metadata when a new connection is created. Metadata must also be updated whenever you change the data structure or content of QlikView documents or Qlik Sense apps connected to Qlik NPrinting. This ensures that Qlik NPrinting is aware of these changes.

After the metadata is reloaded, all instances of QV.exe that are running on Qlik NPrinting Engines associated with the connection will automatically stop and restart to update them. Existing reports are not automatically re-run, so they may contain old data. Reports executed after a metadata reload will show the updated data.

Types of connection status

The Cache status column shows one of the following values for each configured connection:

• Never generated: the connection has never been opened.
• Pending: Qlik NPrinting is attempting to connect.
• Generating: Qlik NPrinting is connected and importing metadata.
• Generated: connection successful on all Qlik NPrinting engines.
• Error: the connection is failing on all available engines. The Qlik NPrinting Scheduler will try to connect again two minutes after a failure.

The Connection status column shows one of the following values for each configured connection:

• Connection successful on all NPrinting engines.
• Warning: One or more engines are not working.
• Connection failed on all NPrinting engines.

Troubleshooting

There are several way to resolve a Warning, Error, or Connection failed status. To start, open the connection you want to troubleshoot, and click the Run verification button. This will give you a list of possible issues. Here is an example where verification failed because Qlik Sense certificates were not installed correctly:

You can also check the following:

• Connection properties: For example, verify the QlikView document path, username, and password. In Qlik Sense, check if the certificates are present on the Qlik NPrinting Engine computer.
• Qlik NPrinting Engine installation and configuration: For example, an engine with QlikView Desktop 12 cannot open a document on a QlikView 11.2 server. Check also that QlikView Desktop has an active license for the Windows user who runs the service.

After resolving any issues, re-launch cache generation, or run a task.

Here are some common causes of connection errors:

• Verify connection errors when setting up a connection to Qlik Sense in Qlik NPrinting
• Verify connection errors when setting up a connection to QlikView in Qlik NPrinting
• Connection status error
• Connection status not shown in Qlik NPrinting web console
• Connection timeouts and long running tasks

Reloading metadata manually

Do the following:

1. From the main menu, click the Apps drop-down, and click Connections.

   Review the entries in the Last cache update column. You should refresh the metadata if the Last cache update value is -.

2. Click on the connection name to open the connection.

3. Click Reload metadata.

   You will see the status:Cache status - Generating. This means that Qlik NPrinting is connecting to Qlik Sense or QlikView and importing metadata. If you have a large app or document, this may take several minutes.

   

4. Once the cache status shows Generated, you can create a new report template. If you get an Error status, check your connection information.

   

Your connection metadata has been updated. You can now create or update reports associated with these connections.

Reloading metadata via scheduled trigger

You can create triggers to schedule regular metadata reloads.

Do the following:

1. From the main menu, click the Apps drop-down, and click Connections.
2. Click on the connection name to open the connection.
3. Click the Triggers button.
4. Click Create trigger.
5. Type a name for the trigger.
6. Select a Schedule type and Time.
7. Set a Start date and Time zone.
8. Click the Enabled button.
9. Click the Create button.

Your metadata will now reload automatically, based on your settings.