Why am I running out of activations so quickly?

Occasionally you will see your activation count go higher than expected. Here are some possible reasons for computers taking up an activation:

• Normal First-Time Install
• Application Server Hosted Application 
• Changing Hostname
• Launching De-Activated Client (Deactivation Instructions)
• Occasional Client Upgrades

If you find you are out of activations more quickly than expected, follow the steps below.

Application server misreading activations

Deployment: On-premises Expertise: Expert user/Admin

If you are running Food Processor on an app server environment, such as Citrix, VDI, VmWare, Terminal server, etc., your server app may assume the activations are per launch rather than per computer. This will eat up your licensed activations quickly.

To prevent this from happening, you will need to edit the .exe.config file.

1. Close all open connections to the database. This includes any open ESHA programs (Genesis R&D Foods, Genesis R&D Supplements, ESHA Port, Food Processor, etc.)
2. Browse to find the config file in the path where your program is installed. This is typically C:\Program Files (x86)\Esha Research\FoodProSQL or EshaPortSQL)
3. Look for a FoodProSQL.exe.config or ESHAPortSQL.exe.config file
4. To edit the File either
   • open Notepad as an Administrator and navigate to the file
      or
   • Copy the file to the desktop, edit the file, save changes and copy and replace the config file back to the program folder
5. Add the following just before the closing </esha.licensing> tag<machineId providerType="PerDomain" />to the config file. T
   This is XML so be attentive to spelling (of course), but also capitalization.
6. Find the <esha.licensing> ... </esha.licensing> tags.
7. Add the following setting within: <machineId providerType="PerDomain" />
   That section should look something like this when finished:
   <esha.licensing>
    <licenseService url="https://accounts.esha.com/licensing/Service.asmx" />
    <licenseWeb url="https://accounts.esha.com" />
    <idserver oauth2TokenEndpoint="https://login.esha.com/issue/oauth2/token" />
    <machineId providerType="PerDomain" />
</esha.licensing>
8. Save your changes, if copied to the desktop copy and replace the file back to the program folder.