This is an advanced repair. If at any time you need assistance, you can contact our Technical Support by clicking on the "Live Chat" option on this page.
The Genesis and Food Processor databases require the database and SQL Server instance to have the collation set as case insensitive.
You can check the collation by opening SQL Server Management Studio. When you connect to the server, right click on the server and choose "Properties". In the General page, there should be a "Collation" under Maintenance. The collation will have either "CS" or "CI". If it is CS, you are set to case sensitive, if CI, then you are set to case insensitive. If you are receiving this error and you have "CI" then you will want to check the database. Expand the "Databases" folder and right click on the database (Default Gendata for Genesis, Eshadata for Food Processor), and choose "Properties". In the database properties, go to the "Options" tab. Here there will be a "Collation" option. If you see "CS" you can use the drop down menu to change the collation. The default generally used by ESHA is "SQL_Latin1_General_CP1_CI_AS"
If it is your SQL Server instance that is set to case sensitive, and you require some database in that instance to be case sensitive, you will need to install a new instance of SQL Server to meet the requirements of the ESHA database. If you don't require case sensitivity for other databases, then you can either uninstall the SQL Server instance, and reinstall it, selecting case insensitive, or run a query on the master database to change the collation.
There is a Microsoft article found here that walks you through updating the collation of the SQL Server instance. The server collation that ESHA uses by default is "SQL_Latin1_General_CP1_CI_AS". This would be an advanced repair, if you are not familiar with SQL Server, you can contact ESHA support by clicking on the "Live Chat" option on this page.