RIP error: "Reference profile could not be loaded"

RIP error: "Reference profile could not be loaded"

Error appears in the Processing tab in the RIP job window.



Reason:  The Queue has lost the link to the Reference profile

Resolution:  open the RIP queue and select the Reference profile tab.  Toggle between another reference profile and back and save the Queue.  This will restore the connection to the reference profile.   Add new job in the Queue. 



    • Related Articles

    • RIP error: 'Connection forcibly closed by remote host'

      This error appears in the Print tab of the RIP. The cause is either: - a comms issue (e.g wrong IP) or - a file issue (sending wrong format, wrong size due to settings on Printer Controller,..) Triage process: Case of Hosonsoft with PrintBridge - ...
    • "PMM is not calibrated on this printer " Error in RIP

      “PMM is Not Calibrated” Message in PrintFactory RIP Issue When sending a print job you may see the popup: “PMM is not calibrated on this printer” This reminder appears and it will prevent the job from printing until dismissed. Cause The RIP’s printer ...
    • RIP User Interface Overview

      Scaling the job window contents This item is in the bottom right hand side of the RIP Interface. Scaleable up and down. By sliding the white button along the bar to the right, makes the window bigger, and the left makes it smaller. The columns are ...
    • My Printer is Errored or Disconnected From the RIP

      When your printer is in a red state, it can halt your printing tasks. This article is meant to cover the most common solutions to these issues. The first step would be to note the error messages in the RIP that may be helpful. Error Message: No ...
    • 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 ...