RIP Won't Open

RIP Won't Open

When experiencing issues with the RIP crashing, contacting support is often a requirement. However, there are a few things you can check and/or do to fix or help us get to the root of the issue more quickly.  Below are steps on how to gather log files and some common causes of crashes that you can check before reaching out.

Including Log Files in Your Support Request
To help us diagnose the issue more quickly, you can include the following log files in your support request:

Crash Reports: These provide valuable information about what caused the software to crash.
PrintFactory Logs: You can find these logs at the following locations:
Windows: C:/Users/Public/PrintFactory/Logs
macOS: /Users/Shared/PrintFactory/Logs
Attaching these files to your support request allows us to get to the root of the issue more efficiently.

Common Crash Causes and Quick Fixes
  1. Removing the Last Job Attempted: Sometimes, a problematic job can cause repeated crashes. By removing the last job you tried to print from your work folder, you may clear the issue and prevent further crashes. Default job location: macOS /Users/Shared/PrintFactory/Work or Windows C:\Users\Public\PrintFactory\Work (for custom locations check: macOS /Users/Shared/PrintFactory/Settings/PrintFactory RIP.xml or C:\Users\Public\PrintFactory\Work\PrintFactory RIP.xml
  2. Checking Hard Drive Space:
    1. Work folder Hard Drive: Insufficient space on your computer’s hard drive can cause the software to crash. Ensure you have enough free space on your local drive to handle the job you're trying to print. The default location for the work folder listed here however you may have this setup on another drive and if that is the case, check that location.
      1. Windows: C:/Users/Public/PrintFactory/Work
      2. macOS: /Users/Shared/PrintFactory/Work
  1. Printing to External Drives: If you’re printing to an external drive or a network location, make sure there is enough space on that drive as well.
  2. Printer's Digital Front End Hard Drive: If your printer has a front end with its own hard drive, check that it isn’t full. A full hard drive on the front end can cause the files to crash during the print process.
Including log files and performing these quick checks can save time and help resolve issues faster. If the problem persists after trying these steps, don’t hesitate to contact support with your findings.

    • Related Articles

    • 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 ...

    • Layout Won't Open

      If a setting or file that was previously saved in Layout Preferences is no longer available, it can prevent Layout from opening. To resolve this issue, you need to reset your preferences by removing the Layout.xml file. Steps to Reset Layout ...

    • 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 ...

    • Job Preview in RIP

      To show or hide the job preview Click the Show/Hide Preview button in the main RIP window top toolbar: You can move the location of the preview pane by clicking the title of the preview window & dragging with the mouse. It can be snapped into ...

    • Faulting module C:\Windows\SYSTEM32\MSVCP140.dll in Event Viewer

      If an application is crashing and in the Event Viewer on Windows shows: Faulting module path: C:\Windows\SYSTEM32\MSVCP140.dll i Then this means that the Microsoft Visual C++ Redistributable Version is faulty or missing. To resolve, please download ...