Error 50138 When Starting Noah 4

You receive the error 50138 ‘Could not connect to the server’ when you start Noah 4. This error is telling you that Noah cannot connect to the server. This can be the Noah Server across the network or on the local machine.

Try the solutions outlined below that apply to your situation. If not able to resolve the 50138 error, see information linked here on how to collect log files for your Noah Distributor’s support technician.

 
 

Solution 1

Go to the PC where your Noah 4 Server database is installed. Restart the NOAH Server Service. You can do this in two ways:

  • Reboot your PC
  • Restart the service manually in the Windows Services Management Console

Solution 2

If you have recently installed or updated to Noah 4.10 or a higher version, and receive the error 50138, please check here. 

 

Solution 3

Check to be sure that the Noah Server machine and the Noah Client machine are in the same time zone.

 

Solution 4

Is it possible that the Noah Server has been upgraded to a newer version than the Noah clients?

In most versions of Noah, a specific error message is given if the server and client versions do not match, but in some cases a 50138 is given.

  • Check the version of Noah on the server
  • Launch the Noah Console to check the Noah version on the workstation
  • Noah server and client versions need to match, update workstations if necessary
    NOTE: The major version needs to match but the minor version can be different, for example you can have a Noah 4.91 server and 4.92 workstation.

Solution 5

Check to be sure a Noah 4 license file is installed. If this machine has been configured as a client but now is attempting to look at the local database a license file needs to be installed.

 

Solution 6

Antivirus software can sometimes be the culprit for 50138. If the above solutions have not resolved the 50138 error, look to the History, Event log, or the Virus chest in your antivirus software to see if a Noah process has been blocked. If possible, temporarily disable the antivirus and try to launch Noah again.
 

Solution 7

50138 can be caused by corruption in the Noah configuration database. The steps below will create a clean configuration database:

  1. Navigate to Services and stop both the Noah Server and Noah Client services. Then minimize the Services window.
  2. Navigate to the NoahCfgDatabase.sdf file located at C:/Program Files (x86)/Common Files/HIMSA Shared and rename the file to NoahCfgDatabase.old.
  3. Restart the Noah Server and then the Noah Client services.
  4. Launch Noah.

Noah will create a new configuration  file when it launches. Any preference settings made in Noah will need to be reset, for example module order and customized fields.
 

Solution 8

50138 can be caused by corruption in the Noah patient database. The steps below will create a clean, empty patient database.

IMPORTANT: You will need to Restore from a Backup to recover the Noah patient database.
 

  1. Navigate to Services and stop both the Noah Server and Noah Client services. Then minimize the Services window. 
  2. Navigate to the NOAHDatabaseCoreSqlCompact.sdf file located at C:/Program Files (x86)/Common Files/HIMSA Shared and rename the file to NOAHDatabaseCoreSqlCompact.old
  3. Restart the Noah Server and then the Noah Client services. 
  4. Launch Noah. 

Noah will create a new, blank, patient database file when it launches. You will need to Restore a recent Noah Backup to recover the patient database.

 

Solution 9

If you have recently updated to Noah 4.8 and started seeing 50138, check here.

 

Solution 10

Manually register Noah components using the following directions.

  1. Open a Command prompt
  2. Navigate to C:\Program Files (x86)\HIMSA\Noah 4
  3. Type noahappsregister fregister
  4. When the command is complete, the last line should read ‘Applications registered’

 

 

Solution 11

Check if the computer’s name or the profile name has been changed:

  1. From the login screen select ‘Connect to New Server’.
  2. Name the New Profile and select Browse.
  3. Choose Refresh – this will check for any available Noah 4 Server computers:
  4. Choose the correct server for the new profile, click Select.
  5. Click OK on the Add/Edit Server Profile box.
  6. At the Noah login choose the new profile:
  7. Once you are successfully in Noah, go to Setup, Administration, Noah Server Setup, Server Profiles and delete the profile to the old computer name.