License/Proxy server needs upgrade to the latest version

When you see the message License/Proxy server needs upgrade to the latest version, it means that your license server on another computer is not updated to the same version as the application you are trying to run.

In this example, the user is trying to load V6.8.1 Layout application whilst the PrintFactory license server (on another computer where PrintFactory is installed) is using V6.7.1

To solve the situation, you need to ensure all computers with PrintFactory installed are using the same version.

• Related Articles

• License (Re-) Activation and discovery

  License Activation and registration License Connectivity: Server and Clients License Check and Re-Activation License Activation and registration How to activate the license When a license is created it is automatically registered to the end-user. The ...

• Moving License Server

  Moving PrintFactory License Server to Another PC When you need to move the License Server to a new PC, the PrintFactory license must first be deactivated on the current PC and then reactivated on the new one. This is because the License Server in the ...

• Online License Activation and registration

  The license is registered during the license creation process. When a license is created and registered to the customer, the user assigned as the license manager will receive a ‘Welcome to PrintFactory’ email. The ‘Welcome to PrintFactory’ email ...

• License Update

  Go to the Software Manager application Click the “Update” button. From Version 6.7. onwards, the update button can be found in the Help menu. The Software Manager application can be accessed by accessing “License Info” from the Help menu in either ...

• Resolving RIP Crash or License Activation Issues After Update to 6.8.1 Due to Faulty MSVCP140.dll

  If you encounter issues such as PrintFactory RIP crashing or the license failing to activate after an update (in V6.8.1), this may be due to an error with the MSVCP140.dll file. You can confirm this by checking the Event Viewer for a fault message ...