Skip to content

Docpay SQL Errors

NEW

Myhealth Docpay uses a cloud based server to connect to our sites, which may be rendered unable to connect by changes to a site's network or server configuration.

This document details the process for resolving such connection issues.

NOTE

SQL Errors can be confuzzling - don't worry, just take it step by step

DANGER

BE CAREFUL

SQL is not to be trifled with, we house sensitive patient data, don't mess with it, only follow steps if you feel comfy with steps, otherwise escalate.


1

Check if PUBLIC IP has changed

If the site IP does not match the IT Journal (Cybersecure would have said something too), check to ensure that you run the bp-ping.exe program in Task Scheduler.

This will update the Docpay server (This may also be referred to as "knock-knock")

WARNING

If the site is running on 4g NOT supplied by Switch Telecomm - extractions will not work.

This will require a manual process, outlined further down.

2

Check Port Forwarding on Unifi

Ensure that the Port forwarding exists is set up. (Docpay IP is 103.230.159.8)

FieldValue
NameBPSQL - DocPay
Source103.230.159.8
Port5434
Forward IPBP Server IP
Forward Port5434
ProtocolTCP
LoggingEnabled

Example here

3

Ensure BP Ports are set correctly

WARNING

This MUST be done when the site is closed or willing to close as it will require a restart of the BP SQL Services

The port that BP uses might not be set to 5434 on the server. Must ensure its 5434.

  1. Open SQL Server Configuration
  2. Under SQL Server Network Configuration - Open protocols for BPSINSTANCE
  3. Open TCP/IP
  4. Click on the IP Adresses Tab
  5. Scroll down to IPALL and change TCP Port to 5434
  6. Click OK and the restart the BPSINSTANCE Sql Service from Services.
Open me for a GIF Guide
4

This is where it gets tricky

There are a few errors that you will not be able to fix without escalation

These include the following errors:

  1. BPSMH User Not Mapped/ not enough permissions

WARNING

When this happens - please escalate to Neil, Kayne, Kristine, or Developer Team