/
50138 error after selecting NoahES US or NoahES EU at the login

50138 error after selecting NoahES US or NoahES EU at the login

The 50138 occurs after selecting NoahES US or NoahES EU at the log in:

In this case the profile that points to Noah ES may have been corrupted. There are two solutions to fix the corrupted profiles, the Noah Fix Server Profiles Tool or manual steps to recreate the file.

Check First! - As of Mar 27, 2026 HIMSA has updated the Noah ES Cloud Software, which is not compatible with older Noah ES Client Versions. If you are still using versions older than 4.117, please upgrade to 4.117 to resolve the issue.

Download Noah ES Client 4.117

Cause

Error 50138 is commonly caused by:

  • A corrupted Noah ES profile configuration.

  • A corrupted or missing Noah ES CloudShim folder.

  • Network, firewall, antivirus, or endpoint security software blocking required Noah ES URLs.

Solution 1: Run the Noah Fix Server Profiles Tool

Download and run the Noah Fix Server Profiles Tool:

Expected Results

If the tool successfully repairs the profile, a confirmation message is displayed.

image-20250117-202809.png

If the tool reports that no profiles were updated, or if error 50138 continues after running the tool, continue to Solution 2.

Solution 2: Recreate the Noah ES Profile

Create a new profile:

  1. Close Noah and dismiss the error message.

  2. Navigate to:

    C:\ProgramData\HIMSA\Noah

  1. Ensure File Name Extensions are visible in File Explorer.

  2. Locate:

    BusinessSystemSettings.xml

  3. Rename the file to:

    BusinessSystemSettings.test

  4. Launch Noah.

  5. Click Next on the Welcome to Noah screen.

  6. In the Configuration Wizard, select:

    Store patient records in Noah ES

  7. Complete the wizard by clicking Next and Finish.

  8. At the login screen, select NoahES US or NoahES EU as appropriate and attempt to log in again.

If ProgramData Is Hidden

See: How to view the Program Data directory - Noah ES Support Portal - Confluence

If File Extensions Are Hidden

See: How to show file extensions - Noah ES Support Portal - Confluence

Solution 3: Recreate the Noah ES CloudShim Folder

If the issue persists after recreating the profile, recreate the CloudShim folder.

Warning

All Noah Services must be stopped before deleting the CloudShim folder.

  1. Open Services in Windows.

  2. Stop the following services:

    • Noah Client Service

    • Noah Server Service

    • Noah Server Util Service

  3. Navigate to:

    C:\Program Files (x86)\HIMSA\Noah 4

  4. Delete the CloudShim folder.

  5. Restart the following services:

    • Noah Client Service

    • Noah Server Service

    • Noah Server Util Service

  6. Launch Noah and attempt to log in again.

Solution 4: Verify Noah ES Connectivity Requirements

If the issue persists after completing the steps above, the computer or network may be preventing Noah ES from communicating with cloud services. Blocked Noah ES URLs can result in a 50138 error.

This may occur if traffic is being blocked by:

  • Windows Firewall

  • Third-party firewall software

  • Antivirus or endpoint security software

  • Proxy servers

  • Web content filtering solutions

  • Network security appliances

Review the following article and ensure all required Noah ES URLs are accessible:

Internet Connection, Firewall and Browser Requirements - Noah ES Support Portal - Confluence

If your clinic uses managed IT services, you may need to provide the article above to your IT administrator so they can verify the required URLs and endpoints are allowed.

Other Errors

If you are not able to resolve with the steps above, have questions or need help, please submit an issue thru the Noah ES Help desk:
Submit an issue or Question - Noah ES Online Help Desk