The NPrinting Designer, NP Server and NP Engine should always be the same version.
Error will be the results if any or all of the components are installed as different versions.
One reason specifically is that .NET framework needs to be consistent and need to match the server and engine etc.
.NET 4.6.2 requirement for all NP components
.NET 4.5.2 requirement for all NP components
Also aside from .NET, the back end schemas for each NP component must match ie: same version or errors in report development or automated deliver will ensue.
OK. If one is not on the same version for all 3 components, could it cause this error: "windows could not start the qlik nprinting schedule service on local computer. error 1067." I'm getting this now as a result of enabling DEBUG mode in the scheduler config file and trying to restart the scheduler service. Thoughts? Thanks.
I needed to specifically say that Designer is not being used on my NP machine, and with that said, I have confirmed that if you are not using Designer on the NP machine then no, the version doesn't matter. However, if you are not using Designer on your NP machine, then it is probably best not to have it there so you are not tempted to use it, OR, even if not using it keep it updated for consistency.