Home   COVID-19   FAQ   How-To Videos   Media Resources   Docs   Troubleshoot

Troubleshoot general client connections

If a workstation has trouble connecting to the Bp Premier server after being added to the network, or after changes to your practice's network, follow the instructions below to troubleshoot the client-server connection.

If a Bp Premier client cannot connect to the server, the Available Servers list is blank:

Best Practice Premier Available Servers

or the error ‘Unable to connect to the server\BPSInstance Server’ appears.

Connection to Bp Server failed

Work through the possible problems and solutions below.

Check the client and server are the same version

This step is particularly important if you are re-engaging a workstation like a remote laptop or a desktop client that has not been used as a Bp Premier client for some time.

Client computers must run the same version of Bp Premier as the server, otherwise the client-server connection will not be successful.

To check the version of a client without starting Bp Premier:

  1. In Windows File Explorer, go to C:\Program Files\Best Practice Software\BPS.
  2. Right-click on the file Best Practice.exe and select Properties.
  3. Click the Details tab and view the product version.

Version in Properties screen

You can view the version of the Bp Premier server by selecting Help > About within the software.

If the client version is not the same as the server version, you must upgrade the client to the same version. Use the same installation media that you used to upgrade the Bp Premier server. You can also download recent program updates from bpsoftware.net.

Check network connection

Check the following items if existing installations have server connection problems.

Physical problems

  1. Are other workstations in the practice able to connect to the Bp Premier server?
  2. Is the server turned on?
  3. Is the network cable plugged in to the computer correctly?
  4. Are the cables from the client connected to the server or network switch?
  5. Is the network card in the computer connected and seated properly, if there is a network card?

Internet access

Open your internet browser and enter the website www.microsoft.com.au. Does the browser display Microsoft’s website? If not, contact your network administrator for assistance. If yes, continue.

The next two tests require that you access the command prompt on your PC. You will need to know the name of the Bp Premier server on your practice network.

  1. Select the Windows flag in the bottom left, click the down arrow to view applications, and open the Command Prompt under Windows System. The Windows command prompt will appear.
  2. In the black command prompt box, type:

    3. ping <Bp server name>

  3. Press Enter.

    4. If unsuccessful, the ping will time out or return an error message that it could not find the host. Contact your network administrator for assistance.

    If the ping is successful, the command prompt will return your server's IP address. Write down the IP address. Continue diagnosing the problem.

  4. In the command prompt, type:

    5. ipconfig

  5. Press Enter. The command prompt will return a set of information about the workstation's IP configuration.
  6. In the section of the returned information titled Ethernet adapter, look at the value for 'Media State'. If the 'Media State' is 'Media Disconnected', a problem exists with your network card or the cable plugged into it. Contact your network administrator for assistance.
  7. Go to the Windows Control Panel and open Network Connections, Manage Network Connections, or Network and Internet, depending on your Windows version.
  8. Check that your current network connection is enabled and active. If not, contact your Network administrator for assistance.

TCP/IP settings

If the resolutions above do not work, make sure that Enable LMHOSTS lookup and Enable NetBIOS over TCP/IP are enabled in your Windows TCP/IP configuration. Your IT support can assist. You must restart the SQL Server Browser service after any changes to TCP/IP configuration.

Check firewalls

If you have installed a client but cannot find the Bp Premier server, your firewall settings may be preventing detection. The Bp Premier server Windows firewall must allow connections to and from Bp Premier clients. This is normally configured during installation, but you may need to run a utility to set the port values correctly.

If your server uses Windows firewall

  1. Log in to Windows on the Bp Premier server as an administrator.
  2. Make sure that Windows firewall is turned on.
  3. In Windows File Explorer navigate to BP.PortsUtility.exe in C:\Program Files\Best Practice Software\BPS\BPSupport.
  4. Right click on BP.PortsUtility.exe and select run as administrator. The Bp Ports Setup Utility will open.
  5. Ensure all the checkboxes on the left are ticked, and click Ok.

  6. Go to a workstation and try to log in to Best Practice again.
  7. If the workstation still cannot connect to the server, continue with Check dynamic ports.

If your server uses third-party firewall software

  1. Log in to Windows on the Bp Premier server as an administrator.
  2. Make sure that the third-party firewall is turned on.
  3. In Windows File Explorer navigate to BP.PortsUtility.exe in C:\Program Files\Best Practice Software\BPS\BPSupport.
  4. Right click on BP.PortsUtility.exe and select run as administrator. The Bp Ports Setup Utility will open.
  5. The list of ports required by Bp Premier will be displayed. The ports will need to be opened in your firewall.
  6. Close the utility when done.
  7. Open the required ports on the server using your firewall configuration software.
  8. Go to a workstation and try to log in to Bp Premier again.
  9. If the workstation still cannot connect to the server, continue with Check dynamic ports.

Check dynamic ports

On some systems, the dynamic port will not be displayed and could block the connection from a workstation. You will need to check SQL server to identify these ports.

  1. Go to Programs or Apps > Microsoft SQL Server > SQL Server configuration Manager.
  2. Select SQL Server Network Configuration.
  3. Select Protocols for BPSINSTANCE.
  4. Double click on the protocol TCP/IP.
  5. Click on IP Addresses.
  6. Scroll to the bottom and identify the entry for 'TCP Dynamic Ports'. This is the dynamic port that needs to be opened within the firewall.
  7. Open the dynamic port on the server using your firewall configuration software.
  8. Go to a workstation and try to log in to Bp Premier again.

If you still cannot connect to the server, you may need to check that the Windows registry entry is pointing to the correct server.

Update registry to point to server

After moving a Bp Premier server, you must edit the Windows registry on each workstation to connect to the new server. You will need the Bp Premier server's IP address or hostname. You can run 'ipconfig' to identify a machine's IP address, or 'hostname' to obtain a machine's hostname.

Obtain server hostname or IP address

  1. Log in to Windows on the Bp Premier server.
  2. From the Windows Desktop, go to Start > Apps > Windows System > Command Prompt.
  3. Type 'hostname' at the prompt and press enter. The command prompt will return the computer's hostname on the next line.
  4. If you need the IP address, type 'ipconfig' at the prompt and press Enter.
  5. The IP address will be listed under the active ethernet card's IPv4 Address. In the following example, the IP address is '192.168.1.10'.

    6. Run ipconfig

Update workstation registry

IMPORTANT  Updating the Windows Registry incorrectly has risks. Update only the entries indicated in the instructions. Record initial values on entries that you change, in case an entry needs to be restored.

  1. Log in to Windows on a Bp Premier workstation.
  2. Open the Windows command prompt.
  3. Type in ‘regedit’ and press Enter. The Registry Editor will open.
  4. Navigate to the following folder:
    • On 32-bit operating systems, scroll to HKEY_LOCAL_MACHINE > Software > Best Practice Software
    • On 64-bit operating systems, scroll to HKEY_LOCAL_MACHINE > Software > Wow6432Node > Best Practice Software.
  5. Navigate to Best Practice Software > Best Practice > Database.
  6. You will see an entry for Server on the right hand side. Double-click this and an Edit String dialog box will appear.

    7. Registry Editor Server Setting

  7. Type in the hostname or IP address for the Bp Premier server into the Value data field.
  8. Click OK.
  9. Navigate to HKEY_CURRENT_USER\Software\Best Practice Software\Best Practice\Database and repeat steps 6-8.
  10. Locate the registry folder HKEY_LOCAL_MACHINE > Software > ODBC > ODBC.INI. If this folder contains any sub-folder starting with BPS, delete these keys.

    11. BPS ODBC.INI Registry Keys

  11. Log in to Bp Premier on the workstation.
  12. Modify a test patient's record on the workstation with a minor change and save the changes.
  13. Log in to the Bp Premier server and view the patient's record you just modified. If the change is visible, the workstation has successfully connected to the new server.
  14. Occasionally, this setting will not work the first time. If the workstation cannot connect to the Bp Premier server, repeat steps 4—8 to update the registry and test the connection to the server again.

Repeat steps 1—12 for each Bp Premier workstation.

Delete Best Practice registry keys and folders under virtualstore

Delete registry keys under virtualstore

  1. Log into Windows on the Bp Premier workstation that is not connecting to the server.
  2. Open the Windows command prompt.
  3. Type in ‘regedit’ and press Enter. The Registry Editor will open.
  4. Select HKEY_LOCAL_MACHINE > Software in the left-hand pane, and select Edit > Find... in the top menu.
  5. In the Find what: field, enter 'virtualstore' and under Look at, ensure Keys is ticked, and Values and Data are unticked.

  6. Click Find Next.

  7. If you cannot find any registry keys called virtualstore, no further action is required. If you do find a virtualstore registry key, check if there are any Best Practice-related keys under it and delete them.
  8. Check if the registry key ODBC.INI exists under virtualstore. If there are any Best Practice-related keys under ODBC.INI, delete them.
  9. Repeat steps 4 - 8 for HKEY_CURRENT_USER > Software.
  10. Log in to Bp Premier on the workstation. Modify a test patient's record on the workstation with a minor change and save the changes.
  11. Log in to the Bp Premier server and view the patient's record you just modified. If the change is visible, the workstation has successfully connected to the new server.

Delete folders under virtualstore

  1. In the client computer's file explorer, navigate to C:\Users\(your user profile)\AppData\Local\VirtualStore\Program Files.

  2. If there is a Best Practice Software folder here, delete it.

User is prompted to reconnect each login

If a Bp Premier workstation prompts a user to reconnect to the server each time you log in, the issue is most likely related to the Windows user having limited permissions to update the registry.

  1. Log in to the workstation as a Windows administrator.
  2. Log in to Bp Premier and connect to the server.
  3. Close Bp Premier.
  4. Open the Windows command prompt.
  5. Type in ‘regedit’ and press Enter. The Registry Editor will open.
  6. Scroll down to the following folder:
    • On 32-bit operating systems, scroll to HKEY_LOCAL_MACHINE > Software > Best Practice Software
    • On 64-bit operating systems, scroll to HKEY_LOCAL_MACHINE > Software > Wow6432Node > Best Practice Software.
  7. Right-click on the folder Best Practice Software and select Permissions. The Permissions for Best Practice Software screen appears.
  8. Select a user group to which the user who cannot connect to server belongs (most likely ‘Users’ or ‘Everyone’).
  9. Tick the box in the Allow column for Full Control. Click Ok.

    10. Registry Editor Full Control

  10. Close the Registry Editor.
  11. Log out as administrator and back in as the Windows user who cannot connect to server.
  12. Log in to Bp Premier and connect to the Bp Premier server.
  13. Log out and back in to Bp Premier to test that the problem is resolved.

Terminal servers unable to connect to server

The steps above apply to troubleshooting terminal server workstations in addition to PC workstations. However, if your practice has a terminal server that will not connect to the Bp Premier server, the steps below may resolve the issue.

  1. Log in to the terminal server that is unable to connect to the server.
  2. Open the Windows command prompt.
  3. Type in ‘regedit’ and press Enter. The Registry Editor will open. If Windows displays a UAC control dialog, click Yes.
  4. Scroll down to the following folder: HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > Microsoft > Windows NT > CurrentVersion > Terminal Server > Install > Software > Best Practice Software > Best Practice > Database.
  5. You will see an entry for Server on the right hand side. Double-click this and an Edit String dialog box will appear.
  6. Type in the IP address for the Bp Premier server into the Value data field.
  7. Click OK.
  8. Log in to Bp Premier again on the workstation.

Last updated 23 July 2020

Forums

Webinars

Videos

Training

Subscribe