Short answer: “There was a problem transmitting an eScript! An unsecured or incorrectly secured fault was received from the other party” in Bp Premier means eRx Script Exchange rejected the security certificate your practice signs prescriptions with. It almost always follows a NASH certificate renewal or a new prescriber being added. Call Best Practice Software support so eRx can update the certificate thumbprint on their side, then re-import the NASH certificate in eRx Setup on the Bp Premier database server, check every prescriber shows the same thumbprint, and restart the eRx services.
A medical practice called us one morning because no doctor could send electronic prescriptions. Every attempt showed the same eScript error and fell back to printing a paper script. A few weeks earlier at another practice, a new doctor’s eScripts failed with the same error even though the thumbprint looked right. We’ve seen this several times across the practices we look after, and the pattern is always a certificate that eRx and Bp Premier no longer agree on. Here is what we found and how to fix it.
Fixed by Ryan Colombo, Head of Operations, and Brendan Ramstadius, Senior Technician at GCIT, working with Best Practice Software support. Written up by Elliot Munro, CISO.
Symptoms
When a prescriber sends an electronic prescription from Bp Premier, an eScript window appears:
There was a problem transmitting an eScript!
An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
Ensure that prescription paper is in the printer and the failed items will be printed.

Other signs of the same problem:
- It happens for every prescriber at once, often the morning after the NASH certificate was renewed or eRx certificates changed.
- Or it happens for one new prescriber only, right after they were added to eRx.
- The eRx service status page says everything is operational.
- Scripts still print on paper, so the practice can keep working, but patients don’t get an eScript token by SMS or email.
- Pharmacies may report that barcodes on recent scripts don’t bring anything up.
People also search for this as “eScript not sending Bp Premier”, “eRx unsecured fault”, “problem transmitting an eScript” or “eRx thumbprint error”.
Affected Software
- Application: eRx Script Exchange (Fred IT Group) through the eRx adapter in Bp Premier
- Platform: the Bp Premier database server, where the eRx adapter runs
- Related Services: the practice NASH certificate (FAC_Sign.p12), the eRx Standard Adapter Service and eRx Standard Adapter Store & Forward Service
Cause
Bp Premier signs each electronic prescription with your practice’s NASH certificate and sends it through the eRx adapter. eRx checks the signature against the certificate thumbprint it has on record for each prescriber. If the two don’t match, eRx refuses the message with a security fault, and Bp Premier shows the “unsecured or incorrectly secured fault” error.
The usual reasons they stop matching:
- The NASH certificate was renewed. The new certificate has a new thumbprint. eRx has to update it on their side, and the new certificate has to be imported into eRx Setup. At one practice eRx tried to update it automatically and failed, which needed manual help from eRx.
- The certificate import failed for a new prescriber. In one case the thumbprint was correct, but the eRx audit log showed the certificate import had errored when the doctor was added.
- A change on the eRx side. In another case Best Practice support fixed certificate settings on the server, but eRx also had to update something on their end before scripts flowed again.
Resolution
Step 1: Call Best Practice Software support
eRx no longer supports Best Practice customers directly, so start with Best Practice Software support. Tell them every prescriber (or one new prescriber) gets the “unsecured or incorrectly secured fault” error, and whether the NASH certificate was recently renewed. They can connect to the server, check the eRx setup and ask eRx to update the thumbprint. Keep the case number.
Step 2: Re-import the NASH certificate in eRx Setup
Once eRx confirms the thumbprint they now hold, or as Best Practice support directs:
- Sign in to the Bp Premier database server. eRx Setup must be run on the database server only, not on workstations or Remote Desktop servers.
- Run
eRxSetup.exefromC:\Program Files\Best Practice Software\BPS. - Import the current NASH certificate (
FAC_Sign.p12) with its PIC password. - Check the Thumbprint column. It must be the same for every prescriber, and it should match the thumbprint eRx or Best Practice gave you.
- Close eRx Setup. Closing it restarts the eRx services.
Step 3: Check the eRx services and log
- Open Services on the database server and check that the eRx services are running and set to Automatic, including eRx Standard Adapter Service and eRx Standard Adapter Store & Forward Service. Start any that are stopped.
- Open
C:\erx\erxadapter.logand look for a successful ping response after the restart.
Step 4: Test with a real prescription
Ask a prescriber to send an eScript. If it goes through, ask the team to keep an eye on the next few. Scripts printed while eRx was failing may need to be reissued if a pharmacy can’t scan them.
If only a new prescriber is affected
- Check the prescriber’s eRx Entity ID was entered correctly in eRx Setup. Each provider has a unique Entity ID for each location.
- Check the eRx audit or adapter log for an error when their certificate was imported. If there is one, run the certificate import again and recheck the log.
Important Notes
- Plan NASH renewals. Diary the NASH certificate expiry date and allow time for eRx to update the thumbprint. Doing the renewal early in the day gives you time to fix problems before the next clinic session.
- Other NASH problems look similar. If health identifier lookups or My Health Record also fail after a renewal, the certificate chain may need updating too. See our NASH chain of trust article below.
- Don’t delete working certificates. Leave the old certificate in place until the new one is confirmed working, in case you need to roll back.
Related Resources
- Best Practice Software: Set up eRx Script Exchange
- Fix: Bp Premier HI Service Errors After a NASH Certificate Renewal
- How to Install Best Practice Certificates
- Fix: “Could Not Create SSL/TLS Secure Channel” in Bp Premier
- IT support for practices running Bp Premier
- IT support for medical practices at GCIT
eScripts failing and doctors waiting? Get in touch with our team.