Romexis PMBridge Connection Errors And How To Fix Them

Planmeca Romexis PMBridge error means the imaging software opened, but the link to your practice management software failed. The usual culprits are a reserved port or a wrong server IP in the bridge file. This guide shows how to clear both and read the log when neither works.

TL;DR

• PMBridge passes patient data between Romexis and your practice software, and a failed bridge leaves Romexis open but disconnected.

• A ***Reserved tag in the port list means a port conflict, cleared from File, License Management, Port Info.

• When the bridge opens, the wrong patient or none, fix the host IP in Romexis.bat.

• The PMBridge log records the failure and lives in the Planmeca program data folder.

What PMBridge Does

PMBridge is the connector Planmeca built so that other software can hand patient details to Romexis and pull images back. A receptionist opens a patient in the practice management system, clicks on the image, and PMBridge carries that patient straight into Romexis so nobody retypes a name or a chart number.

When the bridge breaks, Romexis still opens on its own. It just will not receive the patient from the other program, so the workflow that should take one click now takes manual lookup. Planmeca documents the bridge and a lighter version called DxStart in its technical manual, which is where the log location and port behavior come from.

Error #1: PMBridge Connection Does Not Work

This is the port conflict. Romexis tries to reserve a port for the bridge, fails, and shows a message. After you clear it, Romexis opens, but the bridge stays down. The giveaway is a ***Reserved tag next to the port in the port list.

1. Open File, then License Management, then Port Info, using an account with administrator rights.

2. Look for ***Reserved next to a port, which marks the stuck reservation.

3. Click Clear ports to release the used-port list.

4. Restart Romexis and test the bridge from your practice software.

The Romexis server also cleans the used-port list on its own from time to time, comparing active users against the list, so a restart plus a manual clear usually settles it. If it returns often, two programs are likely fighting over the same port, and your dealer can reassign one.

Error #2: The Bridge Opens The Wrong Patient or No Patient

Here, the bridge runs, but the patient does not arrive, or the wrong record opens. The cause is almost always a wrong server IP written into the bridge's batch file. That file tells the bridge where the Romexis server lives.

5. Open the file Romexis.bat in the Planmeca\Romexis\pmbridge\Program folder.

6. Find the host= entry.

7. Set it to the correct Romexis server IP, for example, host=192.168.1.10, using your real server address.

8. Save the file and restart the bridge.

A fixed server IP is recommended so the address in Romexis.bat does not go stale after a reboot. Leave the rest of the bridge path alone, since Romexis installs to the same program folder on both 32-bit and 64-bit Windows.

When Neither Fix Works, Read The Log

The bridge keeps its own log, and it names the failure when the obvious fixes are missed. You do not have to decode it alone, since your dealer can read it, but knowing where it sits saves time on the call.

The PMBridge log is saved in the %programdata%/Planmeca/Romexis/pmbridge folder. Open the newest file, look near the end for the last error, and have that line ready when you contact support.

Keep The Bridge Working

A stable bridge comes down to a stable address and a little record-keeping. Set it once, and most clinics never touch it again.

• Give the Romexis server a static IP so the host= line in Romexis.bat stays correct.

• Write the server IP into your clinic setup notes next to the bridge details.

• After a practice software update, send one patient through the bridge to confirm it still passes the record.

A broken bridge means a name typed twice and an image saved to the wrong chart, which slows every imaging appointment and muddies the dental treatment plan tied to that record. The practice software on the other side of the bridge matters as much as Romexis, and Dental Reviewed compares options in its guide to practice management software for dentists.

Bottom Line

Read the symptom. A ***Reserved port clears from Port Info with Clear ports and a restart. A wrong patient or no patient points to the host= line in Romexis.bat, which needs the real server IP. When both come up empty, the PMBridge logs in the Planmeca program data folder and names the cause, and your dealer can take it from there.