Troubleshooting: "Failed to load integration-in-progress page" on HP OXPd with PaperCut MF

This article explains how to troubleshoot and resolve the “Failed to load integration-in-progress page” error when embedding PaperCut MF on an HP OXPd device. By following the outlined configuration, network, and device state checks, you will be able to restore communication between the device and the PaperCut Server.

When embedding PaperCut MF on an HP OXPd device, you might encounter the following error in the PaperCut admin console:

Failed to load integration-in-progress page. Skipping device registration. If a user is logged in on the device, try logging the user out. Setup will be retried at [time]. To retry now, press “Apply” below.

This error means the HP device cannot load the embedded application from the PaperCut server. This is typically due to a communication, configuration, or device state issue.

How to resolve the issue

This error can happen for several reasons. Work through these steps sequentially to resolve the problem.

1. Verify the required ports are open for the HP device

For the HP embedded app to communicate to the PaperCut Application Server, the app must be able to communicate with the HP device on these ports:

• Inbound to the PaperCut Application Server (from the HP device): 9191 / 9192 / 9193 TCP
• Outbound from the PaperCut Application Server (to the HP device): 7627 TCP/HTTPS and 80 / 443 TCP

For more information about the ports HP uses, see the Firewall Ports used by NG & MF article.

A blocked port 7627 is one reason you might see this error. To test port 7627 from the PaperCut Application Server, run the following command from the Command Prompt:

Test-NetConnection -ComputerName <printer_IP> -Port 7627

If the port is blocked, you will see an output saying TcpTestSucceeded: False in the Command Prompt.

2. Enable SSL/HTTPS (critical for FutureSmart 5.x)

HP FutureSmart 5.x firmware requires HTTPS for OXP applications and rejects unencrypted HTTP connections.

If ext-device.hp-oxpd.use-ssl is set to N in the Advanced Config Editor, this setting causes the error even when ports are open. Part of the embedded application process involves enabling HTTPS.

Review the steps in the embedded manual under the HTTPS Security (recommended) section, and make sure you have configured the following config keys. Reach out to your PaperCut Partner if you need assistance with this.

• ext-device.hp-oxpd.use-ssl = Y
• ext-device.hp-oxpd.port-num = 443

3. Ensure time sync between server and device

A common reason for certificate import failures on HP devices is a time difference between the PaperCut Application Server and the printer. This time difference can cause the certificate to be rejected as not yet valid or expired.

Ensure both the HP device and the PaperCut server are configured to use the same NTP server. Confirm that their time, date, and time zone settings are exactly aligned.

4. Check the “Skip Disk Load” PreBoot setting

If the HP device recently had an HDD replacement, a factory reset, or a firmware change, the Skip Disk Load setting might have been accidentally enabled. When enabled, this setting prevents third-party apps like PaperCut MF from loading. This step is required to be done by your PaperCut Partner; reach out to them for assistance.

To check and disable this setting:

1. Power off the HP device.
2. Boot into the PreBoot menu.
3. Navigate to: Administrator > Startup Options > Skip Disk Load.
4. Ensure Skip Disk Load is disabled (OFF).

5. Clear broken installations on the HP device

Previous failed installation attempts can leave the device in a bad state. Clear these before re-embedding the device.

To clear broken installations in the HP Embedded Web Server (EWS):

1. Go to General > Solution Installer.
2. Remove any existing or broken PaperCut installations.
3. Reboot the device.
4. Re-embed the device using the PaperCut MF Admin web interface.