This error will occur if the Noah server has been updated to Noah 4.1 but the client is still running Noah 4.0

Cause: The computer name has been changed.

There is an issue with Noah 4 where the module has been launched but it never appears on the screen. Upon further examination the module is visible on the Windows task bar.   Clicking on the task bar icon does not result in the module becoming visible.

This problem only affects new installations of Noah 4. The problem will not appear if the module exists in NOAH System and you migrate it to Noah 4.

If the patient record is coming from a different Noah 4 database, Noah 4 may create a duplicate patient record.

You receive error 50006 when opening the NOAHaud module in Noah System 4.2.

You receive error 1722 while attempting to upgrade your Noah 4 installation.

You receive the error 50112 “Invalid login. Please try again” when you try to login to Noah 4.

You receive the error 50138 "Could not connect to the server ..." when you start Noah System 4.

You receive the error 50175 "The NoahClient Service is currently not running ...".

You receive the error 50166 "Backup failed!" while backing up the Noah 4 database.

You receive error 50126 when using the Noah Console administration functions if you are connected to the Noah machine using Remote Desktop.

Launching Noah 4 you receive the message: No preferred manager of type business system … Noah exception code 308

If the path in the directory or the path in the shortcut have been renamed to lower case C:\Program Files\himsa, this error will occur.

Noah 4 does not support eTONA functionality. When the upgrade detects a NOAH 3 installation with eTONA enabled it will present a message advising to disable in order to continue with the Noah 4 installation.

The Basic Module installation needs communication with the Noah Server and Noah Client services to install successfully. If the communication is interrupted or not available the modules will not install.