Updating the Direct Print Components
Direct print has two parts:
- The Customizable Report Pack extensions in Business Central.
- The local Windows components, which you install with the ForNAV installer: the client-print program on users' computers and the direct print service on your servers.
You update the extensions in Business Central the same way as other extensions. This page is about updating the local Windows components.
When to update
You don't have to update the local components every time a new version is released. Update them when:
- You update the Customizable Report Pack extensions to a new major or minor version. New features in Business Central may need a newer version of the local components. We recommend that you keep the extensions and the local components on versions from the same release.
- You need a fix or a new feature. Check the release notes. If they list a fix or feature for client-print or service-print that you need, update the components.
- You're troubleshooting. If printing fails and you run an old version of the local components, update before you look for other causes. ForNAV support may also ask you to update.
- You replace or set up a machine. Always install the latest version on a new server or a new user computer.
Avoid updating in the middle of a busy period. Plan the update for a time when nobody needs to print, or update one machine at a time (see Several print services).
Find the installed version
The version of the local components is shown in the file properties of the binaries. Go to the installation folder, which is usually:
C:\Program Files\Reports ForNAV
Right-click ForNav.ReportService.exe (service-print) or LocalPrint.exe (client-print), choose Properties, and look at the Details tab.
How to update
To update, download the latest installer and run it on top of the existing installation. You don't have to uninstall the old version first.
Before you update
Back up your configuration. The configuration files are stored in this folder:
C:\ProgramData\ForNAV\Direct Print\ConfigurationThey include
config.json(service-print) andclient.json(client-print). The installer is not meant to change them, but a backup lets you restore them if something goes wrong.Check the print queue. For service-print, check that no jobs are waiting or printing on the ForNAV Print Queue page in Business Central. Jobs created during the update stay in the queue and are printed when the service is running again.
Update service-print
- Log in to the server where the direct print service is installed.
- Run the installer and select the same components that you installed before.
- When the installation is finished, the service starts automatically.
- Open the Direct Print user interface from the system tray, and check that the service is connected to your environments. User interface
- Print a test document.
The update keeps the service's settings, such as the user that the service runs as. If you run the installer with the /DirPrtSvcReinstall=YES switch, the service is removed and installed again, and the service user is reset to NETWORK SERVICE. Don't use this switch for a normal update unless you want to change the startup type. Installer command line switches
Update client-print
- Close the client-print program if it's running. If you use stay in memory, the program can still be loaded in the background after the last print job. You can end
LocalPrint.exein Task Manager, or wait until the idle timeout has passed. - Run the installer and select the client-print component.
- Print a test document.
Update many machines
You can run the installer unattended to update many computers, for example with a software distribution tool. Use the /SILENT or /VERYSILENT switch together with /SUPPRESSMSGBOXES, so the installer doesn't stop and wait for someone to answer a message box. Use /COMPONENTS to select the same components that are already installed.
Client-print:
ReportsForNAV_<version>.exe /COMPONENTS="deployment/print" /SILENT /SUPPRESSMSGBOXES
Add /LOG=<file> to write a log file that you can check if an update fails. Unattended installation
Several print services
If you run the direct print service on several servers, update one server at a time. While one service is being updated, the other services keep printing the jobs from the queue. Scaling service-print
If you route jobs to a specific service, those jobs wait in the queue until that service is running again. Routing
After the update
If printing doesn't work after the update:
- Check the logs for errors. Logs
- Check that the service still runs as the right user and can see the printers. User context
- Compare the configuration files with your backup.
See also Service-print troubleshooting and Client-print troubleshooting.