Summary
This article describes the most common causes of the HRCHECK error when running the ScheduALL for Windows application, along with solutions.
Applicable Products
ScheduALL for Windows desktop client (core) v4.xx and v5.xx
Procedure
An HRCHECK error can be caused by the following:
-
Incomplete or corrupt .NET installation: Verify you have Microsoft .NET 4.5 or 4.6.1 installed, and that you have performed all .NET related Windows Updates.
-
Window’s Data Execution Prevention (DEP): To find this setting, go to Windows Control Panel → System → Advanced System Settings → 'Advanced' tab → the 'Settings…' button under 'Performance' → 'Data Execution Prevention' tab.
The option 'Turn on DEP for essential Windows programs and services' will exempt all non-system applications from DEP, including ScheduALL (schedwin.exe). Selecting this option will also require rebooting the machine. The other option will let you select specific applications to exempt from DEP. If you choose this option, you will then need to add C:\ScheduALL5\Schedwin\Schedwin.exe manually, and reenter it each time you upgrade ScheduALL.
-
Invalid Addresses in ODBC or Configuration Files: Verify that your ODBC connection and any server/component addresses in ScheduALL configuration files are referring to servers by their hostnames, instead of by their IP addresses. This is necessary even if all the components are installed on the same machine. Do not use 'localhost', '(local)', or '.\' when entering server names. You can associate hostnames to IP addresses via the Windows HOSTS file, if necessary.
-
Database Connectivity: Use the ping.exe utility to verify that you can connect to the database server and ScheduALL Application Services server from the user's machine. Verify that the IP addresses shown by the utility are correct for the machines to which you expect to connect. Ping the same servers from a machine where ScheduALL is working without the HRCHECK error and compare the IP addresses.
-
SQL Server Instance Name: If your database is located on a named SQL Server instance, make sure that the instance name is included in the ODBC setup, and in ScheduALL configuration files. (For example, "SERVER01\SQLEXPRESS" instead of the just “SQLEXPRESS” or "SERVER01".)
-
SQL Server Browser: Check that the SQL Server Browser Windows service is enabled and running on the database server machine. Please note it is important that the Browser service starts after the SQL Server service. As such, if you ever need to restart the SQL Server service, you will need to restart SQL Server Browser service right after.
- DNS-related issues: If the database server, ScheduALL Application Services, and/or the client machine are on different subnets from each other, adjust the Windows networking settings as necessary to provide connectivity and communications between them.