Cannot Access HearAid After Windows 10 Update

<< Click to Display Table of Contents >>

Navigation:  HearAid On-Line Help > Frequently Asked Questions >

Cannot Access HearAid After Windows 10 Update

Previous pageReturn to chapter overviewNext page

There is a known issue with the Windows 10 Update installer removing the Firebird service from the Services list. There are three solutions to this problem, with the "best" solution being Solution 3 when users log in to HearAid with their own usernames and passwords. If everybody logs in with the SYSDBA username then Solutions 1 or 2 will also work. These solutions can only be run by the Windows Administrator user!

Solution 1: If users all have their own user names and passwords

1.Log in to your server computer as an Administrator

2.Open Windows File Explorer ie press Windows+E and navigate to the \HearSoft\HearAid folder

3.Right-click on InstallFirebirdService - Run as Administrator.bat and select Run as Administrator

InstallFirebirdService

4.Done (it will only take a fraction of a second to run, so you probably will not see anything other than perhaps a brief flash of a command window). The Firebird service should have reinstalled and started and you should be able to open HearAid again

This solution assumes you installed Firebird using the installer provided by HearSoft Pty Ltd and you used the default installation paths. If you installed Firebird into any other location you will need to modify the C:\Firebird\bin path in the batch file to reflect the actual installation path

Solution 2: If all users log in to HearAid using the SYSDBA username

1.Log in to your server computer as an Administrator

2.Download and run the Firebird installer from http://www.hearsoft.com.au/installers.htm

3.This will automatically restore the Firebird service

4.The SYSDBA password will be reset to     masterkey

This recent change to the Windows update installer, which appears to deem Firebird as not on the "compatibility list", is extremely annoying and quite unnecessary. Hopefully, it will only be a short term issue but if it persists I will notify you of a permanent solution.

Solution 3: Upgrade to HearAid 7.1 and switch to Firebird 3.0

Contact HearSoft to arrange the upgrade