ELITE DataSystem Enterprise Key Entry Not Saving
Issue
I’ve entered the Enterprise Key issued by Botron into ELITE Data Systems (EDS). After saving and re-launching the software, it still displays ELITE Data Systems Basic and Enterprise features are not available.
Resolution
1. Administrative Rights (Easy)
Please check that EDS is configured to run as administrator. If you do not have administrative privileges to the host running EDS please contact your IT department. You will need admin access to run the application.
- Close EDS
- Navigate to C:\Program Files (x86)\ELITE Tester Software
- Right click DataSystem_AppShell_V2.exe
- Go to Properties > Compatibility
- Check (enable) “Run this program as administrator”
- Click “Apply”
- Click “OK”
- Re-launch EDS
- Try re-entering in your Enterprise Key
2. Additional LSA Protection (Advanced)*
I’ve checked that EDS is running with administrative permissions. But, the Enterprise Key is still will not working.
If the Enterprise Key field is blank every time you re-launch the application, you may have “additional” LSA Protection enabled on your host. ELITE Data Systems is not a digitally signed application. Thus, “additional” LSA protection can prohibit you from applying the Enterprise Key.
Please see this Microsoft Knowledge Base Article for instructions to remove additional LSA protection.
*Botron is not responsible for any damages or loss of data.
3. Group Policy (Advanced)*
IMPORTANT –
I’ve checked that EDS is running with administrative permissions and “additional” LSA protection is not enabled but, the application will not save the database location/enterprise license key.
If you get prompted that the “Microsoft Access connection failed”, you may have some additional group policy security settings enabled.
To resolve this issue, navigate to the local group policy editor on the machine.
- Open the Run dialogue (Windows Key + R)
- Type gpedit.msc and click OK
- Navigate to “Computer Configuration > Windows Settings > Security Settings > Local Policies” and click “Security Options”
- Double click the “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” policy and ensure this is “Disabled”
*Botron is not responsible for any damages or loss of data.
Still not having any luck?
One of our Technical Support team members is happy to assist, please submit the following form: